SendPulse currently provides 3 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
New Subscriber
Fires when new subscriber is added
New Unsubscriber
Fires when subscriber unsubscribes
Updated Subscriber
Fires when subscriber details change (polling)
Add Subscriber
Add subscriber to mailing list
Change Variable for Subscriber
Update subscriber variable
Delete Contact
Permanently delete contact from all mailing lists
Unsubscribe User
Remove subscribers from mailing list
Update Subscriber
Update subscriber details and variables
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 SendPulse event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Subscriber
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported SendPulse 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 Subscriber
Combine SendPulse with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
New Subscriber
Finishes with
Add Subscriber, then preserve the outcome in Coherence
The exact authentication fields depend on SendPulse. The workflow structure stays straightforward:
Authorize the SendPulse 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 SendPulse or provide a complementary trigger or action.
SendPulse currently provides 3 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
SendPulse currently lists 3 triggers and 6 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 SendPulse 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.
