ActionCrispUpdated September 2026

How do I fetch a Crisp conversation?

Short answer: You can get conversation in Crisp by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Crisp Get Conversation action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Conversation in Crisp — start free All 4 Crisp actions

Get Conversation in Crisp — start free

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.

Triggered by

Apps that pair well as the trigger for Get 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 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 run history shows the failed step with its input and the error message Crisp returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Conversation support batch operations?

Run Get Conversation inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Crisp's rate limits.

More actions

Other Crisp actions.

Action

List Conversations

Paginated conversations with filters by state, segments, channel. Useful for triage workflows ("show me open conversations assigned to no one") and for capacity reporting.

Action

Resolve Conversation

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.

Action

Send Message

Posts a customer-facing reply or an internal team note (type=note). Routes via the conversation's original channel by default. For posting AI context as internal note or for automated replies on low-complexity tickets.

Get Conversation in Crisp — start free