OpenPhone currently provides 5 triggers that can start a workflow and 4 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.
Call Recording Completed
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
Outgoing Message Delivered
Fires when an outbound message is delivered successfully. Useful for message confirmation workflows.
Outgoing Call Completed
Fires when an outbound call ends. Useful for call logging.
Incoming Call Completed
Fires when an incoming call is completed. Includes voicemail data if available.
Incoming Message Received
Fires when a new SMS/MMS message is received.
Send Message
Send SMS/MMS from your OpenPhone number to a recipient
Create Contact
Create a new contact in your OpenPhone workspace
Update Contact
Update an existing contact in your OpenPhone workspace
Get Call Summary
Retrieve an AI-generated summary of a specific call by ID. Call summaries are only available on OpenPhone Business plan.
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 OpenPhone event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Call Recording Completed
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported OpenPhone 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
Send Message
Combine OpenPhone with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
Call Recording Completed
Finishes with
Send Message, then preserve the outcome in Coherence
The exact authentication fields depend on OpenPhone. The workflow structure stays straightforward:
Authorize the OpenPhone 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 OpenPhone or provide a complementary trigger or action.
OpenPhone currently provides 5 triggers that can start a workflow and 4 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.
OpenPhone currently lists 5 triggers and 4 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 OpenPhone 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.
