Crisp currently provides 2 triggers that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect support activity to the full account history and the next internal action.
New Contact Created
Triggers when a new contact is added.
New Conversation Created
Triggers when a new conversation is started.
Add Note to Conversation
Adds an internal note to a conversation.
Create Conversation
Creates a new conversation.
Create/Update Contact
Creates a new contact or updates an existing contact.
Change Conversation State
Updates the state of a conversation.
Find Conversation
Searches for conversations matching the specified criteria.
Find User Profile
Finds a user profile by email address.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Crisp event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Contact Created
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Crisp action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Add Note to Conversation
Combine Crisp with another integration and Coherence records to connect support activity to the full account history and the next internal action.
Starts with
New Contact Created
Finishes with
Add Note to Conversation, then preserve the outcome in Coherence
The exact authentication fields depend on Crisp. The workflow structure stays straightforward:
Authorize the Crisp account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Crisp or provide a complementary trigger or action.
Crisp currently provides 2 triggers that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect support activity to the full account history and the next internal action.
Crisp currently lists 2 triggers and 7 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Crisp triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
