Reply to Help Scout Conversation: 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
Conversation ID conversation_id	string	Required	Conversation ID. Example: 123
Reply Text text	string	Required	Reply Text
New Status status	options	Optional	New Status. Options: Active, Pending, Closed

Sample request

{
  "conversation_id": "e.g. 123",
  "text": "{{trigger.text}}",
  "status": "{{trigger.status}}"
}

Returns

{
  "success": true
}

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

FAQ

Questions about Reply to Help Scout Conversation.

What does the Reply to Help Scout Conversation action do in Help Scout?

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.

What inputs does Reply to Help Scout Conversation require?

Required: Conversation ID, Reply Text. 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 Reply to Help Scout Conversation support batch operations?

Yes. Run Reply to Help Scout Conversation 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