List Conversations: 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
Page page_number	string	Optional	Page. e.g. "1"

Sample request

{
  "page_number": "1"
}

Returns

{
  "data": [
    {
      "meta": {
        "email": "customer@example.com",
        "nickname": "John"
      },
      "state": "unresolved",
      "session_id": "sess123",
      "is_verified": true
    }
  ]
}

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

FAQ

Questions about List Conversations.

What does the List Conversations action do in Crisp?

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

What inputs does List Conversations require?

List Conversations has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List Conversations support batch operations?

Yes. Run List Conversations 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