SAMIOS
Help Center

Set up the CINC Zapier bridge

Pair a personal SAMI API key with your cincConnectionId so a Code by Zapier step can pass CINC lead events into SAMI OS.

Open in SAMI OS

The CINC Zapier bridge lets a Zap pass CINC lead events into SAMI OS through the public API. You create a personal SAMI key, pair it with your CINC connection ID, and use both inside a Code by Zapier step.

What the bridge does

The bridge connects CINC to SAMI OS using two values: a personal API key (read and write access) and your cincConnectionId. Drop both into a Code by Zapier step, and your Zap can push CINC lead activity into SAMI OS — firing workflow triggers and writing the lead back into Contacts on your behalf.

The key authenticates the call. The cincConnectionId tells SAMI which connected CINC account the events belong to, so it can refresh that user-owned CINC token. Both live on the CINC tab in Settings.

Connect your CINC account first. Without an active connection, there's no cincConnectionId to pair with your key, and the bridge has nothing to point at.

Create your bridge key and copy both values

  1. Open the CINC tab

    Go to Settings and open the CINC tab. Confirm you have an active connection under "Connected CINC accounts."

  2. Copy your cincConnectionId

    On the connected account card, find the cincConnectionId field and click the copy icon. (It's also shown under "Save this for Zapier" right after you connect.) Paste it somewhere safe for the next step.

  3. Create a personal Zapier key

    In the "Zapier bridge keys" section, click Create key. SAMI generates a personal key with read and write access named "Zapier / CINC bridge."

  4. Copy the key immediately

    The plaintext key appears once under "Personal Zapier key created." Click the copy icon and store it now — SAMI will not show the full key again, only a short prefix.

  5. Wire up Code by Zapier

    In your Zap, add a Code by Zapier step and paste both the API key and the cincConnectionId so the step can authenticate and target the right CINC connection.

The key carries read and write scopes, so the same value can both look up records and write CINC leads back into SAMI OS. Treat it like a password.

Revoke a bridge key

Each key in the "Zapier bridge keys" list shows its prefix, when it was created, and when it was last used. To turn one off, click Revoke next to it. The key stops working right away, so update or remove the matching Zap so your CINC events keep flowing.

If you rotate keys, create the replacement and update your Code by Zapier step before revoking the old one. You can manage keys used by other tools alongside these on your other connected accounts.

Related articles

Last updated 2026-06-21

Was this helpful?