Respond.io currently provides 7 triggers that can start a workflow and 9 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.
Contact Tag Updated
Triggers when a tag is added or removed from a contact in Respond.io.
Contact Updated
Triggers when an existing contact is updated in Respond.io.
Conversation Closed
Triggers when a conversation is closed.
Conversation Opened
Triggers when a new conversation is opened.
New Contact
Triggers when a new contact is created in Respond.io.
New Incoming Message
Triggers when a new message is received from a contact.
New Outgoing Message
Triggers when a message is sent from Respond.io.
Add Comment to Conversation
Add an internal comment/note to a conversation in Respond.io.
Add Tag to Contact
Add one or multiple tags to a contact in Respond.io.
Assign or Unassign Conversation
Assign or unassign a conversation to/from a team member in Respond.io.
Create Contact
Create a new contact record in Respond.io.
Create or Update Contact
Create a new contact or update an existing one by email, phone, or ID.
Delete Contact
Permanently delete a contact from Respond.io.
Find Contact
Search for contacts by name, email, or phone number in Respond.io.
Open Conversation
Mark a conversation as open in Respond.io.
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 Respond.io event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Contact Tag Updated
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Respond.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
Add Comment to Conversation
Combine Respond.io with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
Contact Tag Updated
Finishes with
Add Comment to Conversation, then preserve the outcome in Coherence
The exact authentication fields depend on Respond.io. The workflow structure stays straightforward:
Authorize the Respond.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 Respond.io or provide a complementary trigger or action.
Respond.io currently provides 7 triggers that can start a workflow and 9 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.
Respond.io currently lists 7 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 Respond.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.
