Get Conversation: Crisp action

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

{
  "meta": {
    "email": "john@example.com",
    "nickname": "John Doe"
  },
  "state": "resolved",
  "session_id": "session_abc",
  "is_verified": true
}

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

FAQ

Questions about Get Conversation.

What does the Get Conversation action do in Crisp?

Returns the conversation with message history, customer profile, and metadata. The standard lookup for workflows that received a conversation ID via webhook and need richer context.

What inputs does Get 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 Get Conversation support batch operations?

Yes. Run Get 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