Skip to content
TidyCal logoVillage logo

Connect TidyCal to Village

Move data between TidyCal and Village 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
Village triggers
0
Village actions
40

Automation ideas

What you can build with TidyCal and Village

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

  • Booking Canceled in TidyCal creates Get App Information in Village

    Triggers when a new booking is canceled

  • Booking Canceled in TidyCal creates Check Company Paths in Village

    Triggers when a new booking is canceled

  • Booking Canceled in TidyCal creates Refresh Companies in Village

    Triggers when a new booking is canceled

  • New Booking in TidyCal creates Get App Information in Village

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