Clepher Zapier integrationAutomate Clepher with Zapier.
The Clepher Zapier integration gives you 2 triggers, 6 actions and 2 searches to move chatbot subscribers in and out of your other tools. Both triggers are instant, the app works on the free plan, and this page shows what each piece does and what it costs.
Verified Trustpilot reviews · AI, automation & growth agency
What the Clepher Zapier integration actually does for you
Clepher builds AI chatbots for your page. Plugging it into Zapier means two things: a new subscriber or a newly tagged subscriber can start an automation, and that automation can tag people, fill their custom fields, or push a flow or a single card to them without you opening the Clepher dashboard.
Three outcomes cover most of what people build with it. A labelled audience: New Subscriber fires, Attach Tag sorts the person into the right segment straight away. A follow-up that sends itself: a tag lands on someone, and Send Flow pushes the matching conversation to them. A cleaner profile: Set Custom Field writes a value on the subscriber so your later flows can branch on it.
What Zapier does not do here matters just as much. It cannot pick up subscribers who joined before your Zap was switched on. It has no trigger for a flow or a card being sent, and no action that creates a flow: you still design conversations inside Clepher. Every action needs the subscriber's profile ID, so a Zap that starts in another tool usually needs a search step first, and that makes it multi-step.
The Clepher Make integration covers the same app on Make, and Make vs Zapier is there if you are still choosing a platform.
Zapier words, in one minute
Eight terms come back on this page. Here they are in plain English, once, so the rest reads without a dictionary.
- Zap
- The automation you build on Zapier: one starting event, then one or more steps that run each time that event happens.
- Trigger
- The event that starts the Zap, such as a new Clepher subscriber. Once the Zap is on, Zapier sits and waits for it.
- Action
- What the Zap does after it starts: the step that tags, writes or sends something on your behalf.
- Task
- The unit Zapier bills. One action that completes successfully is one task, and your plan counts those.
- Polling vs instant
- Polling means Zapier checks the app on a timer. Instant means the app calls Zapier itself the second the event happens. Clepher's triggers are instant.
- Filter
- A step that lets the Zap continue only when what arrived meets a condition you set, and stops it quietly otherwise.
- Search step
- A step that looks up something already in an app, like an existing subscriber, so later steps can use what it found.
- Connection
- Your Clepher account linked to Zapier once, then reused by every step in every Zap that touches Clepher.
What a Clepher Zap really costs
The trigger is free. Zapier never bills for the event that starts a Zap, and checking for new data costs nothing either.
- Free plan100 tasks a month
- Steps on the free plan1 trigger + 1 action
- Clepher triggersInstant, plan grid does not apply
- Premium appNo
You pay in tasks, one per action that works. A Zap that tags a subscriber then sends a flow uses two tasks per run; a failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two-step Zaps: one trigger, one action. Add a second action, a filter or a search and the Zap becomes multi-step, which needs a paid plan. Clepher is not a premium app, so it runs on the free plan.
Connect Clepher to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. In the dialog that opens, search for Clepher by name and pick it from the results list.
- 02
Sign in to Clepher
Click Add connection. A new tab opens on Clepher's side, where you sign in with the account that owns the chatbot you want to automate. You need an account on the app, plus access to any page you do not own yourself.
- 03
Grant access
Allow Zapier to use the account. From then on the connection is stored once and every Clepher step in every Zap reuses it, so you never sign in again for the next automation.
Your first Clepher Zap: tag new subscribers, then greet them
GoalEvery new subscriber gets a tag and a welcome flow, without anyone touching the dashboard.
- 01
Build: pick the trigger
Create a Zap, choose Clepher as the app and New Subscriber as the event that starts it, then select the connection you just made.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent subscribers on the account, so you map fields on a real person, not on a blank sample.
- 03
Add Attach Tag
Add a Clepher step with Attach Tag. Fill the Profile field with the subscriber's profile ID: look for it in the trigger's test result first, then pick the tag that marks new people.
- 04
Add Send Flow
Add a second Clepher step with Send Flow, map the same profile ID and enter your welcome flow's ID. Two actions make this a multi-step Zap, so a paid plan.
- 05
Test, then Publish
Test each step once and read what came back. When both actions look right, click Publish to switch the Zap on for every subscriber from now on.
Clepher triggers: what can start a Zap
2 events start a Zap when something happens in Clepher, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
New Subscriber
Instant triggerIn Zapier“Triggers when a new user subscribes to your page.”
Starts your Zap the moment someone subscribes to your page through the Clepher bot. The subscriber arrives in the Zap ready to be tagged, enriched or copied into another tool, which makes it the natural entry point for any onboarding sequence.
New Tagged Subscriber
Instant triggerIn Zapier“Triggers when a new tag is attached to a subscriber.”
Reacts each time a new tag is attached to a subscriber, whatever the tag. Tags become signals: a person reaching a certain point in a conversation can set off work outside Clepher.
Clepher actions: what your Zap can do
Clepher gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Attach Tag
ActionIn Zapier“Attach a tag to a subscriber.”
Puts a tag on a subscriber so your Clepher segments and flows can treat them differently. You give it a profile ID and the tag.
Detach Tag
ActionIn Zapier“Detach a tag from a subscriber.”
Takes a tag back off a subscriber, the clean reverse of tagging. Same two inputs: profile ID and the tag to remove.
Send Card
ActionIn Zapier“Send a card to a subscriber.”
Delivers a single card from a flow instead of the whole sequence, which suits a short nudge. Three IDs are required: the subscriber's profile, the flow, and the card inside it.
Send Flow
ActionIn Zapier“Send a flow to a subscriber.”
Pushes an entire Clepher conversation to one subscriber from outside the dashboard. It needs the subscriber's profile ID and the flow's ID.
Set Custom Field
ActionIn Zapier“Set a custom field for a subscriber.”
Writes a value into one of the subscriber's custom fields, so later flows can personalise or branch on it. It asks for the profile ID, the field name and the value.
Unset Custom Field
ActionIn Zapier“Unset a custom field for a subscriber.”
Clears a custom field on a subscriber, leaving it empty rather than holding a stale value. You only pass the profile ID and the field name.
Clepher searches: finding a subscriber first
2 search steps look for data that already exists in Clepher, so a later step can use it.
Every Clepher action needs a profile ID. When your Zap starts in another app, that ID is not there yet, so a search step fetches it. Searches sit at the bottom of the Action event list, under SEARCH, and some fields offer + Add search step to insert one right before the current step.
Find Subscriber by Evidence
SearchIn Zapier“Finds a subscriber by evidence”
Looks a subscriber up from any piece of stored data that identifies them, so a Zap starting elsewhere can reach the right person in Clepher.
Find Subscriber by ID
SearchIn Zapier“Finds a subscriber by profile ID”
Fetches a subscriber when you already hold the profile ID, which is handy to check the person still exists before writing to them.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nobody stops the Zap there and the dependent steps are skipped. Switch it on and the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into find-or-create. Clepher offers no such variant, so you will not see it on these two searches.
- If multiple search results are found?Three ways out when several people match: keep the first one (the default), stop the Zap, or pass all of them to the next steps.
When a Clepher Zap breaks
Zapier attaches no help article to Clepher, so the problems below come from how Zapier itself behaves. They are the ones that cost tasks or leave people out.
Read these before you publish. Each one has a simple guard, and the Zapier troubleshooting page goes further when a Zap still misbehaves.
Old subscribers are never picked up
A Zap only reacts to what happens after it is switched on. Everyone who subscribed before you hit Publish stays outside it; moving that backlog is a separate job.A tag Zap that sets itself off
If a Zap triggered by New Tagged Subscriber attaches a tag, it can wake its own trigger again and again, burning through your task count fast.A bulk import floods the trigger
When a huge batch of subscribers arrives at once, after an import or a migration, Zapier's flood protection can hold the Zap back.A search that finds nobody
By default a search with no result stops the Zap and skips the steps after it. Change the setting if the Zap should carry on.
Need help automating Clepher with Zapier?
A person reads every message.
