List Help Scout Conversations: Help Scout 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
Mailbox ID mailbox	string	Required	Mailbox ID. Example: 12345
Status status	options	Optional	Status. Options: Active, Pending, Closed, All
Page page	string	Optional	Page. 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.

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. Tiny Command handles Help Scout's rate limits automatically so you don't have to throttle manually.

More actions