Datelist
SchedulingConnect AI agents to Datelist, an online booking and appointment scheduling tool. Agents list calendars and products, update or cancel booked slots, and register webhooks so new bookings start a flow the moment they arrive.
What This Integration Enables
Datelist gives you six operations, and the one that is missing tells you what the product is. There is no create action here, because booking creation happens on the public Datelist booking page where the customer chooses their own slot. This connector is not a booking engine that an agent drives. It is the operations layer over appointments that customers made for themselves. Agents read the calendars and the bookable products, retrieve the slots with the contact and the intake answers attached, correct them in place, and cancel when a cancellation is genuinely the right answer. A callback subscription means none of that waits for someone to check an inbox.
That constraint is worth designing around rather than resenting. It means Update Booked Slot carries more weight than it would in a fuller API, because editing an existing appointment is the only repair an agent has: the alternative, canceling and rebooking, hands the second half of the job back to the customer. It also means the interesting automation sits on either side of the booking rather than inside it, in validating what arrived and in acting on what it implies. Every action is built and verified against the Datelist API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Every New Booking Routed and Enriched
The agent registers a callback with Create Webhook against the relevant calendar, so a new booking starts a flow rather than a notification. When one arrives it runs List Booked Slots filtered to that calendar and window, reads the contact email, name, phone, and the custom field answers captured on the public page, and looks the person up in HubSpot. If they are an existing customer the agent attaches the appointment to their record; if not it creates one with the source and the product attached. The team's channel in Slack gets a single message with who booked, for what, and their history, instead of a bare confirmation email.
Reminders That Read the Real Calendar
Each afternoon the agent runs List Booked Slots with an ISO 8601 range covering the following day, across every calendar returned by List Calendars. For each appointment it composes a reminder with the product name, duration, and location taken from List Products, and sends it through Gmail, with an SMS through Twilio for the products where phone contact converts better. Because the reminder is generated from the live slot rather than from a copy, a customer who was moved that morning gets the corrected time rather than the original one.
Fixing a Booking Instead of Destroying It
A customer replies to a reminder to say the phone number on file is wrong and they need the later duration. In a system where an agent can rebook, the reflex is to cancel and recreate. Here that reflex is expensive, because the recreate half cannot be done through this connector and the customer would have to go back to the public page. So the agent finds the appointment with List Booked Slots using the contact email, then calls Update Booked Slot with only the changed fields, using the same field names the list returned. The appointment keeps its identity, its history, and its place on the calendar, and the customer does nothing.
Human-in-Loop Highlight
Cancel Booked Slot is the one call in this connector that cannot be walked back by the agent that made it. It deletes the appointment and frees the time, the action cannot be undone, and because there is no create operation here the agent has no way to put the customer back on the calendar: only the customer can, by returning to the public booking page and choosing again. The call also carries a flag that decides whether a cancellation email is sent, which means an agent can quietly remove someone's appointment and leave them to discover it by arriving. So the agent gathers rather than acts. It pulls the slot with List Booked Slots, the product detail with List Products, and the customer's history, then routes to the service owner in Slack: "Booking [id] for [name] on [date] at [time], product [name], flagged because [reason]. Canceling frees the slot and cannot be undone from here, and rebooking has to be done by the customer. Cancel and send the notification email, cancel silently and call them, or leave it and I will follow up?" The owner picks. Reads, reminders, enrichment, and in place corrections all run on their own. The call that takes a customer's appointment away and may never tell them does not.
Agent Capabilities
6 actionsCalendars and Products
2- List Calendars Lists the booking calendars in the account with their numeric IDs and display names. Each calendar represents a bookable resource, a person, a room, or a service, and its ID scopes products, slots, and webhooks.
- List Products Lists the bookable products, the services or appointment types customers can choose, with price, available places, duration in minutes, and the calendar each belongs to. Optionally filtered by name or calendar.
Bookings
3- List Booked Slots Retrieves appointments with their start and end times, the contact who booked including email, name, and phone, the product, and any custom field values. Filter by contact email, calendar, and an ISO 8601 date range.
- Update Booked Slot Updates an existing appointment by its numeric ID, changing only the fields supplied and using the same field names List Booked Slots returned. The in place repair that keeps the appointment's identity intact.
- Cancel Booked Slot Cancels an appointment by its numeric ID and frees the time, optionally emailing the contact who booked it. This cannot be undone, and rebooking has to happen on the public booking page, so it is routed for human approval.
Webhooks
1- Create Webhook Subscribes a callback URL to new booking notifications for a calendar, so Datelist posts to a FlowRunner entry point each time a slot is taken. The way to start a flow on arrival instead of polling for it.
Frequently Asked Questions
What can FlowRunner do with Datelist?
FlowRunner agents can run List Calendars, List Products, and List Booked Slots in Datelist, plus 3 more actions.
Does connecting Datelist to FlowRunner require OAuth?
No. Datelist connects to FlowRunner with an API key, no OAuth flow required.
Can Datelist trigger a FlowRunner workflow automatically?
Datelist doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Datelist
$100 in credits. No card required. Connect in minutes.