Skip to content
OpenPhone logoSlack logo

Connect OpenPhone to Slack

Move data between OpenPhone and Slack 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
Slack triggers
14
Slack actions
28

Automation ideas

What you can build with OpenPhone and Slack

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

  • Call Recording Completed in OpenPhone creates Add Reaction to Message in Slack

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

  • New Public Message Posted Anywhere in Slack creates Send Message in OpenPhone

    Triggers when a new message is posted to any channel.

  • Call Recording Completed in OpenPhone creates Send Message To A User in Slack

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

  • New Public Message Posted Anywhere in Slack creates Create Contact in OpenPhone

    Triggers when a new message is posted to any channel.

  • Call Recording Completed in OpenPhone creates Send Message To A Channel in Slack

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

  • New Public Message Posted Anywhere in Slack creates Update Contact in OpenPhone

    Triggers when a new message is posted to any channel.

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 Slack, 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.