TriggerHelp ScoutReal-timeUpdated June 2026

When does Help Scout fire on status changes?

Short answer: In TinyCommand, add the Help Scout Help Scout Status Changed trigger to a workflow and publish. It listens through a Help Scout webhook and fires your workflow within seconds of the event, with no polling and no code. Add a filter if you only want some events to start a run.

Trigger workflows on Help Scout Status Changed in Help Scout — start free
Anatomy

What this trigger looks like in a workflow.

Drop it on the canvas. Configure a couple of fields. Publish.

In the builder
Trigger
Help Scout Status Changed
When the matching event happens
status modifiedwatch for status changedwhen status changedon status changedstatus changednew status changedwhen a conversation status changes
What this trigger returns
for the curious

You don’t need to read this. TinyCommand auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.

{
"id": 12345,
"event": "convo.status",
"subject": "Support request",
"customer": "user@example.com"
}
Output shape

Fields available to downstream nodes.

Every field below can be referenced by name in any action or filter that comes after this trigger.

FieldTypeExample
idnumber12345
eventstring"convo.status"
subjectstring"Support request"
customerstring"user@example.com"
FAQ

Questions about Help Scout Status Changed.

How does the Help Scout Status Changed trigger work in Help Scout?
Fires when a conversation transitions state (active, pending, closed, spam). For "conversation closed → request CSAT survey" or "marked spam → train AI classifier" workflows.
Is the Help Scout Status Changed trigger real-time?
Yes. Help Scout Status Changed uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Help Scout.
What data does Help Scout Status Changed return?
The full event payload from Help Scout. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Help Scout Status Changed so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Help Scout admin permissions to use Help Scout Status Changed?
For most Help Scout accounts a standard user can authorize the trigger. Some Help Scout plans require an admin to enable third-party webhooks. Check Help Scout's docs if the trigger fails to register.
More triggers

Other Help Scout triggers.

Trigger
Help Scout Conversation Assigned
Fires when a conversation is assigned (or reassigned) to a user. Useful for "new assignment → ping the user in Slack with context" workflows.
Trigger
Help Scout Conversation Created
Fires when a new conversation lands in a mailbox. Payload includes customer, subject, message body, channel (email, chat, social). The base hook for "new inbound → route to right team" workflows.
Trigger
Help Scout Conversation Moved
Fires when a conversation moves between mailboxes (e.g., Support → Billing). Useful for cross-team handoff workflows that need to notify the new owning team.
Trigger
Help Scout Customer Replied
Fires when a customer replies on an open conversation. The hook for re-opening "pending" conversations and for "high-priority customer replied → notify the assignee immediately" workflows.
Trigger workflows on Help Scout Status Changed in Help Scout — start free