Integrations & the marketplace
Integrations let a flow’s pre/post-hooks (see Flows) read from and write to external systems — look up a caller in your CRM before the conversation starts, check calendar availability, or record the outcome of a call.
Categories
Section titled “Categories”The marketplace groups integrations into crm, calendar, knowledge, and other. Each
integration is either connected via OAuth (for cloud SaaS providers) or via a token/API key
you paste in directly.
Available connectors
Section titled “Available connectors”| Connector | Category | Auth |
|---|---|---|
| HubSpot | CRM / analytics | OAuth |
| Confluence | Knowledge | OAuth |
| Google Calendar | Calendar | OAuth |
| Microsoft Calendar | Calendar | OAuth |
| Pipedrive | CRM | Token |
| Bexio | CRM/ERP (Swiss SMB) | Token |
| CalDAV (Nextcloud and other self-hosted calendars) | Calendar | Token (URL + app password) |
| Odoo | CRM/ERP (EU open-source) | Token (JSON-RPC) |
| Custom webhook | Other | none (arbitrary HTTP call) |
| Custom CRM (abstract-crm) | CRM | Token, self-defined endpoints |
| Custom Calendar (abstract-calendar) | Calendar | Token, self-defined endpoints |
Bexio, CalDAV, and Odoo were added specifically to cover the Swiss and broader-EU market: Bexio is a widely-used Swiss SMB CRM/ERP, CalDAV covers self-hosted calendar stacks common in EU-hosted deployments, and Odoo is a CRM/ERP with a very large EU installed base and a clean JSON-RPC API.
Salesforce, Zendesk, Notion, Intercom, Google Analytics 4, Stripe, and NetSuite are listed in the marketplace as coming soon — not yet connectable.
Custom (abstract) CRM and Calendar
Section titled “Custom (abstract) CRM and Calendar”If you don’t see your specific tool, Custom CRM and Custom Calendar let you map your own
HTTP API directly: you provide a base URL, a bearer token, and configure which capabilities
(lookup_by_phone, lookup_by_email, store_note, store_transcript for CRM;
check_availability, get_slots, schedule_meeting for calendar) your API supports, with
template-variable substitution in the request ({{phone}}, {{email}}, {{contact_id}}, …) and
JSONPath extraction for the response. This is the same mechanism a custom webhook hook action
uses more generally — an arbitrary HTTP call with a templated body and a response-path extraction
into a variable.
Connecting an integration
Section titled “Connecting an integration”From a project’s Integrations page, click Connect on a connector card. OAuth connectors redirect you through the provider’s consent screen; token connectors ask for the credential directly. Once connected, an integration becomes selectable inside a flow’s pre/post-hooks (see Flows) or as a global-tool calendar source.
Headless “abstract mode”
Section titled “Headless “abstract mode””Under the Headless product, integration templates reuse these same connect
forms but with {{field}} placeholders instead of concrete secrets — each tenant instance fills in
its own credentials when the integration template is materialized.