Connect Acuity Scheduling to Kibana
Trigger an automatic workflow in Kibana the moment something happens in Acuity Scheduling. Commercient Pulse handles the handoff in real time.
The world’s most innovative companies run on Commercient
Most popular Acuity Scheduling + Kibana Pulses
When a client completes an intake form in Acuity Scheduling, Pulse automatically creates a new Dashboard Alert in Kibana.
When a new appointment is booked in Acuity Scheduling, Pulse automatically creates a new Dashboard Alert in Kibana.
When an appointment is rescheduled in Acuity Scheduling, Pulse automatically creates a new Dashboard Alert in Kibana.
When a new visualization is created in Kibana, Pulse automatically creates a new Appointment in Acuity Scheduling.
When an anomaly is detected in Kibana, Pulse automatically creates a new Appointment in Acuity Scheduling.
When a saved search alert fires in Kibana, Pulse automatically creates a new Appointment in Acuity Scheduling.
*Pulses may vary based on your platform specifications
Why Commercient?
With Commercient, you can automate everything from a single webhook trigger to complex, multi-system event flows.
Trusted by teams from Fortune 500s to startups
See why more customers are choosing Commercient than any other solution
Make work flow with Commercient agents
Level up your Acuity Scheduling to Kibana integration with Agentic AI. Securely extract, summarize, and transform your integration data.
About Acuity Scheduling
Acuity Scheduling is a scheduling platform used to manage bookings, appointments and calendars.
About Kibana
Kibana is a developer and DevOps platform used to manage code, deployments and infrastructure.
Frequently asked questions (FAQs)
A Pulse workflow starts from a specific event in Acuity Scheduling, such as an appointment is cancelled, and runs a single defined action in Kibana each time that event fires. Exact triggers and actions are configured per workflow.
Yes. Pulse listens for the event in Acuity Scheduling and pushes the update to Kibana as soon as it happens, rather than waiting for a scheduled batch sync. Typical delivery is near-instant, depending on the source platform's webhook or event support.
Yes, though it runs as a separate one-way workflow in the other direction. Commercient can set up a second Pulse trigger so that when a saved search alert fires in Kibana, the update flows back into Acuity Scheduling automatically.
Pulse workflows are event-driven, so they react as soon as Acuity Scheduling emits the triggering event. Reaction time is typically within seconds, depending on how quickly Acuity Scheduling delivers the event.
No. Pulse workflows are configured, not coded. Commercient sets up the trigger in Acuity Scheduling and the matching action in Kibana for you, so no in-house development work is required.