OnceHub (ScheduleOnce)
SchedulingRead bookings and their customer details from OnceHub (formerly ScheduleOnce). Agents browse booking pages and master pages, manage contacts, and look up team members to route follow-ups when meetings are scheduled, rescheduled, or canceled.
What This Integration Enables
Scheduling platforms hold the most perishable data in the go-to-market stack: a booking is only useful before it happens, and a cancellation is only actionable right after. OnceHub organizes that data well, booking pages per team member, master pages grouping them behind one link, statuses from Scheduled through No Show, and FlowRunner agents move it while it still matters. They read bookings with their customer details, map pages to owners, maintain the contact list from external lead capture, and route follow-ups the moment a meeting is scheduled, rescheduled, or canceled. - Sync new and upcoming bookings into a CRM, [Google Sheets](/integrations/google-sheets), or a warehouse - Alert the team in [Slack](/integrations/slack) when meetings are scheduled, rescheduled, or canceled - Enrich booking records with customer details before routing follow-up automations - Cross-reference meetings against [Calendly](/integrations/calendly) when both platforms are in play - Store new customers as contacts, matched by email, so records exist exactly once - Map booking and master pages to owners via the user list for accountable routing The page structure is what makes routing precise. Because each booking page is a bookable calendar usually tied to one team member, and master pages group them by service or team, an agent reading List Booking Pages and List Master Pages can answer "whose meeting is this and what kind is it" without any lookup table maintained by hand, and that answer drives every notification and follow-up downstream.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The 8 am meeting sheet
Every morning, List Bookings pulls the day with a starting-time lower bound, and each result appends to the day sheet in [Google Sheets](/integrations/google-sheets): page, customer, time, status. Overnight changes stand out because yesterday evening's snapshot sits one tab over. The [Slack](/integrations/slack) digest tags each meeting's owner, resolved through List Users from the booking page. Reps start the day knowing their schedule moved, instead of finding out at the meeting.
The cancellation that becomes a reschedule
A sweep finds a booking flipped to Canceled. Get Booking pulls the customer's details and the original event type, and the flow opens a follow-up: an alert to the owning rep with context, plus a draft reschedule note with the booking page link. Sent within the hour, a cancellation is a calendar collision to fix. Discovered next week, it is a cold lead.
One customer, one record, every system
A demo booking arrives from a customer nobody has seen before. The agent checks List Contacts by email, finds nothing, and calls Create Contact with the booking's name and email so OnceHub's own records stay clean, then mirrors the same person into the CRM. When that customer books again through a different master page, the email match finds the existing record and the follow-up thread continues instead of restarting from hello.
Human-in-Loop Highlight
Create Contact is the single write in this connector, and FlowRunner flows guard it with an email-first match against List Contacts, because a scheduling account where the same customer exists three times will misroute every automation built on top of it. But the sharper judgment call in OnceHub flows is what to do with a status. List Bookings reports No Show as a distinct state, and a no-show is the most delicate trigger in scheduling automation: fire a "sorry we missed you" sequence at someone who actually attended, or who canceled properly, and you have told a prospect your systems do not know who they met with. So status-driven outreach to Canceled and No Show customers routes through the sales lead first: the agent assembles the list, the booking evidence, and the drafted messages, and a person who was in the room, or can ask someone who was, approves before anything reaches the customer. Reads are cheap. What you send based on them is not.
Agent Capabilities
8 actionsBookings
2- List Bookings Retrieves scheduled bookings with filters by booking page, status across Scheduled, Rescheduled, Canceled, Completed, and No Show, and a starting-time lower bound, paginated by cursor. The sweep behind every sync and digest.
- Get Booking Retrieves one booking by ID with scheduling details, status, its booking page, and customer information. The enrichment step before routing any follow-up.
Booking Pages
2- List Booking Pages Lists the account's booking pages, each a bookable calendar typically tied to a team member with its own availability and event types. The routing table for ownership.
- List Master Pages Lists the master pages that group booking pages behind a single link where customers pick a person or service first. The structural read for understanding how demand enters the account.
Contacts
3- List Contacts Lists stored customers with an optional email filter for targeted lookup, paginated by cursor. The match step that keeps every human a single record.
- Get Contact Retrieves one contact by ID with name, email, phone, and stored metadata. The detail read behind follow-up personalization.
- Create Contact Creates a new customer record from an email plus optional names, returning the assigned ID. The connector's one write, always preceded by an email match.
Users
1- List Users Lists the account's team members with names, emails, and roles. The mapping read that connects bookings and pages to the people accountable for them.
Frequently Asked Questions
What can FlowRunner do with OnceHub (ScheduleOnce)?
FlowRunner agents can run List Bookings, Get Booking, and List Booking Pages in OnceHub (ScheduleOnce), plus 5 more actions.
Does connecting OnceHub (ScheduleOnce) to FlowRunner require OAuth?
No. OnceHub (ScheduleOnce) connects to FlowRunner with an API key, no OAuth flow required.
Can OnceHub (ScheduleOnce) trigger a FlowRunner workflow automatically?
OnceHub (ScheduleOnce) doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with OnceHub (ScheduleOnce)
$100 in credits. No card required. Connect in minutes.