- Home
- Resources
- Integrations
- Clarify
Clarify Zapier integrationAutomate Clarify with Zapier.
The Clarify Zapier integration gives you 3 triggers, 7 actions and 5 searches. All three triggers are instant, so your Zaps start the moment a record moves, even on the free plan. Here is what each one does, what it costs and where it trips people up.
Verified Trustpilot reviews · AI, automation & growth agency
What the Clarify Zapier integration actually does for your pipeline
Clarify is a CRM built for revenue teams. Hooking it to Zapier lets a change in Clarify start an automation, called a Zap, and lets a Zap write back into Clarify: create a record, update it, label it, comment on it or delete it. No code, and no export to babysit.
Three outcomes cover most of what people build. First, a labelled pipeline: a record lands in a list, and Add Label to Record or Remove Label From Record keeps the tags in step without anyone clicking. Second, a written trail on every account: Create Comment drops a note on a person or a company the moment something happens elsewhere in your process. Third, a clean database: Find Company and Find Person check whether a record already exists before anything gets created, and can create it when it does not.
One extra deserves a mention. Get Meeting Recording Transcript pulls the transcript of a recorded meeting into the Zap, so a later step can work with the text.
Now the limits. Every action needs to know which kind of record it is touching (the Object field, Person or Company for instance), and most need the record ID too. Clarify will not guess it for you: the ID has to come from the trigger or from a search step placed before. And the Zap only sees what happens after it is switched on.
Data read on 1 October 2026 from version App207796CLIAPI@2.1.2 of the app. If you are weighing platforms before you commit, our Make vs Zapier comparison sets them side by side.
Zapier vocabulary, in plain English
Seven words come back on every line of this page. Here they are once, so the rest reads easily.
- Zap
- The automation you build: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier sits and waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or changes something for you in an app.
- Task
- What Zapier bills you for: one action that completes successfully. Your plan counts these and nothing else.
- Polling vs instant
- Polling: Zapier checks the app on a timer. Instant: the app calls Zapier itself the second the event happens.
- Filter
- A step that lets the Zap continue only when the data that arrived meets your condition, and stops it otherwise.
- Search step
- A step that looks up something already in the app, so the steps after it can use what it found.
What a Clarify Zap really costs
Clarify is not a premium app on Zapier, so it works on the free plan. The trigger never costs a task, and neither does Zapier checking for new data.
- Free tasks per month100
- Steps on the free plan2 (trigger + action)
- Premium appNo
- Clarify triggers that wait for a timerNone, all 3 are instant
You pay in tasks, one per action that goes through. An action that fails is not counted. A Zap with three actions uses three tasks per run. The free plan gives you 100 tasks a month and Zaps of two steps only, one trigger and one action. Add a filter, a search such as Find Company or a second action, and the Zap becomes multi-step, which needs a paid plan. A few apps and actions take more than one task when they complete.
Connect Clarify to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Clarify account linked once, then reused by every step that touches Clarify.
- 02
Pick Clarify
Type Clarify in the search box of the dialog, select it, then click Add connection. You need a Clarify account, plus access to any records you do not own and want the Zap to work on.
- 03
Sign in and grant access
A new tab opens on Clarify. Sign in with the account the Zap should act as, then allow Zapier to access it. Every Zap you build afterwards can pick this connection.
Your first Clarify Zap: a comment on every company added to a list
GoalWhen a company joins a Clarify list, leave a comment on it so the team knows why it is there.
- 01
Build: choose the trigger
Start a new Zap, pick Clarify, then Record Added to List. Set Object to Company and choose the list you care about. The trigger only listens to that one list.
- 02
Test the trigger
Add a company to that list in Clarify, then run the test. Zapier brings back the three most recent items, so you map fields from a real record.
- 03
Build: add Create Comment
Add Clarify again as the action and choose Create Comment. Set Object to Company, map the record's ID from the trigger and write the message.
- 04
Test the action
Run the action test and open the company in Clarify. The comment should be there. If it landed on the wrong record, fix the ID mapping now.
- 05
Publish
Click Publish to switch the Zap on. From now on, each company added to the list gets its comment right away, on any plan.
Clarify triggers: what starts a Zap
3 events start a Zap when something happens in Clarify, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.
Record Added to List
Instant triggerIn Zapier“Triggers when a record is added to a list.”
Starts the Zap whenever a record is placed in one of your Clarify lists. You choose the kind of record and the exact list, so the Zap only wakes up for that list and ignores everything else happening in the CRM.
Record Created
Instant triggerIn Zapier“Triggers when a new record is created.”
Fires each time a brand new record appears in Clarify, of the type you set in the trigger. Think of it as the doorbell for fresh people or companies entering the CRM.
Record Updated
Instant triggerIn Zapier“Triggers when a record is updated.”
Runs the Zap whenever an existing record of the chosen type changes. It reacts to edits, not to creation, which makes it the right entry point for follow-ups that depend on what a rep just changed.
Clarify actions: what a Zap can do in your CRM
Clarify gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Label to Record
ActionIn Zapier“Adds one or more labels to a record.”
Puts one or more labels on a record, so you can sort and segment it later inside Clarify.
Create Comment
ActionIn Zapier“Creates a comment.”
Posts a written comment on a person or company, with the text you compose from earlier steps.
Create Record
ActionIn Zapier“Creates a new record.”
Adds a new record to Clarify, of the type you set in Object. Object is the one required field.
Get Meeting Recording Transcript
ActionIn Zapier“Retrieves the transcript of a meeting recording.”
Fetches the transcript of a recorded meeting, so a later step can store or use the text.
Remove Label From Record
ActionIn Zapier“Removes one or more labels from a record.”
Takes one or more labels off a record, the mirror of the step above.
Delete Record
ActionIn Zapier“Deletes a record.”
Removes a record from Clarify for good, picked by its type (Object) and its Record ID, both required.
Update Record
ActionIn Zapier“Updates a record.”
Changes the fields of a record that already exists. You give it the type (Object) and the Record ID, both required.
Clarify searches: look before you create
5 search steps look for data that already exists in Clarify, so a later step can use it.
A search step finds something already in Clarify and hands it to the steps that follow. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Some action fields also offer + Add search step, which inserts the search right before and wires its result in. Whether a search wants an exact match or something close is up to Clarify, not Zapier. Every search exposes three settings worth understanding before you publish.
Find Company
SearchFind or createIn Zapier“Finds a Company by its domain name or creates one if it isn't found.”
Looks up a company by its domain name, which is required.
Find Meeting
SearchIn Zapier“Finds a meeting by its ID.”
Retrieves a meeting from Clarify by its ID, so later steps can use it.
Find Person
SearchFind or createIn Zapier“Finds a Person by their email address, name, or LinkedIn, or creates one if it isn't found.”
Finds a person by email address, name or LinkedIn profile.
Find Record
SearchIn Zapier“Finds a record by its ID.”
Pulls a record of any type when you already know its ID, with Object and Record ID both required.
Find User
SearchIn Zapier“Finds a workspace user by their email address or phone number.”
Finds a member of your Clarify workspace by email address or phone number.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. Switch it on and the Zap keeps going, empty-handed.
- Create X if it doesn't exist yet?Tick it and the search becomes a find-or-create: it drops the setting above and asks for the fields needed to create the missing record.
- If multiple search results are found?Three ways out when several records match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When a Clarify Zap breaks
Zapier attaches no help article to Clarify and lists no specific limit for it. What breaks is the general behaviour of Zaps, which hits a CRM harder than most tools.
Four cases come back over and over. If you are stuck on one of them, our Zapier troubleshooting service exists for exactly that.
Old records never come through
A Zap reacts only to what happens after you publish it. Records already in your lists or already created stay untouched. Moving the backlog is a separate job.The Zap triggers itself in a loop
Watch Record Updated and run Update Record on the same type, and each update sets the trigger off again. Tasks vanish fast. A filter breaks the loop.A bulk import gets held back
Import hundreds of records at once and Zapier's flood protection can pause the Zap rather than fire it for every one.The action fails on a missing ID
Most Clarify actions need a Record ID. If the trigger or search did not supply one, the step fails. A failed action costs no task, but the work is not done.
Need help automating Clarify with Zapier?
A person reads every message.



