Skip to content
Acuity Scheduling logoOutseta logo

Connect Acuity Scheduling to Outseta

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

Acuity Scheduling triggers
2
Acuity Scheduling actions
8
Outseta triggers
6
Outseta actions
44

Automation ideas

What you can build with Acuity Scheduling and Outseta

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

  • Appointment Canceled in Acuity Scheduling creates Retrieve Account in Outseta

    Triggers when an appointment is canceled.

  • New Account Event in Outseta creates Add Blocked Off Time in Acuity Scheduling

    Triggers on account-scoped events (lifecycle, stage, billing, subscription, invoice).

  • Appointment Canceled in Acuity Scheduling creates Retrieve Person in Outseta

    Triggers when an appointment is canceled.

  • New Account Event in Outseta creates Create Appointment in Acuity Scheduling

    Triggers on account-scoped events (lifecycle, stage, billing, subscription, invoice).

  • Appointment Canceled in Acuity Scheduling creates Retrieve Deal in Outseta

    Triggers when an appointment is canceled.

  • New Account Event in Outseta creates Create Client in Acuity Scheduling

    Triggers on account-scoped events (lifecycle, stage, billing, subscription, invoice).

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 Acuity Scheduling and acts in Outseta, 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.