Crisp Zapier integrationAutomate Crisp with Zapier.
The Crisp Zapier integration gives you 8 triggers, 8 actions and 2 searches. Below: what each one does, what it costs on your plan, how to link your workspace and the traps to know before your support inbox starts running on its own.
Verified Trustpilot reviews · AI, automation & growth agency
What the Crisp Zapier integration does for a support team
Crisp gathers your customer conversations (live chat, email, Messenger, Twitter, SMS) in one inbox. Linking it to Zapier lets other tools react the second a conversation starts or a contact changes, and lets them write back into Crisp: notes, replies, segments, events.
Here is the strongest argument first: every one of the 8 Crisp triggers is instant. Crisp tells Zapier the moment something happens, so even on the free plan nothing waits for a 15-minute check. That changes what you can build.
Three outcomes come up again and again. Conversations sorted before anyone reads them: New Conversation starts the Zap, Add Segments to Conversation tags it with the segment your team sorts by. Context where agents work: Send Note Message drops a note message inside the thread, right where the agent will read it. Campaigns driven by what happens elsewhere: Add a User Event fires an automated Crisp campaign from a signal in another tool.
What Zapier does not do here: there is no action to delete a conversation or a contact, the searches only look things up by query or email, and nothing that happened before you switched the Zap on is replayed. If you are still choosing a platform, the Crisp Make integration covers the same inbox from Make, and n8n vs Zapier puts the two side by side.
Zapier words, in plain English
Seven terms carry the whole page. A quick read and you are set.
- 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 it to happen.
- Action
- What the Zap does once started: the step that writes, sends or moves something in an app on your behalf.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan allowance counts those and nothing else.
- Instant vs polling
- An instant trigger is pushed by the app the moment the event happens. A polling one is checked by Zapier on a timer instead.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
- Search step
- A step that looks up something already stored in an app, so the steps after it can use what it found.
What a Crisp Zap really costs
Crisp is not a premium app on Zapier, so it runs from the free plan. You pay in tasks, and only for actions that work.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps only
- Crisp triggersAll 8 instant, whatever the plan
- Failed actionNot counted
The trigger never costs a task. Each action that succeeds counts as one; one that fails is not counted. A Zap with three actions uses three times what a one-action Zap uses. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. A second action, a filter or a search turns it into a multi-step Zap, which needs a paid plan. The interval grid below applies to polling triggers only; Crisp's triggers are all instant, so it does not slow them down.
Connect Crisp to Zapier in three steps
- 01
Open your connections
In Zapier, go to the Apps page and click + Add connection. A connection is your Crisp account linked once, then reused by every Zap that uses Crisp from then on.
- 02
Find Crisp
Type Crisp in the dialog's search box, select it, then click Add connection. You need a Crisp account already in place, since Zapier only links an existing one.
- 03
Sign in and grant access
Log in to Crisp in the tab that opens and grant Zapier access. If the Zap will touch a workspace you do not own, check first that your user can read or write there.
Your first Zap: tag and annotate every new conversation
GoalWhen a conversation opens in Crisp, add a segment to it and leave a private note for the agent who picks it up.
- 01
Pick the starting event
Create a Zap, choose Crisp and the New Conversation event, then select the connection you added. This trigger is instant, so the editor marks it with a lightning bolt.
- 02
Test on real data
Run the trigger test. Zapier brings back the three most recent conversations of your account, so you map fields on a real one.
- 03
Add the segment
Add Add Segments to Conversation, fill Conversation ID with the conversation identifier you spot in the trigger test data (if it is not there, put Search for Conversation in front) and type the segment your team uses for new threads.
- 04
Leave the note
Add Send Note Message with the same Conversation ID and a short line telling the agent what to check first before replying.
- 05
Test and publish
Test both actions and check the thread in Crisp, then Publish. Two actions make it a multi-step Zap, which needs a paid plan.
Crisp triggers on Zapier
8 events start a Zap when something happens in Crisp, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.
Edited Contact
Instant triggerIn Zapier“Triggers when a contact is edited.”
Fires whenever a contact profile in Crisp is changed. It lets other tools catch the fresh version of a person instead of a stale copy.
Message Sent
Instant triggerIn Zapier“Triggers when an operator sends a message”
This one reacts to your side of the chat: it starts the Zap each time an operator sends a message to a customer.
Message Incoming
Instant triggerIn Zapier“Triggers when a visitor sends a message.”
The customer-side counterpart: the Zap starts every time a visitor writes to you. It is one of the triggers Zapier puts forward for Crisp.
New Contact
Instant triggerIn Zapier“Triggers when a new contact is created.”
Goes off when a new contact is created in Crisp, which makes it the natural start of any onboarding flow.
New Conversation
Instant triggerIn Zapier“Triggers when a new conversation is created.”
Starts the Zap when a brand new conversation opens. This is the natural entry point for routing and triage.
Conversation Custom Data Updated
Instant triggerIn Zapier“Triggers when custom data is added or removed in a conversation.”
Crisp lets you attach custom data to a conversation. This trigger fires whenever a piece of it is added or removed.
Conversation Segments Updated
Instant triggerIn Zapier“Triggers when a segment is added or removed in a conversation.”
Reacts when a segment is added to or removed from a conversation. This is how a segment set by hand becomes the start of an automation.
Conversation Status Change
Instant triggerIn Zapier“Triggers when a conversation is (un)resolved.”
Fires when a conversation is resolved, or reopened. It marks the end, or the unexpected return, of a support case.
Crisp actions on Zapier
Crisp gives you 8 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Segments to Conversation
ActionIn Zapier“Add segments to a conversation”
Tags a conversation with one or more segments, so it is sorted without anyone opening Crisp.
Create/Update Contact
ActionIn Zapier“Creates/Update a contact”
Adds a person to Crisp, or refreshes their profile if it exists. Email and name are both required.
Create Conversation
ActionIn Zapier“Creates a conversation”
Opens a new thread in Crisp with a first message. It needs the user email, user name, who the message is from, and the message itself.
Add a User Event
ActionIn Zapier“Triggers an automated campaign”
Records an event on a person in Crisp, which is what launches an automated campaign there. Email and event name are required.
Send Note Message
ActionIn Zapier“Send a note message in a conversation”
Leaves a note message in a conversation for whoever handles it next. Conversation ID and note content are required.
Send Operator Text Message
ActionIn Zapier“Send a text message to a user”
Posts a reply to the customer as an operator, inside an existing conversation. Conversation ID and message content are required.
Send User Text Message
ActionIn Zapier“Send a text message as the user”
Writes into a conversation as if the user had typed it. It takes the same two required fields as the operator version.
Change Conversation State
ActionIn Zapier“Update the state of a conversation”
Moves a conversation to another state, resolved for instance, without anyone clicking in Crisp. Only the Conversation ID is required.
Looking things up in Crisp before you act
2 search steps look for data that already exists in Crisp, so a later step can use it.
A search step finds something that already exists so the actions after it can use it. Crisp searches sit at the bottom of the Action event list, under SEARCH, and some fields offer + Add search step to slot one in just before. How close the match must be is Crisp's call, not Zapier's.
Search for Conversation
SearchIn Zapier“Search previous Crisp conversations using a search query (an email, username, or word).”
Looks through past Crisp conversations with a query: an email, a username or a word. It is the way to reach a thread when the Zap starts in another tool.
Search for a Profile
SearchIn Zapier“Search previous Crisp people profile using an email address.”
Finds a person's profile in Crisp from their email address, so later steps can use what Crisp knows about them.
The three settings every search exposes
- Successful if no search results are found?On its default, a search that finds nothing stops the Zap and skips the steps relying on it. Turn it on and the Zap continues with empty values.
- Create X if it doesn't exist yet?On apps that offer it, this box turns a search into a find-or-create. Neither Crisp search has that variant, so a missing item has to be created by its own action.
- If multiple search results are found?Three ways out when several items match: keep the first one, the default, stop the Zap, or hand all of them on at once.
When a Crisp Zap breaks
Zapier links no help article and no app-specific limit to Crisp. The failures that matter are the general ones, and one of them is especially easy to trigger on a chat tool.
Four cases to know before you publish. If something still goes wrong, start from the Zapier troubleshooting page.
Replies that answer themselves
Message Sent plus Send Operator Text Message, or Conversation Segments Updated plus Add Segments: the Zap writes where it listens and runs in a loop, eating tasks.Past conversations stay put
A Zap only reacts to what happens after you switch it on. Threads and contacts already in Crisp are never sent; moving that history is a separate job.A burst of events gets held
After a bulk import of contacts or a migration, a trigger can receive a huge batch at once. Zapier's flood protection may hold it back rather than run it all.Actions with no conversation
Notes, replies, segments and state changes all require a Conversation ID. When no earlier step provides one, the action cannot run; Search for Conversation fills the gap.
Need help automating Crisp with Zapier?
A person reads every message.



