Sales engagement platform for contacts, campaigns, and outbound outreach workflows.
Reply.io currently provides 10 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Get Contact
Look up a contact in Reply.io by their email address and retrieve their details.
Create or Update Contact
Add a new contact to Reply.io, or update their details if a contact with that email already exists.
Delete Contact
Permanently delete a contact from Reply.io by their email address. This cannot be undone.
Add Contact to Campaign
Create a new contact (or update an existing one) and immediately enrol them in a campaign so they start receiving outreach emails.
Push Contact to Campaign
Enrol an existing contact in a campaign so they start receiving outreach emails. Enable "Force Push" to move the contact even if they are already active in another campaign.
Remove Contact from Campaign
Stop a contact from receiving further emails in a specific campaign. The contact's record is kept in Reply.io.
Remove Contact from All Campaigns
Remove a contact from every campaign they are enrolled in. No further emails will be sent to them. Their contact record is kept in Reply.io.
Mark Contact as Replied
Record that a contact has replied to your outreach. This stops further follow-up emails to that contact across all active campaigns.
Mark Contact as Finished
Mark a contact as finished so they no longer receive emails in any campaign. Use this when you have completed all outreach to that contact.
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.
Use a change in Coherence to run a supported Reply.io 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
Get Contact
Combine Reply.io with another integration and Coherence records to keep account, contact, and deal context attached to the work around it.
Starts with
A Coherence workflow starts
Finishes with
Get Contact, then preserve the outcome in Coherence
The exact authentication fields depend on Reply.io. The workflow structure stays straightforward:
Authorize the Reply.io 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 Reply.io or provide a complementary trigger or action.
Reply.io currently provides 10 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Reply.io currently lists 0 triggers and 10 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 Reply.io 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.
