- Home
- Resources
- Integrations
- CONSENSUS
CONSENSUS Zapier integrationAutomate CONSENSUS with Zapier.
The CONSENSUS Zapier integration gives you 2 triggers, 0 actions and 0 searches. In plain terms: CONSENSUS can start an automation when a lead arrives or a demo gets watched, but nothing can write back into it. Here is what that buys you.
Verified Trustpilot reviews · AI, automation & growth agency
What the CONSENSUS Zapier integration actually does
CONSENSUS runs interactive video demos that prospects watch on their own time. Hooked up to Zapier, it becomes a starting point: each new lead, or each demo someone watches, can kick off work in the rest of your tools. It only goes one way, out of CONSENSUS.
Three things people usually build with it. First, a lead alert: New Lead fires, and your sales channel or CRM hears about the prospect while they are still warm. Second, a follow-up queue: Demo Watched fires when someone views a demo from Sales Accelerator, so a rep can call the people who watched it, not the whole list. Third, a running log: either trigger feeds a sheet, which gives you a record of demand that does not depend on anyone remembering to export it.
Now the part the listing does not spell out. CONSENSUS has no actions and no search steps on Zapier. A Zap cannot create a demo, update a lead or look anything up inside CONSENSUS. If your plan needs data pushed back into it, Zapier will not do that job, and you will have to handle that side some other way.
Both triggers are instant (more on that below), which is good news on a free plan. If you are weighing tools before you commit, the n8n vs Zapier and Make vs Zapier comparisons lay out the trade-offs.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here is what each one means, without the jargon.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in another app.
- Task
- The unit Zapier bills. One task equals one action your Zap completes successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming item meets a condition you set, and stops it the rest of the time.
- Connection
- Your CONSENSUS account linked to Zapier once, then reused by every step in every Zap that touches CONSENSUS.
What it costs you in tasks
CONSENSUS is not a premium app, so it works on the free plan. The trigger itself never costs a task.
- Premium appNo, works on the free plan
- Free plan tasks100 per month
- Free plan Zap sizeTwo steps: one trigger, one action
- Trigger costZero tasks
Only a successful action is billed: a lead posted to Slack is one task, and a failed post costs nothing. The free plan gives you 100 tasks a month. Catch: it stops at two steps, one trigger plus one action, and nothing more. Add a filter or a second action and you have a multi-step Zap, which needs a paid plan. The interval grid below only concerns polling triggers; both CONSENSUS triggers skip it, because the app reports each event itself.
Connect CONSENSUS to Zapier in three steps
- 01
Open your Apps page
In your Zapier account, go to Apps and click + Add connection. Before that, make sure you hold a CONSENSUS account, plus access to anything you do not own yourself that the Zap should follow.
- 02
Pick CONSENSUS
Type CONSENSUS into the search box of the dialog, select it, then confirm with Add connection. Zapier hands you over to CONSENSUS so you can sign in there.
- 03
Sign in and grant access
Log in to CONSENSUS with the account whose leads and demos you want to follow, then allow Zapier to reach it. The connection now shows up in your list, ready for any Zap.
Your first Zap: hot leads to Slack
GoalPost each new CONSENSUS lead to a sales channel, but only the ones worth a fast reply.
- 01
Create the Zap
Start a new Zap, pick CONSENSUS as the app that starts it and New Lead as the event, then select the connection you made earlier.
- 02
Test the trigger
Run the test. Zapier pulls the three most recent leads from your account, so you can pick a real one and see exactly which values CONSENSUS sends.
- 03
Add a filter
From the plus icon, add Filter. Choose one value you spotted in the test, a rule, and what to compare it with. Text rules only work on text, so pick the right type.
- 04
Add the Slack action
Add Slack with Send Channel Message, choose the channel, and map the lead values from the trigger into the message so a rep sees who it is at a glance.
- 05
Test, then publish
Run each step once and read what came back. When the message looks right, click Publish. The filter makes this a multi-step Zap, so it needs a paid plan.
The 2 CONSENSUS triggers
2 events start a Zap when something happens in CONSENSUS, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
Demo Watched
Instant triggerIn Zapier“Triggers when a demo is watched from Sales Accelerator.”
This one starts your Zap each time a prospect views a demo from Sales Accelerator. It tells you who engaged with the content, which is a different signal from who simply filled in a form.
New Lead
Instant triggerIn Zapier“Triggers when a new lead is collected in Consensus.”
Every time CONSENSUS collects a fresh lead, this trigger hands it to Zapier, ready to be posted, logged or pushed into a CRM by the action you pick next.
When a CONSENSUS Zap breaks
Zapier attaches no help article to CONSENSUS, and no app-specific limit has been documented. What goes wrong comes from Zapier itself.
Four cases cover most of the head-scratching. If one of them does not match what you see, the Zapier troubleshooting page walks through the wider list.
Old leads never show up
A Zap only reacts to events after it is switched on. Leads and watched demos from before that moment are not picked up; moving them is a separate job.A big import goes quiet
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back instead of running them all.The filter never lets anything through
Filter rules are typed. A text rule only reads text and a number rule only reads numbers, so picking the wrong type stops every single lead.Publish is blocked on the free plan
The free plan builds two-step Zaps only. A filter or a second action turns it into a multi-step Zap, which asks for a paid plan before it runs.
Need help automating CONSENSUS with Zapier?
A person reads every message.



