Technology & Integrations
Technologies organized by function. Integrations are scoped per project, not assumed to be prebuilt connectors.
Groq API
SupportedAI models and providers
Use: Model inference for chat and agents
Needs: API key held by the deployment
n8n
SupportedWorkflow automation
Use: Orchestrating multi-step workflows
Needs: An n8n instance and credentials per tool
Webhooks
SupportedWorkflow automation
Use: Triggering workflows from forms and events
Needs: A sender that can POST
Chatwoot
SupportedCustomer support
Use: Inbox, handoff to humans, conversation history
Needs: Chatwoot account and API token
Docker
SupportedDeployment
Use: Packaging and running services
Needs: A host that runs containers
Generic CRM with an API
Requires technical validationCRM systems
Use: Lead creation and updates
Needs: API access, field mapping, write permission
Email / calendar providers
Requires technical validationEmail and scheduling
Use: Notifications and booking
Needs: API or SMTP access
Telephony provider
Requires custom implementationVoice and telephony
Use: Inbound and outbound calls
Needs: Provider account and number
Customer databases
Requires technical validationDatabases and vector search
Use: Read-only lookups for answers
Needs: Scoped read credentials
Software with no API
Not currently supportedLegacy or closed software
Use: -
Needs: Assessed case by case
Having a public API does not mean an integration exists. Each one is scoped and validated per project.
For any integration, we clarify
- What can be connected and what data can move
- Possible workflows and required permissions
- Technical limitations
- How to request it: use the contact form