Skip to content
ZidiDocs

Integrations overview

The Integrations page connects Zidi to your CRM, your automation tools, Slack and your ad pixels. This page lists every card, how each one connects, and which plan you need.

Available on: Pro for every card you connect. Starter and Pro for the campaign webhook. Free, Starter and Pro for Claude and ChatGPT.

Open the Integrations page

  1. In the sidebar, click Integrations.
  2. Use the category buttons (All, Sales & CRM, Analytics, Automation, Notifications, Website Embeds) or the Search integrations... box to find a card.
  3. Click a card to open its page. Each connectable card has its own connect and disconnect buttons. Embed cards open a guide.

The header counts your connections as "n / 18 connected". Only the 18 cards you can connect count. The 8 website embed cards are guides and are counted separately as "8 embed guides".

Each card carries a badge:

  • Connected: the integration is set up. Hovering shows Manage.
  • Available: you can connect it. Hovering shows Set up.
  • Guide: a how-to page with nothing to connect. Hovering shows View guide.

Which plan you need

Everyone can open every card and read it. Connecting any integration on this page needs the Pro plan. Starter is not enough. A paid seat on a Pro team also counts as Pro.

If you are on Free or Starter and click a connect button, a dialog opens instead. It says "Connecting Name to Zidi is a Pro feature." Click Upgrade Plan to go to Billing, or Maybe Later to close it.

The campaign webhook is one exception. It is not a card on this page. It lives on each campaign and works on Starter and Pro.

Claude and ChatGPT are the other exception. They are not cards either, and you can connect them on every plan. See Claude and ChatGPT.

See Plans and limits for everything else each plan includes.

Every card and how it connects

CRMs (Sales & CRM)

All eight CRMs send data one way, from Zidi into the CRM. How CRM sync works explains what is written and when.

CardHow you connectGuide
Copper CRMSign in with Copper (or an API key)Copper
HubSpotSign in with HubSpotHubSpot
SalesforceSign in with SalesforceSalesforce
Zoho CRMPick your region, then sign in with ZohoZoho CRM
FreshsalesDomain and API keyFreshsales
Monday.comAPI token and a boardmonday.com
Close CRMSign in with CloseClose
ActiveCampaignAPI URL and API keyActiveCampaign

Automation

CardHow you connectGuide
ZapierAdd a Zidi step in Zapier and allow accessZapier
Make.comPaste a Make webhook URLMake

Notifications

CardHow you connectGuide
SlackSign in with Slack, then pick a channelSlack

AI assistants

Claude and ChatGPT have no card on this page. You connect them from inside the assistant, on any plan; see Claude and ChatGPT.

Tracking pixels (Analytics)

Seven cards: Google Analytics 4, Google Tag Manager, Meta Pixel, LinkedIn Insight Tag, X (Twitter) Pixel, TikTok Pixel and Pinterest Tag. For each one you paste your ID and click the connect button. See Tracking pixels.

Website embeds

Eight guide cards: WordPress, Webflow, Wix, Squarespace, Carrd, Notion, Substack and Linktree. There is nothing to connect. They explain how to paste a Zidi video into those sites. See Embed on a website.

Campaign webhooks

Not a card on the Integrations page. You set it up on a draft campaign's Custom Webhook card. It sends campaign details to your own HTTPS address when you launch, signed so your server can check that the request came from Zidi. Available on Starter and Pro. See Campaign webhooks.

What happens if you leave Pro

Your CRM, Make.com, Slack and pixel connections stay in place. Sending pauses until you are on Pro again and resumes without reconnecting. The table shows what happens to each one. Zapier also pauses. If you switch from Pro to Starter, Zidi may also remove its Zapier connection. If Zapier asks after you upgrade, reconnect Zidi there. If your subscription is cancelled or ends instead, the Zapier connection stays and works again once you are back on Pro.

IntegrationWhile you are not on Pro
CRMsNo launch pushes, no campaign engagement updates and no tracked-share notes. A Copper-sent draft cannot launch; see Campaigns sent from Copper.
ZapierYour Zaps get no events and Zidi searches fail. After a switch from Pro to Starter, the connection may be removed. After you upgrade, check your Zaps and reconnect the Zidi account in Zapier if it asks.
Make.comNothing is sent to your scenario.
SlackNo messages are posted.
Tracking pixelsPixels stop loading on your pages. The card still shows Connected.

Events that happen while you are off Pro are not sent later. The exception is a campaign launched during the gap: after you upgrade, open the campaign and click Re-sync to CRM to push its recipients. For campaigns you launched earlier, a recipient's next visit after you upgrade updates your CRM with where they are now.

You can still disconnect any integration while you are off Pro.

Recent Sync Activity

Below the cards, the Recent Sync Activity table shows the last 20 things Zidi wrote, or tried to write, to your connected CRMs. It appears once there is at least one entry. Click Refresh to reload it. It covers CRMs only, not Zapier, Make, Slack or pixels.

ColumnWhat it shows
ActionWhich kind of sync ran (see below)
Statussuccess, failed, skipped, partial, or pending (a Copper import still running)
DetailsThe recipient's email for launch pushes, the error text for failures, which follow-up failed for partial entries, or a short raw record for engagement and tracked-share entries. Email addresses inside error text are hidden as [redacted-email].
DateWhen it ran, in your local time

The Action column shows internal codes:

ActionMeaning
campaign_contact_pushA recipient pushed at launch or by Re-sync
campaign_engagementA campaign opened or completed update
timeline_eventA tracked-share viewing note
copper_audience_importAn audience import from Copper into a campaign

A partial status means the contact was written but the note or tag was not. The Details column then starts with "note failed:" or "tag failed:".

The table only shows entries for CRMs that are connected now. Entries for a CRM you disconnected are kept. They are hidden while it is disconnected and reappear if you connect the same CRM again. The "Synced records" number on each CRM page counts every entry, including failed and skipped ones.

How Zidi stores your credentials

Sign-in tokens and API keys are stored encrypted with AES-256-GCM. Each connection belongs to your own Zidi user. Teammates do not share it: each person connects their own CRM account.