Integrations

Connect Converse to your existing CRM, helpdesk, data warehouse, or any other system using webhooks, HTTP tools, or MCP servers.

Webhooks (Outbound Events)

Configure webhooks to receive real-time notifications when events occur in Converse. Your endpoint receives a POST request with a JSON payload within milliseconds of the event.

Available events

• call.started — A new call session began. Payload includes caller number, agent ID, and channel.
• call.ended — A call finished. Payload includes duration, transcript, sentiment score, and reason.
• call.transferred — A call was transferred to a human or number.
• escalation.created — A call was escalated to the human handoff queue.
• campaign.contact.completed — A campaign contact was dialed. Payload includes outcome and interest detection result.
• campaign.completed — All contacts in a campaign have been processed.

HTTP Tools (Agent actions)

Your agents can call any HTTP endpoint mid-conversation. This is the primary way to integrate with CRMs, databases, and business systems. See Knowledge & Tools for full configuration details.

Common use cases

• Look up a customer record in your CRM by phone number
• Check order status or inventory
• Book an appointment in your calendar system
• Submit a support ticket
• Verify identity or account status
• Send data to your analytics pipeline

Example: CRM lookup

{
  "name": "get_customer",
  "type": "http",
  "http_method": "GET",
  "http_url": "https://crm.example.com/customers?phone={{caller_phone}}",
  "http_headers": { "Authorization": "Bearer {{api_token}}" },
  "description": "Look up customer record by phone number at the start of a call",
  "when_to_use": "When the call starts, look up the customer's name and account status"
}

MCP Servers

Model Context Protocol (MCP) is an open standard that lets you connect any MCP-compatible server to your agents. This is the most powerful integration option — a single MCP server can expose dozens of tools.

Popular MCP servers provide access to:

• Databases (read/write SQL)
• File systems and document stores
• Third-party APIs (GitHub, Slack, Google Workspace)
• Custom internal tools and microservices

See Knowledge & Tools → MCP Servers for setup instructions.

Data isolation

All integrations — HTTP tools, webhooks, and MCP servers — are scoped to your organization. One organization's tools cannot be accessed or triggered by another organization's agents. This is enforced at both the application and database levels.