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.
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 |
{"mailboxId": "e.g. 12345","subject": "e.g. Customer needs help with billing","customer_email": "customer@example.com","text": "{{trigger.text}}","status": "{{trigger.status}}"}
{"success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.