Connect Crisp to other apps with Zapier so a new contact, conversation, or segment can start an action elsewhere.

You can send leads to your CRM, notify teammates, or update Crisp from another service without building a custom integration. Connect your accounts, choose the right event, and test your first Zap below.

Connect Zapier to Crisp

To connect your workspace:

1. In Crisp, open 🧩 Plugins → Zapier and install the plugin.
2. Click Generate new token in the plugin settings. You’ll use this token to authenticate Crisp in Zapier.
3. Go to Zapier Connections and click Add Connection.
4. Search for Crisp and select the app.
5. Paste the Crisp token and click Yes, continue.

Crisp is now connected to Zapier, and you can start creating Zaps.

Create your first Zap

Zapier lets you combine triggers, actions, and searches. The exact list may evolve over time, but the Crisp integration includes the main events and actions needed to automate common workflows.

Choose the trigger according to the outcome you need. New Conversation fits an alert for a newly started conversation; Message Incoming fits an action that should run for each incoming message, including messages in an existing conversation. For a CRM handoff, start with New Contact, then map the contact fields required by the receiving app.

To build that first Zap:

1. Create a Zap in Zapier and choose Crisp as the trigger app.
2. Select New Contact and the Crisp connection you configured above.
3. Use a recognizable test contact to check which fields the trigger provides.
4. Choose your CRM as the action app, then map the contact email, name, and other required fields to its create-or-update action.
5. Test the action and check the resulting record in the CRM before enabling the Zap.

Use the event and action lists below to adapt this pattern to a different support task.

Common Crisp triggers

Crisp triggers can include:

• Message Incoming → when a visitor sends a message
• Message Sent → when an operator sends a message
• New Contact → when a contact is created
• Edited Contact → when a contact is updated
• New Conversation → on the first incoming message detected in a conversation created less than a minute earlier
• Conversation Custom Data Updated → when custom data is added or removed from a conversation
• Conversation Segments Updated → when a segment is added or removed from a conversation
• Conversation Status Change → when a conversation state changes

Common Crisp actions

Crisp actions can include:

• Create/Update Contact → create or update a contact in Crisp
• Add a User Event → add an event to an existing contact, which can trigger an event-based campaign configured in Crisp
• Create Conversation → create a new conversation and send a message
• Add Segments to Conversation → add segments to an existing conversation
• Change Conversation State → set a conversation to resolved, unresolved, or pending
• Send Note Message → add a private note to a conversation
• Send Operator Text Message → send a text message to a user with an existing conversation

Common Crisp searches

Crisp searches can include:

• Search for Conversation → search previous conversations by email, username, or keyword
• Search for a Profile → search for a Crisp profile by email address

For actions on an existing conversation, map its Conversation ID (session_id) from the trigger or a search step. For Create/Update Contact and Add a User Event, provide the contact’s email address.

Before enabling a Zap, test it with one contact or conversation and inspect the result in the destination app. Confirm that the mapped email, name, or conversation reference belongs to the test record. If the action sends a message or changes a conversation, also check the customer-facing result or updated conversation state in Crisp.

Zap examples using Crisp

Choose an example according to what should start the automation: a new profile, a new conversation, or a customer's signup choice. Check that the trigger reflects that event before reusing a template, since a contact being created is not the same event as a customer agreeing to join a mailing list.

Link Crisp with a CRM

Use the New Contact trigger to send new Crisp contacts to a CRM such as Pipedrive or Salesforce.

Notify your team about new conversations

Use the New Conversation trigger to send an SMS notification for a newly started Crisp conversation. It does not run when an older conversation is reopened or when a conversation is created without an incoming message. Use Message Incoming when your alert should also cover existing conversations.

Include enough context in the alert for the receiving teammate to find the request, such as a conversation link when the trigger provides it. Test with a new conversation and check that the alert reaches the intended recipient.

Add new users to a mailing list

Use Conversation Segments Updated to react to a newsletter-signup segment. Filter for the segment you need, then use a Mailchimp action that adds or updates the subscriber in the intended audience. The trigger also runs when segments are removed, so check the conversation’s current segments before subscribing anyone.

The template below uses New Contact, so change its trigger and add the signup filter if you follow the segment-based example. Check the resulting audience subscription with a test contact before enabling the Zap.

Updated on: 03/11/2026