ActionHelp ScoutUpdated May 2026

What Help Scout mailboxes exist?

Short answer: Drop the "Help Scout → List Help Scout Mailboxes" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 4 Help Scout actions

Sample request

{}

Returns

{
  "_embedded": {
    "mailboxes": [
      {
        "id": 12345,
        "name": "Support",
        "email": "support@company.com"
      }
    ]
  }
}

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 Mailboxes.

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

Google Sheets → Help Scout

2 Google Sheets triggers

HubSpot → Help Scout

18 HubSpot triggers

FAQ

Questions about List Help Scout Mailboxes.

What does the List Help Scout Mailboxes action do in Help Scout?

Returns every mailbox in the connected account. Useful for resolving mailbox IDs at workflow setup and for cross-mailbox routing rules.

What inputs does List Help Scout Mailboxes require?

List Help Scout Mailboxes 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 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 Mailboxes support batch operations?

Yes. Run List Help Scout Mailboxes 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