Can TidyCal and Copper talk in both directions?

Yes. Build one flow that starts in TidyCal 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 TidyCal to Copper

Move data between TidyCal 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 TidyCal Explore Copper

TidyCal triggers: 3
TidyCal actions: 1
Copper triggers: 11
Copper actions: 20

Automation ideas

What you can build with TidyCal and Copper

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

Booking Canceled in TidyCal creates Create Person in Copper
Triggers when a new booking is canceled
New Activity in Copper creates Custom API Call in TidyCal
Triggers when a new activity is logged
Booking Canceled in TidyCal creates Update Person in Copper
Triggers when a new booking is canceled
New Person in Copper creates Custom API Call in TidyCal
Triggers when a new person/contact is created.
Booking Canceled in TidyCal creates Create Lead in Copper
Triggers when a new booking is canceled
New Lead in Copper creates Custom API Call in TidyCal
Triggers when a new lead is created.