Skip to content
TidyCal logoHedy logo

Connect TidyCal to Hedy

Move data between TidyCal and Hedy 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
Hedy triggers
5
Hedy actions
19

Automation ideas

What you can build with TidyCal and Hedy

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

  • Booking Canceled in TidyCal creates Get Session in Hedy

    Triggers when a new booking is canceled

  • Session Created in Hedy creates Custom API Call in TidyCal

    Triggers when a new session is created in Hedy.

  • Booking Canceled in TidyCal creates List Sessions in Hedy

    Triggers when a new booking is canceled

  • Session Ended in Hedy creates Custom API Call in TidyCal

    Triggers when a session is completed in Hedy.

  • Booking Canceled in TidyCal creates Get Highlight in Hedy

    Triggers when a new booking is canceled

  • Session Exported in Hedy creates Custom API Call in TidyCal

    Triggers when a user manually exports a session via the app. Payload includes exportedAt instead of endTime.

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