Can OpenPhone and ClickUp talk in both directions?

Yes. Build one flow that starts in OpenPhone and acts in ClickUp, 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.

Connect OpenPhone to ClickUp

Move data between OpenPhone and ClickUp 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.

Start building Explore OpenPhone Explore ClickUp

OpenPhone triggers: 5
OpenPhone actions: 4
ClickUp triggers: 30
ClickUp actions: 31

Automation ideas

What you can build with OpenPhone and ClickUp

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

Call Recording Completed in OpenPhone creates Create Task in ClickUp
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
Task Created in ClickUp creates Send Message in OpenPhone
Triggered when a new task is created.
Call Recording Completed in OpenPhone creates Create Task From Template in ClickUp
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
Task Created in ClickUp creates Create Contact in OpenPhone
Triggered when a new task is created.
Call Recording Completed in OpenPhone creates Create Folderless List in ClickUp
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
Task Created in ClickUp creates Update Contact in OpenPhone
Triggered when a new task is created.