Help Scout trigger

Overview

The Help Scout Trigger node starts a workflow when events occur in Help Scout. It listens for webhook notifications from Help Scout covering conversations, customers, and satisfaction ratings. Supported events include conversation creation, assignment, status changes, merges, moves, tag changes, agent replies, customer replies, notes, customer creation, and satisfaction rating receipt. Verifies webhook authenticity using HMAC-SHA1 signature verification against the x-helpscout-signature header. Outputs the full event payload from Help Scout.

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires Help Scout OAuth2 credentials. See the Credentials Guide for setup instructions.

Parameters

Parameter	Type	Required	Default	Description
Help Scout Account	credential	No	—	Connect your Help Scout account via OAuth2.
Events	multiOptions	Yes	[]	Which Help Scout events to listen for.
				Options: convo.assigned, convo.created, convo.deleted, convo.merged, convo.moved, convo.status, convo.tags, convo.agent.reply.created, convo.customer.reply.created, convo.note.created, customer.created, satisfaction.ratings

Output Data

Each accepted delivery produces one output item. The Help Scout event payload is placed directly on the item alongside three metadata fields:

{
  "id": 0,
  "type": "convo.created",
  "folderId": 0,
  "previousFolderId": 0,
  "number": 0,
  "status": "active",
  "subject": "",
  "mailbox": { "id": 0, "name": "" },
  "assignee": { "id": 0, "email": "", "first": "", "last": "" },
  "customer": { "id": 0, "email": "", "firstName": "", "lastName": "" },
  "tags": [],
  "threads": [],
  "_trigger": "helpscout_webhook",
  "_timestamp": "2026-01-01T00:00:00.000Z",
  "_webhookEvent": "convo.created"
}

• _trigger — always helpscout_webhook.
• _timestamp — ISO 8601 timestamp of when the delivery arrived.
• _webhookEvent — the event name, copied from the payload’s type field, or unknown when it is absent.

The remaining fields come straight from Help Scout and vary by event: conversation events carry conversation fields such as id, number, status, subject, mailbox, assignee, customer, tags and threads; customer.created carries the customer record; satisfaction.ratings carries the rating. Reference them downstream by expression, for example {{ $json.customer.email }} or {{ $json.subject }}.

Deliveries whose HMAC-SHA1 signature does not match the registered secret are rejected with 401 and never start the workflow.

Example Configuration

Fire on new conversations:

{
  "type": "helpscout_trigger",
  "parameters": {
    "events": ["convo.created"]
  }
}

Watch customer replies and notes:

{
  "type": "helpscout_trigger",
  "parameters": {
    "events": ["convo.customer.reply.created", "convo.note.created"]
  }
}

Track conversation routing and status changes:

{
  "type": "helpscout_trigger",
  "parameters": {
    "events": ["convo.assigned", "convo.moved", "convo.status", "convo.tags"]
  }
}

Collect satisfaction ratings and new customers:

{
  "type": "helpscout_trigger",
  "parameters": {
    "events": ["satisfaction.ratings", "customer.created"]
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

The Help Scout Trigger listens for events related to conversations, customers, and satisfaction ratings within Help Scout. This is the right tool when you need to start a workflow automatically in response to specific support events, rather than manually initiating it or polling for changes. It produces the complete event payload from Help Scout when a matching event occurs.