Skip to content
ActionDriftUpdated May 2026

How do I list Drift conversations?

Short answer: Drop the "DriftList Drift Conversations" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Limit
limit
stringOptional
Sample request
{
"limit": "{{trigger.limit}}"
}
Returns
{
"data": [
{
"id": 1234,
"status": "open",
"contactId": 42
}
]
}

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

Triggered by

Apps that pair well as the trigger for List Drift Conversations.

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

FAQ

Questions about List Drift Conversations.

What does the List Drift Conversations action do in Drift?
Paginated conversations with filters by status and assignee. Useful for triage workflows or for "all unassigned conversations from last hour" capacity awareness.
What inputs does List Drift Conversations require?
List Drift 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 Drift 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 Drift Conversations support batch operations?
Yes. Run List Drift Conversations inside a Loop node to process arrays. Tiny Command handles Drift's rate limits automatically so you don't have to throttle manually.
More actions

Other Drift actions.

Send list drift conversations from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.