Can tl;dv and Copper talk in both directions?

Yes. Build one flow that starts in tl;dv and acts in Copper, 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 tl;dv to Copper

Move data between tl;dv and Copper 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 tl;dv Explore Copper

tl;dv triggers: 2
tl;dv actions: 5
Copper triggers: 11
Copper actions: 20

Automation ideas

What you can build with tl;dv and Copper

A few flows teams run between tl;dv and Copper. Use one as a starting point, or build your own from scratch.

Meeting Ready in tl;dv creates Create Person in Copper
Triggers when a meeting has finished processing and is ready
New Activity in Copper creates Upload Recording in tl;dv
Triggers when a new activity is logged
Meeting Ready in tl;dv creates Update Person in Copper
Triggers when a meeting has finished processing and is ready
New Activity in Copper creates List Meetings in tl;dv
Triggers when a new activity is logged
Meeting Ready in tl;dv creates Create Lead in Copper
Triggers when a meeting has finished processing and is ready
New Activity in Copper creates Get Meeting in tl;dv
Triggers when a new activity is logged