SuperSaaS
SchedulingConnect AI agents to SuperSaaS, an online appointment scheduling service. Agents create and update appointments, check availability, maintain the user database, and react to new bookings so schedules stay current without manual upkeep.
What This Integration Enables
SuperSaaS has been running online schedules for a long time, and the connector reflects a platform that grew to fit many different businesses rather than one. The first thing to understand is that a SuperSaaS schedule comes in three kinds and they are not interchangeable. Appointment and resource schedules book against rooms, staff, or equipment. Capacity schedules sell places in fixed slots and return slots rather than bookings. Service schedules behave differently again, and the platform does not support availability queries or appointment creation through the API for them at all. List Schedules reports the type, and any flow that skips that check will eventually call an operation the schedule cannot honor. Get Availability, Create Appointment, Update Appointment, and Delete Appointment cover the booking lifecycle, while List Appointments In Range and Get User Agenda serve the two reads operations teams reach for most.
The second thing is that SuperSaaS carries a real user database, not a list of names attached to bookings. Users have contact details, a timezone, a role, a credit balance, and custom fields, and every user operation accepts either the internal SuperSaaS ID or your own foreign key from whatever system owns identity in your business. That makes SuperSaaS unusually good at being the scheduling half of a larger stack. List Recent Changes completes the picture: it is a purpose-built sync endpoint that returns creations, updates, and deletions since a timestamp you supply, with a deleted flag on removed bookings, so an external system stays current without a nightly full reload. Write operations also expose a Trigger Webhook flag, so a flow can decide whether its own change should fan out through the account's existing webhooks. Agents run bookings, availability, and sync unsupervised. Operations that remove a person go to a human, which is the human-in-the-loop default FlowRunner builds around. Every operation and the trigger are built and verified against the SuperSaaS API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A New Booking Lands Everywhere It Should
On New Appointment fires within seconds of a customer booking. The agent runs Get Appointment with the form option enabled so the custom intake answers come back with the booking rather than as a separate lookup. It checks the schedule type from List Schedules, because a capacity schedule and a resource schedule need different downstream handling. Get User resolves the attendee against the foreign key the CRM already uses, and the booking is written to HubSpot against that record with the intake answers attached. A summary reaches the team in Slack with Get User Agenda output, so whoever picks it up can see what else this person already has booked.
Offering Times Without Anyone Opening the Calendar
An inbound request asks for the earliest available consultation. The agent runs Get Availability from today's date with the appointment length set, constrained to the resources qualified for that service, and takes the first three results. Those go back through Gmail as concrete times rather than an invitation to suggest one. When the customer picks a slot, Create Appointment commits it with their contact details and custom fields, and the Trigger Webhook flag fires the account's existing notification setup so the confirmation matches what customers already receive. The whole exchange costs one email in each direction.
Keeping the Warehouse Current Without a Full Reload
An operations team reports on utilization from a warehouse rather than from the scheduling UI. Every fifteen minutes the agent runs List Recent Changes with the timestamp of the last successful sync, paging through with the limit and offset parameters. Creations and updates are upserted into the reporting table; rows carrying the deleted flag are marked canceled rather than dropped, so the cancellation rate stays visible. A daily rollup lands in Google Sheets with bookings by resource and by schedule. Because the endpoint is designed for exactly this, the sync stays cheap even as the account's history grows.
Human-in-Loop Highlight
Delete User is the operation that deserves the gate, and the reason is where the identifier comes from. SuperSaaS accepts either its own internal ID or your foreign key, which is a value produced by a different system entirely: a CRM record ID, a membership number, an HR identifier. FlowRunner does not own that value and cannot verify it still points where it used to. Meanwhile Update User exposes a Not Found Handling option that can silently ignore a miss rather than raise an error, so a mapping that has quietly drifted looks perfectly healthy across thousands of successful-looking calls. The delete is where a drift stops being silent. It permanently removes the user record along with their credit balance and their place in the schedule, and the operation is irreversible. So the agent stops. It posts to the operations owner: "Offboarding sync wants to run Delete User for foreign key CRM-40218. Get User returns [name], last appointment 9 days ago, credit balance 4 sessions remaining. Delete, transfer the balance first, or leave the record and remove access another way?" Bookings, reschedules, availability reads, user creation, and the whole change feed run without anyone being asked. Erasing a person and the credit they paid for does not.
Agent Capabilities
17 actionsSchedules and Resources
2- List Schedules Retrieves all schedules in the account with their IDs, names, and types. Types include appointment, capacity, and service schedules, and each behaves differently for availability and booking, so this read belongs early in any flow.
- List Resources Lists the resources or services configured within a specific schedule. On a resource schedule these are the bookable rooms, staff, or equipment; on a service schedule these are the offered services.
Appointments
9- List Appointments Lists bookings for a schedule, optionally limited to a time window. The form option attaches any custom field data submitted at booking time, which saves a second call per appointment.
- Get Appointment Retrieves a single booking by ID, including timestamps, attendee details, status, price, and audit fields such as created and updated times. The form option returns the custom field values captured when the booking was made.
- Create Appointment Creates a new booking on a schedule from a start and finish time, or from a slot ID on capacity schedules. Attendee details, a resource, and custom fields can be attached. Service-type schedules do not support creation through the API.
- Update Appointment Updates an existing booking, changing only the fields supplied. Supports rescheduling to new start and finish times, reassigning a resource, and editing attendee details or custom fields.
- Delete Appointment Permanently deletes a booking and frees the slot. The operation is irreversible, so flows that cancel at volume are worth pointing at a confirmation step rather than running open loop.
- Get Availability Returns the free slots for a schedule from a given date and time, optionally constrained to an appointment length, a specific resource, and a maximum number of results. Not supported on service-type schedules.
- Get User Agenda Retrieves all upcoming appointments for a single user on a schedule, taking either the SuperSaaS user ID or your own foreign key. The read behind a personal agenda view or a targeted reminder.
- List Recent Changes Retrieves appointments created, updated, or deleted on a schedule since a given time, with a deleted flag on removed bookings. Built for synchronization, so poll it with the timestamp of the last successful sync.
- List Appointments In Range Retrieves the appointments or slots on a schedule within a time window, or just today's, filtered by resource or service and paginated. Capacity schedules return slots here while resource and service schedules return bookings.
Users
5- List Users Lists the users in the account with pagination, defaulting to one hundred per page and supporting up to one thousand. The form option attaches custom field data to each record.
- Get User Retrieves a single user by identifier, where a numeric value is treated as the internal SuperSaaS ID and an alphanumeric value as your own foreign key. The lookup that turns an external identity into a SuperSaaS one.
- Create User Creates a new user with contact details, timezone, credit balance, role, and custom fields. Duplicate Handling controls whether a repeated name raises an error or is quietly ignored, which is worth setting deliberately in any sync.
- Update User Updates an existing user by internal ID or foreign key, changing only the fields supplied. Not Found Handling decides whether a missing user returns an error or is silently ignored, so a drifting mapping can hide behind successful calls.
- Delete User Permanently deletes a user by internal ID or foreign key, removing the record from the account. The operation is irreversible and can be driven by an identifier owned by another system, so it is routed for confirmation.
Forms
1- List Form Submissions Retrieves submissions for a standalone form by its form ID, optionally filtered by time or user and paginated. The way to pull intake or registration data that was collected outside a specific booking.
Triggers
1 triggersEvent Triggers
1- On New Appointment Fires when a new appointment is booked on the selected schedule, emitting the raw booking object. The first poll establishes a baseline without firing, so pre-existing appointments are never replayed into a flow. Only appointments created after monitoring begins trigger it, and the polling interval is configurable down to thirty seconds.
Frequently Asked Questions
What can FlowRunner do with SuperSaaS?
FlowRunner agents can run List Schedules, List Resources, and List Appointments in SuperSaaS, plus 14 more actions.
Does connecting SuperSaaS to FlowRunner require OAuth?
No. SuperSaaS connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can SuperSaaS trigger a FlowRunner workflow automatically?
Yes. SuperSaaS supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with SuperSaaS
$100 in credits. No card required. Connect in minutes.