Skip to content
OpenPhone logoSalesforce logo

Connect OpenPhone to Salesforce

Move data between OpenPhone and Salesforce the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

OpenPhone triggers
5
OpenPhone actions
4
Salesforce triggers
9
Salesforce actions
27

Automation ideas

What you can build with OpenPhone and Salesforce

A few flows teams run between OpenPhone and Salesforce. Use one as a starting point, or build your own from scratch.

  • Call Recording Completed in OpenPhone creates Add Contact to Campaign in Salesforce

    Fires when a call recording finishes. Useful for post-transcription or archival workflows.

  • New Case Attachment in Salesforce creates Send Message in OpenPhone

    Fires when a new Attachment or File is added to any Case record.

  • Call Recording Completed in OpenPhone creates Add File to Record in Salesforce

    Fires when a call recording finishes. Useful for post-transcription or archival workflows.

  • New Case Attachment in Salesforce creates Create Contact in OpenPhone

    Fires when a new Attachment or File is added to any Case record.

  • Call Recording Completed in OpenPhone creates Add Lead to Campaign in Salesforce

    Fires when a call recording finishes. Useful for post-transcription or archival workflows.

  • New Case Attachment in Salesforce creates Update Contact in OpenPhone

    Fires when a new Attachment or File is added to any Case record.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in OpenPhone and acts in Salesforce, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.