Skip to content

Integrations

Connect chat outcomes to the systems your team already uses.

Chatvox keeps native integrations focused and practical: route urgent moments into Slack, sync leads into Salesforce, or use Custom API when the workflow needs a direct HTTPS connection.

Start building See pricing
Slack
Salesforce
Custom API extensibility

Native

Current integration surface

Today the native integration story is intentionally narrow: Slack and Salesforce are the registered providers, and both connect at the agent level rather than only at the workspace level.

01

Slack

Slack is the fastest path from customer conversation to internal team awareness. Connect an agent through OAuth, sync channel options, and send notifications when a chat needs human attention or operational follow-up.

Starter plan or above
OAuth-based agent connection
Supports Slack Notification action

02

Salesforce

Salesforce handles CRM-connected lead handoff. Connect it per agent, then use Salesforce Add Lead to push captured lead data into Salesforce and shorten the path from conversation to sales ownership.

Starter plan or above
OAuth connection with sync visibility
Supports Salesforce Add Lead action

Extensibility

When native integrations are not enough, use Custom API

Custom API is the main extensibility layer for Chatvox. It is the route for internal systems, custom endpoints, and workflows that do not fit the native Slack or Salesforce path.

Custom API capabilities

Use Custom API when the agent needs to query an internal system, create or update records in a third-party tool, or trigger an external operational workflow during the conversation.

HTTP methods

GET, POST, PUT, PATCH, DELETE

Auth options

Bearer token, basic auth, API key, or none

Response modes

JSON or text

Timeout window

1,000 ms to 15,000 ms

Constraints worth knowing

The endpoint URL must be public and HTTPS.
Instructions are required for the action configuration.
Multiple Custom API actions can be created for one agent.
Request fields, headers, and response mapping are configurable.

Workflow Map

Which connection path fits which outcome

The practical decision is usually simple: use native integrations when the workflow matches Slack or Salesforce, and use Custom API when it does not.

Need
Best path
Why it fits
Typical outcome
Notify the team about an important conversation
Slack
Native channel-aware notification flow
A team sees the issue in Slack quickly
Push captured lead data into CRM
Salesforce
Native lead handoff path from chat to CRM
Qualified lead ownership starts faster
Call an internal product or operations endpoint
Custom API
Native integrations do not cover custom systems
The conversation triggers an external workflow
Handle a product-specific routing or data update
Custom API
Custom request/response mapping gives more control
Chat fits the business process instead of the reverse

Connected Actions

Integrations matter because actions can use them in real workflows

Slack and Salesforce are not isolated settings pages. They become useful when the agent uses them during a conversation to notify a team, capture a lead, or route a next step.

That is why the integration story and the action story are tightly connected in Chatvox.

Collect Leads

Configurable capture forms

Native

Smart lead capture that waits for intent instead of blocking every chat. Configurable fields and messaging.

Slack Notification

Route to the right channel

Native

Send real-time Slack notifications for notable conversations, lead captures, and escalation moments.

Salesforce Add Lead

CRM sync automation

Native

Automatically push captured lead data into your Salesforce instance. Connect at the agent level for precise control.

Custom API

Your HTTPS endpoints

Extensible

Call your own endpoints during conversations to connect CRMs, ticketing, scheduling, or any operational tooling.

Integrations FAQ

A few practical questions about the integration model

Which native integrations are currently available?

The current registered native integrations are Slack and Salesforce.

Do integrations connect per workspace or per agent?

Integrations connect per agent. One agent on a team can have Slack or Salesforce connected while another agent on the same team does not.

Do native integrations require a paid plan?

Yes. Native integrations require Starter or above.

Can integrations be disabled globally?

Yes. Super admins can globally enable or disable integration providers across the application, which is useful for maintenance windows or staged rollouts.

Should Custom API be described as a native integration?

No. Custom API is better positioned as the extensibility layer for workflows beyond the native Slack and Salesforce connections.

Start with the native path when it fits,then extend the workflow when needed

Connect Slack or Salesforce for the common routed outcomes, and use Custom API when the business process needs a more specific system touchpoint.

Create your first Chatvox agent