Can Acuity Scheduling and 0CodeKit talk in both directions?

Yes. Build one flow that starts in Acuity Scheduling and acts in 0CodeKit, 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 0CodeKit

Move data between Acuity Scheduling and 0CodeKit 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 0CodeKit

Acuity Scheduling triggers: 2
Acuity Scheduling actions: 8
0CodeKit triggers: 0
0CodeKit actions: 34

Automation ideas

What you can build with Acuity Scheduling and 0CodeKit

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

Appointment Canceled in Acuity Scheduling creates Current Month in 0CodeKit
Triggers when an appointment is canceled.
Appointment Canceled in Acuity Scheduling creates Specific Month and Year in 0CodeKit
Triggers when an appointment is canceled.
Appointment Canceled in Acuity Scheduling creates Current Week in 0CodeKit
Triggers when an appointment is canceled.
New Appointment in Acuity Scheduling creates Current Month in 0CodeKit
Triggers when a new appointment is scheduled.