Skip to content
TidyCal logoClockodo logo

Connect TidyCal to Clockodo

Move data between TidyCal and Clockodo 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.

TidyCal triggers
3
TidyCal actions
1
Clockodo triggers
2
Clockodo actions
33

Automation ideas

What you can build with TidyCal and Clockodo

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

  • Booking Canceled in TidyCal creates Create Entry in Clockodo

    Triggers when a new booking is canceled

  • New Entry in Clockodo creates Custom API Call in TidyCal

    Triggers when a new time entry is created

  • Booking Canceled in TidyCal creates Get Entry in Clockodo

    Triggers when a new booking is canceled

  • New Absence Enquiry in Clockodo creates Custom API Call in TidyCal

    Triggers when a new absence enquiry is created

  • Booking Canceled in TidyCal creates Get Entries in Clockodo

    Triggers when a new booking is canceled

  • New Booking in TidyCal creates Create Entry in Clockodo

    Triggers when a new booking is created

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 TidyCal and acts in Clockodo, 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.