Quill Booking
SchedulingConnect AI agents to Quill Booking, the WordPress appointment scheduling plugin. Agents list events and calendars, cancel or reschedule bookings, and react when bookings are created or changed on your WordPress site so schedule changes propagate instantly.
What This Integration Enables
Quill Booking is the odd one out among scheduling connectors, and the reason is architectural. It is site-local. There is no vendor cloud in the middle: FlowRunner posts to your own WordPress site, and the Quill Booking plugin running on that server handles the request. Your booking data never leaves infrastructure you already control, which matters more to some teams than any feature on a comparison chart. The action surface is deliberately narrow to match. Verify API Key proves the connection, List Events and List Calendars expose the appointment types and hosts configured on the site, and Cancel Booking and Reschedule Booking are the only two levers that write.
That narrowness is a design statement, not a gap. Quill Booking is built to push rather than to be polled, and On Booking Event is where the value sits. One subscription covers creations, cancellations, and reschedules on a chosen event, or all three at once through the Any Booking Event option, and it arrives with the complete booking payload rather than an ID you then have to go and fetch. So the shape of a Quill Booking flow is: the site tells FlowRunner what happened, agents fan that out to the systems that need to know, and the two write actions send a decision back the other way. Because those two writes are the entire return path, they are where the human-in-the-loop gate belongs. Every operation and the trigger are built and verified against the Quill Booking integration API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A Booking on the Site Becomes a Record Everywhere Else
A prospect books a discovery call on the site. On Booking Event fires immediately with the attendee details, the event, the timing, the location, and whatever custom questions the form asked. The agent runs List Calendars to resolve which host the booking landed on, then searches HubSpot for the attendee's email. An existing contact gets the meeting logged against it. A new one gets created with the form answers already populated, so the host opens the record and finds the qualifying context rather than a blank note. A short summary goes to the host in Slack. Nobody opens the WordPress admin at any point.
Cancellations That Close Their Own Loops
The same trigger fires on a cancellation. The agent reads the payload, marks the CRM record accordingly, and stops the pre-appointment reminder sequence that would otherwise keep emailing somebody who is no longer coming. It appends the cancellation to a running sheet in Google Sheets with the event, the host, and the lead time, which turns a scattered annoyance into a pattern the team can read. Late cancellations concentrated on one event type are worth knowing about. The agent does not rebook anyone, because rebooking is the host's call and the connector has no create action to do it with.
An Inbound Request to Move an Appointment
A customer emails asking to move Thursday to the following week. The agent identifies the booking from the CRM record written when it was first created, then assembles the request for the host: who, the current slot, the requested slot, and the original booking's custom field answers. That goes to the host through Gmail or Slack. The host replies with a time, and only then does Reschedule Booking run with the confirmed ISO 8601 start and end. The customer receives one message with the new time, instead of the four-message negotiation that normally consumes a morning.
Human-in-Loop Highlight
Reschedule Booking accepts an absolute start and end time and moves a customer's appointment to it. What is worth noticing is what the connector cannot do alongside that. There is no availability action anywhere in the surface, no way to list existing bookings, and no create action to put things back. So an agent proposing a new time is asserting that a slot is open with nothing in the connector to verify the claim against. The host discovers the collision when two people arrive for the same half hour. That is why the gate sits here rather than on the cancellation. Before any move, the agent posts to the host: "Reschedule request from [name], currently Thursday 14:00, asking for Tuesday 10:00. I cannot check your availability from here. Confirm Tuesday 10:00, propose another time, or leave it as it stands?" The host answers with a slot they can see, and Reschedule Booking runs once against a time a human has actually checked. Reads, CRM writes, and the fan-out from On Booking Event all run unsupervised, because none of them changes what a customer will find on their calendar.
Agent Capabilities
5 actionsAccount
1- Verify API Key Checks that the configured Site URL and API key are valid by asking the Quill Booking plugin to confirm the credentials. Returns the site name, site URL, and installed version, which makes it the right connection test before anything else runs.
Events
2- List Events Lists the bookable events, meaning the appointment types, configured in Quill Booking on the connected site. Each event carries a numeric ID, a hash ID, and a name. The returned event ID is what the booking trigger watches.
- List Calendars Lists the calendars, meaning the hosts or teams, configured on the connected site. Each calendar carries a numeric ID and a name, and calendars group the events that can be booked against them.
Bookings
2- Cancel Booking Cancels an existing booking by its numeric booking ID and returns the updated booking data. Canceling frees the time slot and, where the site is configured for it, notifies the attendee and the host.
- Reschedule Booking Moves an existing booking to a new start and end time, supplied as ISO 8601 timestamps with a timezone offset. Because no availability check exists in this connector, the new time is routed for host confirmation before the write runs.
Triggers
1 triggersEvent Triggers
1- On Booking Event Fires when a booking event occurs for the selected Quill Booking event, meaning a booking is created, canceled, or rescheduled. Choosing Any Booking Event fires on all three. Quill Booking registers a webhook for the selected event and delivers the full booking payload, including customer, event, timing, location, and custom fields, so the flow starts with everything it needs rather than an ID to look up.
Frequently Asked Questions
What can FlowRunner do with Quill Booking?
FlowRunner agents can run Verify API Key, List Events, and List Calendars in Quill Booking, plus 2 more actions.
Does connecting Quill Booking to FlowRunner require OAuth?
No. Quill Booking connects to FlowRunner with an API key, no OAuth flow required.
Can Quill Booking trigger a FlowRunner workflow automatically?
Yes. Quill Booking supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Quill Booking
$100 in credits. No card required. Connect in minutes.