Sender currently provides 7 triggers that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect campaign activity to the records and follow-up it should influence.
New Campaign
Fires when a new campaign is created in Sender
New Group
Fires when a new group/list is created
New Subscriber
Fires when a subscriber is added to any group or to account
New Subscriber in Group
Fires when a subscriber is added to a specific group/list
Updated Subscriber
Fires when a subscriber's data (fields) is updated
New Unsubscriber
Fires when someone unsubscribes globally
New Unsubscriber From Group
Fires when a subscriber is removed/unsubscribed from a specific group
Add / Update Subscriber
Add a new subscriber or update existing subscriber's data
Create Campaign
Creates a draft campaign in Sender
Unsubscribe Subscriber
Mark an email address as unsubscribed globally or from a group
Add Subscriber to Group
Add an existing or new subscriber into one or more groups
Remove Subscriber from Group
Remove a subscriber from a specific group
Send Campaign
Trigger sending of a drafted campaign to its recipient list
Update Subscriber
Update an existing subscriber's data
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 Sender event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Campaign
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Sender 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
Add / Update Subscriber
Combine Sender with another integration and Coherence records to connect campaign activity to the records and follow-up it should influence.
Starts with
New Campaign
Finishes with
Add / Update Subscriber, then preserve the outcome in Coherence
The exact authentication fields depend on Sender. The workflow structure stays straightforward:
Authorize the Sender 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 Sender or provide a complementary trigger or action.
Sender currently provides 7 triggers that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect campaign activity to the records and follow-up it should influence.
Sender currently lists 7 triggers and 7 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 Sender 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.
