Connections & API keys

The Connections tab connects the CRM to the rest of the world: it issues API keys that outside systems use to write leads in. Your web agency's landing page, a partner's site, a Zapier step, your own backend — anything that can POST JSON can file a deal.

How it works

1. 1
   Create a key

   CRM → Connections → New key. Name it after the source ("Landing page — spring promo").
2. 2
   Pick the destination

   Each key targets a board and a column — "send this source's leads to New requests". Different sources can land in different columns.
3. 3
   Send it

   The key (crk_…) is shown once. The caller POSTs form fields to /crm/ingest with it — see the CRM ingest API for the exact contract.

One service, many CRMs

A CRM service is a container, not a single database. It holds as many tables (the rows) and boards (the pipelines those rows appear on as cards) as you need — leads, applicants and support requests can each have their own, side by side in one service.

A Connections key points at exactly one table via database_id, and optionally at a board column, so each source lands where it belongs. Over MCP that whole chain is create_crm_table → create_crm_board → create_crm_api_key; the tool reference has the arguments.

What a submission becomes

• A row in the CRM table, fields matched to your CRM fields by key or label.
• A card in the key's target column.
• An attribution record naming the key — the deal knows which website sent it.
• A **form submitted trigger** — so the speed-to-lead recipe covers external forms too.