Short answer: Drop the "Help Scout → Create Help Scout Conversation" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
Triggered by anything in the catalog. Free tier available. No credit card.