--- title: "EasyWeek Integration" description: "Connect AI agents to EasyWeek, appointment scheduling software for service businesses. Agents check real-time availability, create and reschedule bookings, and look up staff and services so schedules stay full without manual coordination." url: https://flowrunner.ai/integrations/easyweek date_modified: 2026-08-12T15:40:33-07:00 --- # EasyWeek [Scheduling](https://flowrunner.ai/integrations/category/project-management-productivity) Connect AI agents to EasyWeek, appointment scheduling software for service businesses. Agents check real-time availability, create and reschedule bookings, and look up staff and services so schedules stay full without manual coordination. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 14 actions · API key · available [EasyWeek website](https://easyweek.io/) · [Platform Documentation](https://developers.easyweek.io) · Capability data verified 2026-08-10 1. An end of day sweep reads every booking reserved for today across all locations 2. Get Booking loads the timing, staff member, service, and order total for each one 3. Get Booking Statuses separates the still in progress bookings from the settled ones 4. Front desk payment records are matched against each booking total in minor units 5. Any booking without a matching payment goes to the location manager with the detail 6. Manager confirms the paid amount before Complete Booking closes the record for good ## What This Integration Enables EasyWeek is built for service businesses that run more than one room and more than one person: salons, clinics, studios, workshops. The object at the center is not a calendar entry, it is a staff member's day at a specific location. Everything hangs off that. Locations carry their own opening hours, timezone, and address. Staff are listed per location with their service category. Services are priced per location in minor currency units. Availability is resolved for a service at a location, optionally narrowed to one staff member, in the customer's own timezone. Agents work through that hierarchy in order, then create the booking, which matches or creates the customer from their phone number and name in the same call. What separates EasyWeek from a generic appointment API is the lifecycle on the other side of the booking. Reschedule Booking can move it and optionally tell the customer. Cancel Booking records a reason, an internal note, and which staff member performed it. Complete Booking marks it done and records the payment against a financial account. And the platform enforces the one way door: a booking that is already completed or canceled cannot be rescheduled or canceled again. Agents run the whole front half without supervision. The state that cannot be reopened is where a person gets asked. Every action is built and verified against the EasyWeek API. ### Without FlowRunner **Availability guessed over the phone**: Reception offers a time, then checks whether the stylist or clinician is actually free **Day sheets rebuilt per location**: Each branch keeps its own view of tomorrow and head office reconciles them later **Close-out done from memory**: Bookings are marked complete at the end of a shift with the amount recalled rather than checked ### With FlowRunner **Real openings offered first**: Get Available Time Slots returns bookable times for the service, location, and staff member in the customer's timezone **One workspace, every branch**: List Locations and List Bookings give head office the same picture the branch has **Completion approved with the number**: Complete Booking runs on a confirmed amount, because the state it writes is final ## Use Case Scenarios ### Booking Request to Confirmed Appointment A client submits a request through a form built in [Typeform](https://flowrunner.ai/integrations/typeform), choosing a service and a preferred window. The agent runs List Locations to resolve the branch, List Services to find the service UUID and its price, and List Staff when the client asked for a specific practitioner. It calls Get Available Time Slots across the requested date range with the client's timezone passed through, so the options it offers are in the client's local time and not the branch's. It books the first fitting slot with Create Booking, which matches the client by phone number or creates them, and confirms by email through [Gmail](https://flowrunner.ai/integrations/gmail-service). Reception never plays telephone tag over a time that turns out to be taken. ### Tomorrow's Sheet and the Reschedules It Produces Each afternoon the agent runs List Bookings filtered to the upcoming state for every location, and sends each client a reminder with the service, the practitioner, and the address. Replies asking to move are handled directly: the agent finds the booking, calls Get Available Time Slots for the same service and staff member, offers the nearest alternatives, and applies the change with Reschedule Booking, with the customer notification enabled so the change is confirmed rather than silent. Any booking whose client cannot be reached becomes an [automation exception](https://flowrunner.ai/concepts/automation-exceptions) posted to the branch channel in [Slack](https://flowrunner.ai/integrations/slack) with the phone number already attached. ### Revenue and Utilization Across Branches Head office wants to see which services and which practitioners actually fill their day. Every night the agent runs List Bookings per location across the day's window, resolves each staff member through List Staff and each service through List Services, and writes a row per booking into [Google Sheets](https://flowrunner.ai/integrations/google-sheets) with the state, the duration, and the order total converted once from minor currency units. Get Workspace supplies the currency and locale so the figures are labeled correctly rather than assumed. The result is a single utilization view that does not depend on each branch reporting the same way. ## Human-in-Loop Highlight Complete Booking is the terminal state in EasyWeek, and it carries money. It marks the appointment as completed and records the payment against a financial account, defaulting to the booking total unless a specific amount is supplied. Once it has run, the platform will not let that booking be rescheduled or canceled again. So an agent that completes a no show, completes at full price when the client paid a deposit, or completes the wrong appointment on a busy afternoon has written a financial record the branch has to correct outside the system. That is why the agent prepares the close-out rather than performing it. It runs List Bookings for the day, Get Booking for the totals, and matches each against the payments the front desk recorded, then routes the gaps to the location manager: "Booking \[id\], \[client\] with \[staff member\] at \[time\], service \[name\], total \[amount\]. No matching payment found. Complete at \[amount\], complete at a different amount, cancel with a reason, or leave open?" The manager answers, and the agent runs Complete Booking with the confirmed figure or Cancel Booking with the confirmed reason, then logs which manager decided. Availability checks, bookings, reminders, reschedules, and note updates all run without asking. The one call that closes the record and books the money does not. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 14 actions ### Workspace and Catalog 4 - **Get Workspace** Retrieves the connected workspace profile, including its name, booking domain, country, locale, currency, brand colors, and contact details. Used as a connection check and to label monetary figures correctly downstream. - **List Locations** Lists the branches configured in the workspace with names, opening hours, timezone, and address. The location UUID scopes staff, services, availability, and bookings. - **List Staff** Lists the staff members working at a given location with their name, position, description, and service category. Used to resolve a practitioner before filtering availability or assigning a booking. - **List Services** Lists the bookable services at a location with price in minor currency units, duration, and category, optionally filtered by category or by staff member. ### Availability and Booking 4 - **Get Available Time Slots** Retrieves bookable slots for a service at a location across a date range, grouped by date with start and end times, remaining quantity, and price. Pass the customer timezone so the options offered are in their local time. - **Create Booking** Creates an appointment for a customer at a location for a service and start time. The customer is matched or created from their phone number and name. Assign a staff member explicitly or leave it to EasyWeek. Take the reserved time from Get Available Time Slots. - **Get Booking** Retrieves a single booking by UUID with its timing, timezone, duration, completion and cancellation flags, public notes, currency, and order total. - **List Bookings** Lists bookings with filtering by lifecycle state, location, staff member, customer, status, and reserved or created date ranges. The basis for day sheets, reminders, and utilization reporting. ### Booking Lifecycle 5 - **Reschedule Booking** Moves a booking to a new start time, optionally notifying the customer. A booking that is already completed or canceled cannot be rescheduled. - **Cancel Booking** Cancels a booking and marks it canceled, optionally recording a reason, an internal note, and the staff member who performed it. A booking that is already completed or canceled cannot be canceled again. - **Complete Booking** Marks a booking completed and records the payment against a financial account, using the booking total unless a specific amount is supplied. This is a final state and is routed for human confirmation of the amount. - **Update Booking Notes** Sets the public notes on a booking, replacing any existing note text. Public notes are visible on the record and can carry customer facing context. - **Get Booking Statuses** Retrieves the non-final, in progress booking statuses configured in the workspace, each with a UUID and display name. Used to filter List Bookings to work that is still open. ### Customers 1 - **List Customers** Lists customers in the workspace with exact match lookup by phone number or email, case insensitive on email. Used to resolve an existing customer UUID before booking or filtering. ## Frequently Asked Questions ### What can FlowRunner do with EasyWeek? FlowRunner agents can run Get Workspace, List Locations, and List Staff in EasyWeek, plus 11 more actions. ### Does connecting EasyWeek to FlowRunner require OAuth? No. EasyWeek connects to FlowRunner with an API key, no OAuth flow required. ### Can EasyWeek trigger a FlowRunner workflow automatically? EasyWeek doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at EasyWeek?** This integration exposes EasyWeek to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/easyweek. Site index: https://flowrunner.ai/llms.txt