ActionCrispUpdated May 2026

How do I mark a Crisp conversation as resolved?

Short answer: Drop the "Crisp → Resolve Conversation" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 4 Crisp actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Session ID sessionId	string	Required	Session ID

Sample request

{
  "sessionId": "{{trigger.sessionId}}"
}

Returns

{
  "state": "resolved"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Resolve Conversation.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Crisp

2 Google Sheets triggers

HubSpot → Crisp

18 HubSpot triggers

FAQ

Questions about Resolve Conversation.

What does the Resolve Conversation action do in Crisp?

Transitions a conversation to resolved state — the standard close-out. Useful for "AI judge agrees customer is satisfied → auto-resolve" workflows or for bulk-resolve maintenance on inactive conversations.

What inputs does Resolve Conversation require?

Required: Session ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Crisp returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Resolve Conversation support batch operations?

Yes. Run Resolve Conversation inside a Loop node to process arrays. Tiny Command handles Crisp's rate limits automatically so you don't have to throttle manually.

More actions