Integrating Collected Customer Data from SMOC.AI

Simple guide showing how to connect SMOC customer and outcome data to your CRM, data warehouse, or custom systems.

Get your integration token

All SMOC data integrations authenticate with a private API key generated in Console — the same pattern as Zapier and MCP.

For the REST API and MCP:

Go to Settings → Integrations → API in SMOC Console.
Generate a new key and copy it immediately — it's shown only once, so store it somewhere secure.

Your key is tied to your company. Every request made with it is automatically scoped to your data — you only see contacts, companies, and analytics that belong to you.

Integration options

SMOC supports several ways to move data out of the platform:

Zapier — no-code automation to 2,000+ apps with the New Contact trigger. Generate a key under Settings → Integrations → Zapier. See the Zapier eGuide.
REST API — programmatic access for contact retrieval, messaging workflows, sync jobs, and custom pipelines. Use the API key from Settings → Integrations → API.
MCP — read-only access for AI clients such as Claude, Cursor, and VS Code. Uses the same API key from Settings → Integrations → API. See the MCP eGuide.
Integration partners — contact SMOC for managed handoffs through partner connectors.
Manual export — download CSV from the contacts section in Console when you need a one-off extract.

Using the REST API

Send your integration key on each request to SMOC public REST endpoints. Typical use cases include:

Retrieving contacts and interaction history for CRM or data-warehouse sync.
Routing outcomes into internal pipelines on a schedule.
Connecting messaging workflows and outcome data to your stack.

All responses stay company-scoped — you never see another tenant's data.

For endpoint details and examples, follow the steps in this guide and the related eGuides at smoc.ai/eguides. For a product overview of all integration paths, see smoc.ai/integrations.