Meet.bot
SchedulingConnect AI agents to Meet.bot, an AI-first meeting scheduling platform. Agents check availability, book meetings, manage connected calendar events, and maintain scheduling pages so meeting coordination happens without email ping-pong.
What This Integration Enables
Most scheduling connectors talk to a booking database. Meet.bot talks to the calendars themselves, and that is the distinction to build on. One half of this surface is the public booking layer: scheduling pages with their own URLs, real availability that honors the owner's buffers and booking window, and a booking operation that puts a guest on the calendar with an iCalendar UID returned. The other half reaches straight past it into the connected accounts, listing calendars with their provider and per-calendar write access, returning busy intervals across all of them, listing and creating events, and rescheduling or canceling events that Meet.bot never created.
That reach is genuinely useful and worth handling carefully. It means an agent can check real conflicts before proposing a time rather than trusting a page's own view. It also means a write does not stop at a booking record, it lands on a person's actual calendar and sends the invite. The platform's own defaults reflect this: List Events omits event titles unless the detail level is set to Full, because the calendar it is reading is somebody's private one. Agents get the reach; a person keeps the calls that change what is already on the calendar. Every action is built and verified against the Meet.bot API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A Chat Agent That Books a Real Slot
A prospect in a live chat asks for a demo. The agent runs List Scheduling Pages to find the right page, Get Page Info for the duration and how far ahead bookings are allowed, then Get Available Slots for the coming week, requesting one-click shareable booking links so the prospect can confirm without a form. When they choose, the agent runs Book Meeting with their name and email and up to fifteen additional attendees, and posts the booking to the sales channel in Slack with the guest's company already resolved from HubSpot. The slot offered is one the owner is actually free for, because the page resolved it against their connected calendars.
The One-Off Meeting Nobody Has to Negotiate
An escalation needs three internal people and a customer, today. The agent runs List Calendars to confirm which accounts have write access and which need reauthentication, then Get Free Busy across the window for everyone involved, and picks the first interval where nobody is busy. It creates the meeting with Create Meeting, letting it auto create the web conference link, and invites the additional attendees in the same call. Note that Create Meeting meters as a pay-per-meeting booking, so a flow that creates meetings in bulk should be scoped deliberately rather than run against a whole list.
Booking Events That Reach the Rest of the Stack
The revenue team needs bookings to arrive in the CRM as they happen rather than as an overnight sync. The agent runs Create Webhook pointing at a FlowRunner entry point, choosing whether the subscription covers all pages or selected ones and whether its scope is one user or the whole team, and stores the returned shared secret so incoming payloads can be verified. Each booking event then drives its own flow: the contact is upserted in HubSpot, the meeting is logged to Google Sheets for pipeline reporting, and the owner is notified. List Webhooks audits what is registered and Update Webhook flips a subscription inactive without tearing it down.
Human-in-Loop Highlight
Update Event and Delete Event are not booking-record operations. They act directly on the calendar provider, they cannot be undone, and they reach events that Meet.bot never created: a customer's board meeting, an interview, a one to one, anything sitting on a connected calendar the token can write to. The awkward part is what the agent can see while deciding. List Events withholds event titles by default for privacy and returns them only when the detail level is set to Full, so an agent proposing a change is frequently looking at a time block, an id, and an attendee count rather than at what the meeting is. Rescheduling something on that basis is a guess about somebody else's priorities. So the agent stops before it writes. It gathers the conflicting events, the free/busy picture around them, and which of them came from a scheduling page, and asks the calendar owner in Slack: "Two events overlap on [date] from [time] to [time]. One was booked through your [page] page, one is an existing calendar event I can see as a time block only. Move the page booking to [alternative], move the other, or leave both and I will flag the attendees?" The owner answers, and only then does the agent run Update Event with start and end supplied together, or Delete Event, and record who approved it. Reading calendars, resolving availability, offering slots, and booking on a page all run without asking. Reaching into a colleague's existing calendar does not.
Agent Capabilities
17 actionsScheduling Pages
4- List Scheduling Pages Lists the scheduling pages on the account with each page's title, meeting duration, and public URL. The page URL is the identifier the other page operations key on.
- Get Page Info Retrieves public information about a single scheduling page: title, meeting duration, owner name, and how many days ahead bookings are allowed.
- Get Page Configuration Retrieves the full configuration of the authenticated user's booking page, including slug, duration, timezone, buffers, booking window, recurring weekly availability, and branding. Read this before proposing any change.
- Update Page Configuration Updates the booking page configuration, changing only the fields supplied: title, slug, duration, description, timezone, active state, booking window, buffers, minimum notice, slot step, and web conferencing behavior. Changes take effect on a page people already hold links to.
Booking
2- Get Available Slots Retrieves bookable slots for a scheduling page, honoring the owner's availability, buffers, and booking window, with optional date range and count and optional one-click shareable booking links per slot.
- Book Meeting Books a meeting on a scheduling page for a guest at a slot returned by Get Available Slots, adding the guest to the calendar invite plus up to fifteen additional attendees. Returns the booking confirmation with its iCalendar UID.
Calendars and Events
6- List Calendars Lists the connected calendar accounts and their individual calendars, including provider, email, whether the account needs reauthentication, and per-calendar write access. Check write access before planning any event operation.
- Get Free Busy Returns busy intervals across the connected calendars for a time window, optionally restricted to one calendar. The conflict check before a meeting is proposed or created.
- List Events Lists meetings across the connected calendars for a time window. Event titles are omitted for privacy unless the detail level is set to Full. Returns the event ids that Update Event and Delete Event require.
- Create Meeting Creates a one-off meeting between the caller and a main guest, with up to fifteen additional invitees, and can auto create a web conference link. This meters as a pay-per-meeting booking, so bulk creation should be scoped deliberately.
- Update Event Reschedules or retitles a single calendar event by calendar id and provider event id. Start and end must be supplied together. Because it writes to the calendar provider and cannot be undone, it is routed for the calendar owner's approval.
- Delete Event Cancels and deletes a single calendar event by calendar id and provider event id. This operates directly on the calendar provider and cannot be undone, so it is routed for human approval.
Webhooks
5- List Webhooks Lists the outbound webhooks configured for the user, including target URL, coverage, scope, associated pages, active state, and the shared secret used to verify payloads.
- Create Webhook Creates an outbound webhook that Meet.bot calls on booking events, covering all pages or selected pages, scoped to one user or the whole team. Returns the shared secret for payload verification.
- Get Webhook Retrieves a single webhook by id with its target URL, coverage, scope, associated pages, active state, and shared secret.
- Update Webhook Updates a webhook by id, changing only the fields supplied: target URL, description, coverage, scope, associated pages, and active state. The way to pause a subscription without losing its configuration.
- Delete Webhook Permanently deletes a webhook by id, after which Meet.bot stops sending events to its target URL. This cannot be undone.
Frequently Asked Questions
What can FlowRunner do with Meet.bot?
FlowRunner agents can run List Scheduling Pages, Get Page Info, and Get Page Configuration in Meet.bot, plus 14 more actions.
Does connecting Meet.bot to FlowRunner require OAuth?
No. Meet.bot connects to FlowRunner with an API key, no OAuth flow required.
Can Meet.bot trigger a FlowRunner workflow automatically?
Meet.bot doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Meet.bot
$100 in credits. No card required. Connect in minutes.