Sign In Scheduling (10to8)
SchedulingConnect AI agents to Sign In Scheduling, the online appointment booking platform formerly known as 10to8. Agents look up services, staff, and locations, find open slots, and book appointments for customers so scheduling requests get handled without staff intervention.
What This Integration Enables
Look at the shape of this connector before anything else. Six of the seven operations read, and exactly one writes. Get Organisation, List Services, List Staff, List Locations, List Booking Questions, and Find Available Slots describe a business and its openings. Book Appointment commits a slot. That is the whole surface, and it is not an oversight. Sign In Scheduling's Booking API v2 exists to power the customer-facing booking funnel, so it exposes precisely what a booking experience needs and nothing beyond it. There is no cancel, no reschedule, and no way to read appointments that already exist, because those are the business's internal concerns and they live inside the product.
Understanding that shape tells you what to build. This connector is how an agent replaces a booking widget with a conversation. Somebody asks a question in a channel they already use, and the agent answers with the services this business actually offers, the sites where they are offered, the staff qualified to deliver them, and real open times narrowed to what the customer asked for. Because List Booking Questions returns the custom questions the organization asks during booking, the agent can collect what the business needs before the slot is taken rather than at the door. One honest note on naming: 10to8 has been rebranded to Sign In Scheduling as part of Sign In App, and the Booking API v2 remains live on the legacy host, so both names refer to the same platform. Every read runs on the agent's own judgment. The single write commits a real person to a real time and the platform typically notifies them, so it sits behind a human-in-the-loop gate. Every operation is built and verified against the Sign In Scheduling Booking API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The Booking Conversation Replaces the Booking Page
An inquiry arrives asking whether anyone can look at a boiler this week. The agent runs List Services to find the matching service and its duration, then List Locations to work out which site covers the customer's service area. Find Available Slots returns real openings for that service across the next five days, optionally narrowed to the engineers qualified for it. The agent replies through Gmail with three concrete times and the questions List Booking Questions says this business asks. The customer picks a time and answers, and Book Appointment commits it. No booking page, no back and forth about availability, and no diary opened by a member of staff.
Keeping the Catalog Honest Somewhere Else
Service menus drift. A price changes, a location closes, an engineer leaves, and the version on the website, in the CRM, and in the quoting sheet all fall out of step at different speeds. Each night the agent runs Get Organisation, List Services, List Staff, and List Locations, and writes the results to Google Sheets as the single source the other systems reconcile against. Anything that changed since the previous run is posted to the operations channel in Slack as a short diff. The platform where bookings actually happen becomes the record everything else follows.
Watching the Openings Nobody Is Filling
Empty capacity is invisible until it has already been lost. Every morning the agent runs Find Available Slots for the next three days per service and per location, and counts the openings that remain. Where a site or a service is holding more free capacity than it should at that lead time, the agent posts the figure to the branch manager with the specific gaps listed. It also checks the same window against the campaigns running in HubSpot, so the team can see whether demand or promotion is the thing that is short. The agent reports the gap. It does not fill it by booking anyone.
Human-in-Loop Highlight
Sign In Scheduling puts the instruction in its own documentation: book only real, consented appointments, because the action writes live data and typically notifies the customer. That is the gate, and it is a gate about consent rather than about reversibility. Book Appointment creates or matches a customer from a name, an email, and a mobile number, and then commits that named human to a time and a place. An agent that runs it is asserting something it cannot verify on its own, namely that this person asked for this appointment. There is a second edge to it. List Booking Questions exists precisely because the business decided some things must be known before a visit, but nothing in the API forces those answers to be present, so an agent can book a slot that staff cannot properly prepare for. The rule the agent follows is simple. When the customer picked the time themselves, in their own words, and answered the questions the business asks, it books. When the request came secondhand, from a colleague, a CRM field, a lead form somebody else filled in, or a conversation where the person never actually chose a slot, it stops and asks staff: "Booking a same-day plumbing visit for [name] at 14:00, based on a note in the CRM. The customer has not confirmed the time and two required questions are unanswered. Book it, or contact them first?"
Agent Capabilities
7 actionsOrganization
1- Get Organisation Returns the organization details for the account tied to your API key, including its name, contact information, and public booking configuration. The right first call to confirm the token is valid and to see which business it belongs to.
Catalog
4- List Services Lists the bookable services offered by the organization with each one's name, duration, and identifier. The service identifier is what Find Available Slots and Book Appointment both work against.
- List Staff Lists the staff members, meaning the bookable resources, with each member's name and identifier. Use a staff identifier to narrow availability to the people qualified for a service, or to assign a specific person to a booking.
- List Locations Lists the physical or virtual locations where the organization offers appointments, including each location's name, address, and identifier. The read that turns a customer's service area into the right site.
- List Booking Questions Lists the custom questions the organization asks customers during booking, with each question's prompt, type, and identifier. These are what a business needs to know before a visit, so collect them before the slot is committed.
Availability and Booking
2- Find Available Slots Queries open appointment slots within a date range, optionally narrowed to a specific service, staff member, or location. Start and end are ISO 8601 timestamps, and the returned start and end times feed straight into Book Appointment.
- Book Appointment Books a new appointment against an available slot, taking the service, the slot times, optionally a staff member and location, and the customer's name, email, and mobile number. The platform creates or matches the customer. This writes live data and typically notifies the customer, so it is routed for confirmation whenever consent is secondhand.
Frequently Asked Questions
What can FlowRunner do with Sign In Scheduling (10to8)?
FlowRunner agents can run Get Organisation, List Services, and List Staff in Sign In Scheduling (10to8), plus 4 more actions.
Does connecting Sign In Scheduling (10to8) to FlowRunner require OAuth?
No. Sign In Scheduling (10to8) connects to FlowRunner with an API key, no OAuth flow required.
Can Sign In Scheduling (10to8) trigger a FlowRunner workflow automatically?
Sign In Scheduling (10to8) doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Sign In Scheduling (10to8)
$100 in credits. No card required. Connect in minutes.