Outbound OS
Sign inBook a demo

Integrations

The connections that exist, and what they require.

Outbound OS connects customer conversations, lead sources and approved AI clients to the CRM. A named connection means the product supports it; it does not remove the account or provider approval needed to use it.

Channels

Where customer conversations move.

WhatsAppAvailable

WhatsApp Business Cloud API

Connected through a supported business solution provider, using the customer’s business account.

Before setup

  • A Meta Business account
  • A WhatsApp Business sender number connected through the provider
  • Meta-approved templates where template messages are required
Available

SMTP and IMAP

Sending and reply intake run through the customer’s own mailboxes.

Before setup

  • SMTP and IMAP server details
  • Credentials or app passwords for each mailbox
  • Provider permission for the intended sending volume

Lead sources and data

Bring records in without pretending every system has a native app.

IndiaMARTAvailable

IndiaMART enquiry API

Enquiries enter the workspace through IndiaMART’s available API access.

Before setup

  • An IndiaMART account with enquiry API access
  • The credentials associated with that account
Data transferAvailable

CSV import and export

Move structured lead data into or out of the workspace.

Before use

  • A CSV whose fields can be mapped during import
  • No third-party account connection is required
DeveloperAvailable

Webhooks

Send supported workspace events to a receiving endpoint the customer controls.

Before setup

  • A receiving HTTPS endpoint
  • Agreement on the payload and events being used

AI clients

Connect through MCP, not a copied export.

The MCP endpoint exposes explicit CRM tools to authenticated, compatible clients.

MCPAvailable

Model Context Protocol server

Claude and other MCP-capable clients can work with leads, messages, campaigns, analytics and system controls.

Before setup

  • A client that supports remote MCP servers
  • An approved authentication credential
  • Tool-approval behavior configured for write and destructive actions
Read the MCP guide

Not implied

No imaginary catalogue.

If a channel, CRM or marketplace is not named above, treat it as unavailable unless confirmed during implementation.

Planned connections belong on the roadmap after there is real scope behind them, not as faded logos on this page.

Check the accounts your team controls.

Bring the channels and lead sources you use. We will show what can connect now and what approval is still needed.

Book a demo