FlowRunner
PricingContact
Theme
Start Free

anny

Scheduling

Connect AI agents to anny, a booking platform for rooms, workspaces, equipment, and event locations. Agents check resource availability, create and update bookings, manage customers, and cancel orders so shared spaces stay reserved without manual coordination.

Verified 19 actions API key available
anny website ↗ Platform Documentation ↗ Capability data verified 2026-08-12
A nightly sweep reads tomorrow's reservations across every resource
Get Booking loads each reservation with its resource, service, and customer
Get Resource Availability tests whether an equivalent room is free that day
List Orders confirms whether the reservation sits behind a paid order
Facilities and the booking owner receive the conflict with both options attached
The owner decides which reservation keeps the room before anything is released

What This Integration Enables

anny is a booking system for things rather than for people. The scarce object is a room, a desk, a piece of equipment, or an event location, and everyone in the building is competing for it. Agents read that inventory through List Resources and Get Resource, learn how each item may be booked through List Services and Get Service, and confirm a slot is genuinely open with Get Resource Availability before they commit anything. On the write side they create, reschedule, and cancel reservations, register the person behind each one as a customer, and reconcile the orders that group bookings with their pricing and payment state.

The pair worth noticing is Check In Booking and Check Out Booking. Most booking APIs stop at the reservation and never learn whether it was used. anny closes that loop, which turns a calendar full of optimistic holds into a usage record an operations lead can act on. Agents run the reads and the routine holds on their own. The decisions that take capacity away from a named person go to that person, which is the human-in-the-loop default FlowRunner builds around. Every action is built and verified against the anny Admin API.

Without FlowRunner

Rooms held by habit Recurring holds outlive the project that created them and nobody reclaims the slot
Conflicts found at the door Two teams learn about the double booking when they both show up with guests
No usage record Nobody can tell which reserved desks and rooms were actually occupied

With FlowRunner

Conflicts surfaced overnight List Bookings and Get Resource Availability compare demand against real capacity before the day starts
Releases decided by an owner A room comes free only after the person holding it agrees to give it up
Attendance written to the record Check In Booking and Check Out Booking record real usage against each reservation

Use Case Scenarios

Room Request to Confirmed Reservation

A request lands from an intake form built in Typeform with a date, a headcount, and an equipment list. The agent runs List Resources filtered to the right category, checks each candidate with Get Resource Availability, and picks the smallest room that fits the headcount rather than the first one free. It runs List Customers to find the requester, falls back to Create Customer when there is no match, and holds the room with Create Booking. The confirmation goes out through Gmail with the room name, the time, and the check-in instructions. The requester never has to know which room codes map to which floor.

Reclaiming Capacity Nobody Uses

Every week the agent pulls the previous seven days with List Bookings, then compares each reservation against its Check In Booking record. Reservations that were held and never checked in are collected into a report written to Google Sheets, grouped by team and by resource. The facilities lead sees which recurring holds are consuming the two rooms everyone fights over. The agent does not cancel anything on that report. It hands the owner of each stale hold a message in Slack asking whether the series should continue, and only acts on the replies it gets back.

Cancellation With the Money Attached

A customer cancels a paid workspace booking. The agent runs Get Booking to load the reservation, then Get Order to find the commercial record behind it, because in anny a single order can cover several bookings and canceling one is not the same as canceling all of them. It assembles the order total, the affected bookings, and the organization cancellation rule, and routes the whole picture to the operations owner. On approval it runs Cancel Order, which releases the bookings under that order together, and logs the outcome. Refund handling stays with finance, where it belongs.

Human-in-Loop Highlight

The gate in anny is not creating a booking. It is taking one away. Delete Booking removes a reservation entirely, and the moment the slot is free anyone in the organization can claim it, so there is no undo even if the deletion turns out to be wrong thirty seconds later. Cancel Order is broader still, because it releases every booking grouped under that order according to the organization's cancellation rules. So when an agent is about to free contested capacity, it stops. It posts the evidence to the resource owner in Slack: "Conference Room 4 on Thursday 09:00 to 11:00 is held by [name] and requested by [name]. Get Resource Availability shows no equivalent room of that capacity free that day. Release the hold, keep it, or offer the 14:00 slot instead?" The owner answers, and only then does the agent run Update Booking to reschedule, or Cancel Order if the whole reservation is going. Reads, availability checks, and new holds run without anyone being asked. Anything that removes a room from someone who is counting on it gets a person in the loop.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via Slack
Human decides
Agent resumes with decision

Agent Capabilities

19 actions

Resources and Services

5
  • List Resources Lists the bookable resources in the organization, such as rooms, desks, equipment, and event locations, with filtering by resource group or category. Use it to build the candidate set before checking availability.
  • Get Resource Retrieves a single resource by ID, including its title, description, capacity, and active status. Used when an agent needs the capacity figure before matching a room to a headcount.
  • Get Resource Availability Returns the bookable timeslots configured for a resource. Run this before Create Booking so the hold lands on a slot that is genuinely open rather than one that only looks free.
  • List Services Lists the bookable services the organization offers. A service defines how a resource may be booked, for example a consultation, a rental option, or an event ticket.
  • Get Service Retrieves a single service by its slug, including pricing configuration and booking rules. The slug is the human readable identifier shown in the service URL.

Bookings

5
  • List Bookings Lists reservations with filtering by status, resource, service, and customer email, plus full text search and sorting. Used for weekly utilization reports and for finding the reservation behind a conflict.
  • Get Booking Retrieves a single reservation with its status, start and end dates, and links to the resource, service, and customer. The evidence step before any change is proposed.
  • Create Booking Creates a reservation for a resource and service over a start and end date range, in ISO 8601 format. Optionally sets an initial status and a description.
  • Update Booking Changes an existing reservation: reschedule it with new start and end dates, edit its description, or set its status. The reversible way to take a reservation out of service, by setting the status to Canceled rather than deleting the record.
  • Delete Booking Permanently removes a reservation. The freed slot becomes immediately claimable and the record is gone, so this is routed for confirmation rather than run on the agent's own judgment.

Attendance

2
  • Check In Booking Records that the customer has arrived and the reservation is in use. Run at the start of a booked slot to build a real occupancy record.
  • Check Out Booking Records that the customer has left and the reservation is complete. The other half of the occupancy record, and the signal that a room has come free early.

Customers

4
  • List Customers Lists customers with filtering by email, mobile number, or full text search. Used to find an existing record before creating a duplicate.
  • Get Customer Retrieves a single customer by ID, including name, email, mobile, company, and custom fields.
  • Create Customer Creates a customer record. Email is required; given and family name, mobile, company, and locale are optional. Used to register a requester before booking on their behalf.
  • Update Customer Updates an existing customer record. Only the fields supplied are changed, so a single attribute such as the mobile number can be corrected in isolation.

Orders

3
  • List Orders Lists orders with pagination. An order groups one or more bookings with their pricing and payment information, which makes it the right object for revenue reconciliation.
  • Get Order Retrieves a single order with its status, total, currency, and the bookings and customer attached to it. Run this before any cancellation so the full scope of the release is visible.
  • Cancel Order Cancels an order and the bookings grouped under it, following the organization's cancellation rules. Because the blast radius covers every booking on the order, this is routed for human confirmation.

Frequently Asked Questions

What can FlowRunner do with anny?

FlowRunner agents can run List Resources, Get Resource, and Get Resource Availability in anny, plus 16 more actions.

Does connecting anny to FlowRunner require OAuth?

No. anny connects to FlowRunner with an API key, no OAuth flow required.

Can anny trigger a FlowRunner workflow automatically?

anny doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with anny

$100 in credits. No card required. Connect in minutes.