Platform / Integrations

Connect the tools
you already use.

Bring outside services into the same workspace so applications, agents, chatbots, email flows, and phone workflows can do real work.

The integration model

From provider event to inside work.

Integrations are more than a list of connectors. A provider sends an event, a credential establishes trust, an integration script normalizes the payload, and a connection routes the result to the right workspace capability.

ProviderWhatsApp, Instagram, Facebook, Twitter/X, Telnyx, email, ChatGPT, Claude, or another service.
CredentialEncrypted access details, scopes, provider fields, and a status that can be monitored or revoked.
DestinationA chatbot, application, agent, workflow, email flow, phone flow, or MCP client.

Credentials

Create a trusted path to a provider.

Credentials hold the provider-specific information needed to communicate with an external service. They are owned by the workspace, stored securely, and can be revoked without rebuilding the applications that use them.

Authentication options

Use the authentication method required by the provider: manual values, OAuth, API keys, tokens, basic authentication, or a custom credential type.

Provider configuration

Name the credential, enter its provider fields, choose the integration script, configure scopes or extra parameters, and use the generated webhook URL when the provider needs one.

Credential states: active credentials can receive events, revoked credentials are intentionally disabled, and error credentials need attention before dependent workflows can continue.

Event lifecycle

Every event is observable.

External providers use different payloads and event names. Integration scripts turn those payloads into a normalized event that the rest of the platform can process consistently.

01ReceivedThe provider sends an event to the configured webhook.
02NormalizedThe integration script converts provider data into a common structure.
03QueuedThe event is prepared for the connected workspace capability.
04ProcessedThe application, chatbot, agent, or workflow handles the event.

When something needs attention: events can remain pending configuration or move to failed. Review the credential, script, webhook configuration, permissions, and provider response before retrying.

Channels

Meet customers where they already are.

Social messaging

Connect WhatsApp, Instagram, Facebook, or Twitter/X credentials and route incoming messages or channel events to a chatbot. The platform can create or continue a conversation using normalized provider data.

Configure chatbots ↗

Phone with Telnyx

Telnyx uses provider-specific webhook handling and signed request validation. Connect the credential to a phone-enabled chatbot or call flow and investigate signature, status, or routing errors when calls do not arrive.

Incoming email

Generate an inbound email address or webhook, select the handling script, and enable or disable the route. Incoming messages can become inputs for workspace workflows.

External AI through MCP

Authorize ChatGPT or Claude through the dedicated MCP OAuth flow. Access is scope-based, connections can expire or be revoked, and the connection can be managed from workspace settings.

Explore MCP ↗

Chatbot bindings

One credential does not mean every bot receives every event.

A provider credential becomes useful to a chatbot through an explicit connection and binding. This keeps channel ownership clear and prevents unrelated chatbots from receiving the same traffic by accident.

Credential / connection
↓
Chatbot binding
↓
Normalized event
↓
Conversation, response, or human handover

Use the chatbot configuration to define the bot’s instructions, permissions, welcome behavior, and human handover rules.

Security and operations

Keep connections controlled and recoverable.

Encrypted valuesProvider secrets are stored as protected credential data rather than exposed in the documentation or user interface.
Scoped accessUse provider scopes and workspace permissions to limit what a connection can do.
Revoke quicklyRevoke credentials or MCP connections when access should stop, then reconnect with corrected values.

Credential error

Check provider values, required scopes, expiry, and whether the credential is active. Revoke and recreate it when the provider no longer accepts the original secret.

Event failure

Check the webhook URL, selected integration script, provider signature, chatbot binding, and event status. A valid credential can still fail if the event route is incomplete.

A complete example

Connect a social support chatbot.

  1. Create the credential. Choose the provider credential type and enter the required provider values.
  2. Select the integration script. The script receives provider events and decides how to normalize and handle them.
  3. Configure the webhook. Copy the generated webhook URL into the provider’s channel settings.
  4. Bind the chatbot. Connect the active channel connection to the chatbot that should receive the conversation.
  5. Process the conversation. The event is received, normalized, queued, and delivered to the chatbot or a human handover path.

The same pattern applies across channels: establish trust, receive the event, normalize it, connect it to the right capability, and monitor the result.

Build agents ↗Build with prompts ↗Read Chatbots ↗