ActionHelp ScoutUpdated September 2026

How do I create a Help Scout conversation?

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

Create Help Scout Conversation in Help Scout — start free All 4 Help Scout actions

Create Help Scout Conversation 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.

Field	Type	Required	Description
Mailbox ID mailboxId	string	Required	Mailbox ID. Example: 12345
Subject subject	string	Required	Subject. Example: Customer needs help with billing
Customer Email customer_email	string	Required	Customer Email. e.g. "customer@example.com"
Message Body text	string	Required	Message Body
Status status	options	Optional	Status. Options: Active, Pending, Closed

Sample request

{
  "mailboxId": "e.g. 12345",
  "subject": "e.g. Customer needs help with billing",
  "customer_email": "customer@example.com",
  "text": "{{trigger.text}}",
  "status": "{{trigger.status}}"
}

Returns

{
  "success": true
}

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

Triggered by

Apps that pair well as the trigger for Create Help Scout Conversation.

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 Create Help Scout Conversation.

What does the Create Help Scout Conversation action do in Help Scout?

Files a new conversation in a mailbox with customer, subject, body, channel. For "external support channel → file as Help Scout conversation" workflows.

What inputs does Create Help Scout Conversation require?

Required: Mailbox ID, Subject, Customer Email, Message Body. 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 run history shows the failed step with its input and the error message Help Scout returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create Help Scout Conversation support batch operations?

Run Create Help Scout Conversation inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Help Scout's rate limits.

More actions

Other Help Scout actions.

Action

List Help Scout Conversations

Paginated conversations with filters by mailbox, status, tag, assignee, customer. For triage workflows and capacity-planning dashboards.

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.

Create Help Scout Conversation in Help Scout — start free