Slack integrationKnow in Slack the moment someone watches
Zidi posts to a single Slack channel when the things worth interrupting people for happen: a video is viewed, a call-to-action is clicked, a campaign goes out, or a viewer crosses half, four-fifths or all of a recording.
It is the fastest feedback loop the product has. A prospect opens the walkthrough you sent this morning and the rep who sent it finds out in the place they already have open, rather than the next time they think to check a dashboard.
How to connect Slack
- 1
Open the Slack card in Zidi
Go to Integrations in your Zidi dashboard and choose Slack. Connecting needs someone who can add an app to the Slack workspace.
- 2
Approve the app in Slack
Slack asks for permission to post messages, to join a public channel and to see basic information about your channels so Zidi can offer you a choice of destination. Approve it and you are returned to Zidi.
- 3
Pick the channel
Choose which channel receives the notifications. Zidi adds itself to a public channel on its own; for a private one, type /invite @Zidi in that channel first so the app can post there.
Slack notifications are on the Zidi Pro plan. One channel is stored per Zidi account, so pick the place the people who send videos actually read — a shared sales channel usually beats a personal direct message, because the value is in a teammate spotting the reply opportunity you missed.
What Zidi posts, and when
| What happens in Zidi | What appears in Slack |
|---|---|
| A video is viewed | A message naming the video and the viewer where one is known, so the person who sent it can act while the tab is still open on the other side. |
| A call-to-action is clicked | A message recording that the button on the video page was pressed — the strongest signal a video produces. |
| A campaign is launched | A message confirming that the campaign has gone out, which doubles as the timestamp everybody can measure replies against. |
| A viewer crosses fifty, eighty or one hundred per cent | A milestone message, so a long recording tells you who is still watching rather than only who started. |
Messages are sent once and not retried. That is a deliberate trade: a duplicate alert in a busy channel costs more attention than a missed one, so Zidi would rather drop a notification than post it twice if Slack is briefly unreachable. The CRM integrations behave the opposite way, queueing and retrying, because a missing record matters more there than a delayed one.
One channel, chosen on purpose
Zidi posts to a single channel per workspace rather than routing by campaign or by sender. That is a smaller feature than it could be, and it is the right size for what these messages are: interruptions. A channel with a handful of alerts a day gets read, and one that has been split six ways gets muted. If you need the traffic separated later, Slack's own tools do it better than a routing table inside Zidi would — a channel-specific keyword alert, or a workflow that reposts anything mentioning a particular campaign name. Start with the shared channel where the people who send videos already talk to each other, and move it only if the volume proves you wrong.
Public channels need nothing from you. Zidi joins them itself once you pick them. A private channel is invisible to an app until it is invited, so type /invite @Zidi there before you expect the first message.
What Slack tells you that a dashboard cannot
The value of a view notification is entirely in its timing. Knowing that somebody watched your demo two days ago is a report; knowing they are watching it now is a reason to send a message while you are on their mind. That is why the milestone alerts exist at all: on a ten-minute walkthrough, the fact that a prospect is still there at eighty per cent is a stronger buying signal than the initial click, and it arrives in time to be useful. Pair it with the CRM integrations rather than choosing between them — Slack is where the team reacts, and the CRM is where the record lives once the moment has passed.
What Slack will not tell you about. There are four notification types and no others. Comments left on a video, uploads, edits and analytics summaries do not produce messages, so nobody should build a process on an alert that is not in the list above.
Slack integration questions
Which events produce a message?
Four: a video view, a call-to-action click, a campaign launch, and a viewer crossing fifty, eighty or one hundred per cent of a recording. Nothing else does. In particular there is no notification when somebody comments on a video, so do not rely on Slack to surface those.
Can I send different videos to different channels?
Not today. One channel is stored per Zidi account and every notification from it goes there; a teammate who connects Slack separately picks their own. If you need to split the stream, Slack's own keyword alerts and workflows can watch the channel and repost what matters to a narrower audience.
Why did a notification never arrive?
Two likely reasons. The channel is private and Zidi was never invited, which you fix by typing /invite @Zidi in it. Or Slack was briefly unreachable when the message was sent: notifications are delivered at most once and are not retried, because a repeated alert costs a busy channel more than a missing one. The underlying event is still recorded in your Zidi analytics and, if you use them, in your CRM.
Does connecting Slack let Zidi read our conversations?
No. Zidi asks for four permissions and no more: posting messages, joining a public channel, and viewing basic information about public and private channels so it can offer you a choice of destination. None of them grants access to message history, and the app cannot see direct messages at all. It is a one-way connection — Zidi posts into the channel you picked and never reads anything back out of Slack.
Which Zidi plan is required?
Pro, checked on the server when the connection is made and again before each message is sent. A workspace that drops off Pro stops receiving notifications and keeps the connection, so an upgrade resumes them without reconnecting Slack.
Still stuck? Email support@zidi.ai or contact our team.
Other Zidi integrations
CopperPaste a Copper API key and the login email that made it. Recipients become People and engagement is logged as Activities on the contact.
HubSpotCampaign recipients become HubSpot contacts matched by email, and video engagement lands on the contact as five custom properties Zidi creates plus a note.
SalesforceRecipients are matched or created as Contacts; opens, completions and CTA clicks are logged as completed Tasks on the activity timeline.
ZohoConnect any of Zoho CRM's data-centre regions with OAuth. Recipients sync as Contacts and engagement is written as Notes on the contact.
ActiveCampaignConnect with your API URL and key. Recipients sync as Contacts with Notes, and Zidi applies engagement tags such as Watched Video and High Engagement.
CloseConnect Close with OAuth. Recipients are matched by email and video engagement is written as note Activities on the record.
FreshsalesConnect with your Freshsales bundle alias and API key. Recipients sync as Contacts and engagement is written as Notes on the contact.
Monday.comPick a board, paste an API key, and each recipient becomes a board item whose updates record how far they watched and whether they clicked.
ZapierZidi is a public app in the Zapier App Directory, with five triggers: video viewed, video uploaded, CTA clicked, campaign launched and watch threshold.
MakePaste a Make.com webhook URL and Zidi posts the same five events to it, each carrying an idempotency key your scenario can use to ignore retries.
See every Zidi integration — CRMs, Zapier, Make, Slack, tracking pixels and embed guides.