Start free
ActionHelp ScoutUpdated June 2026

How do I list Help Scout conversations?

Short answer: You can list help scout conversations in Help Scout by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Help Scout List Help Scout Conversations action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Help Scout Conversations in Help Scout — start free All 4 Help Scout actions
List Help Scout Conversations in Help Scout — 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.

FieldTypeRequiredDescription
Mailbox ID
mailbox
stringRequiredMailbox ID. Example: 12345
Status
status
optionsOptionalStatus. Options: Active, Pending, Closed, All
Page
page
stringOptionalPage. e.g. "1"
Sample request
{
  "mailbox": "e.g. 12345",
  "status": "{{trigger.status}}",
  "page": "1"
}
Returns
{
  "page": {
    "totalElements": 42
  },
  "_embedded": {
    "conversations": [
      {
        "id": 123,
        "status": "active",
        "subject": "Billing issue",
        "mailboxId": 12345
      }
    ]
  }
}

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

Triggered by

Apps that pair well as the trigger for List Help Scout Conversations.

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

Gmail → Help Scout
1 Gmail triggers
Slack → Help Scout
13 Slack triggers
Google Sheets → Help Scout
2 Google Sheets triggers
HubSpot → Help Scout
18 HubSpot triggers
FAQ

Questions about List Help Scout Conversations.

What does the List Help Scout Conversations action do in Help Scout?
Paginated conversations with filters by mailbox, status, tag, assignee, customer. For triage workflows and capacity-planning dashboards.
What inputs does List Help Scout Conversations require?
Required: Mailbox 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 Help Scout 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 Help Scout Conversations support batch operations?
Yes. Run List Help Scout Conversations inside a Loop node to process arrays. TinyCommand handles Help Scout's rate limits automatically so you don't have to throttle manually.
More actions

Other Help Scout actions.

Action
Create Help Scout Conversation
Files a new conversation in a mailbox with customer, subject, body, channel. For "external support channel → file as Help Scout conversation" workflows.
Action
List Help Scout Mailboxes
Returns every mailbox in the connected account. Useful for resolving mailbox IDs at workflow setup and for cross-mailbox routing rules.
Action
Reply to Help Scout Conversation
Posts a customer-facing reply or internal note. For "AI-assisted draft → posted as internal note for the agent to review and send" or for full-auto reply workflows on routine ticket types.
List Help Scout Conversations in Help Scout — start free