Help Scout currently provides 4 triggers that can start a workflow and 9 actions a workflow can run. Use those building blocks to connect support activity to the full account history and the next internal action.
Conversation Created
Triggers when a new conversation is started in a mailbox.
Conversation Assigned
Triggers when a conversation is assigned to a user.
New Customer
Triggers when a new customer is added.
Tags Updated
Triggers when tags on a conversation are modified.
Create Conversation
Start a new conversation.
Send Reply
Sends a reply in an existing conversation.
Add Note
Adds a note to a conversation.
Create Customer
Adds a new customer to Help Scout.
Update Customer Properties
Updates customer's properties.
Find Conversation
Finds an existing conversation using provided filter.
Find Customer
Finds a customer by email.
Find User
Finds a user by email.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Help Scout event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Conversation Created
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Help Scout action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Conversation
Combine Help Scout with another integration and Coherence records to connect support activity to the full account history and the next internal action.
Starts with
Conversation Created
Finishes with
Create Conversation, then preserve the outcome in Coherence
The exact authentication fields depend on Help Scout. The workflow structure stays straightforward:
Authorize the Help Scout account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Help Scout or provide a complementary trigger or action.
Help Scout currently provides 4 triggers that can start a workflow and 9 actions a workflow can run. Use those building blocks to connect support activity to the full account history and the next internal action.
Help Scout currently lists 4 triggers and 9 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Help Scout triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
