Can Acuity Scheduling and Village talk in both directions?

Yes. Build one flow that starts in Acuity Scheduling 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.

Connect Acuity Scheduling to Village

Move data between Acuity Scheduling 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.

Start building Explore Acuity Scheduling Explore Village

Acuity Scheduling triggers: 2
Acuity Scheduling actions: 8
Village triggers: 0
Village actions: 40

Automation ideas

What you can build with Acuity Scheduling and Village

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

Appointment Canceled in Acuity Scheduling creates Get App Information in Village
Triggers when an appointment is canceled.
Appointment Canceled in Acuity Scheduling creates Check Company Paths in Village
Triggers when an appointment is canceled.
Appointment Canceled in Acuity Scheduling creates Refresh Companies in Village
Triggers when an appointment is canceled.
New Appointment in Acuity Scheduling creates Get App Information in Village
Triggers when a new appointment is scheduled.