FlowRunner
PricingContact
Theme
Start Free

Booqable

E-commerce

Connect AI agents to Booqable, rental business management software. Agents create and reschedule rental orders, check equipment availability, move orders through pickup and return, and generate the paperwork each stage needs.

1 trigger 29 actions API key available
A booking request arrives from a form, a shop or a partner system
The requested products, quantity, rental period and pickup location are read from the request
Check Inventory Availability returns how many units can actually be booked for that exact period
Create Order opens the order and Book Product On Order allocates the inventory
The order is read back to confirm no shortage flag was raised on any line
The rental desk receives the order, its period, and any line that came back short
A person decides before Confirm Shortage is used to book past a shortage

What This Integration Enables

Rental software has one constraint that sales software does not: the same physical unit cannot go out twice. Everything interesting about Booqable follows from that. Inventory is not a number to decrement, it is a calendar, and availability is a question about a period and a location rather than about a count. This connector is built around that shape. Check Inventory Availability answers how many units of one or more products can be booked for an exact window at a given location. List Plannings shows booked quantities, reservation windows and start or stop progress per product. Stock items are individual physical units with their own status and current location, so serial numbered kit can be booked specifically rather than generically through Book Stock Items On Order. The order lifecycle is explicit rather than implied: Create Order opens a period, Book Product On Order allocates inventory and creates the planning and line together, Transition Order Status moves the order to reserved to hold that inventory and assign an order number, Start Order Product marks units as picked up or delivered, and Stop Order Product marks them returned.

A handful of platform facts change how a flow should be written. Booqable serves every account from its own subdomain, so configuration is a company slug alongside the access token you create under Authentication Methods in your user settings. The connector targets the v4 API, which follows JSON:API and which Booqable documents as being in beta with the right to make changes that are not backwards compatible reserved, so treat schema stability as a thing to monitor rather than assume. Responses come back as Booqable sends them, with records under data and fields in data.attributes, and most read actions accept an Include parameter that sideloads related records in the same request. All money is integers in cents, which matters most for Set Line Price. There is one trap in the object model worth naming: rental items must be added with Book Product On Order, because lines created through the Lines resource are custom charge lines that do not allocate any inventory, which produces an order that looks complete and reserves nothing. Deleting a customer or a document archives it rather than destroying it, which is a kinder default than most. And this connector does have a realtime trigger, On Booqable Event, covering orders, customers, invoices, quotes, contracts, payments, completed carts and products. Agents keep the calendar, the customer record and the paperwork in step. The decision to book past a shortage is where human-in-the-loop oversight belongs.

Without FlowRunner

Availability answered from memory Somebody checks a wall planner or their own recollection, and two customers are promised the same three lights for Saturday
Orders held in a chat thread A booking is agreed by message, entered later, and the period that gets typed is not always the period that was agreed
Paperwork produced item by item Quotes, contracts and invoices are written up separately per booking, and the invoice is finalised whenever somebody gets to it

With FlowRunner

Availability checked against the period Check Inventory Availability answers for an exact rental window and location before anything is promised
The order is the record Create Order, Book Product On Order and Transition Order Status carry the booking from request to reserved with an order number attached
Documents issued from the order Create Document issues the quote, contract or invoice against the order it belongs to, and finalising is a deliberate step

Use Case Scenarios

A booking request that is answered against the calendar, not against a total

A request arrives from a web form or a partner for four cameras and two tripods from Friday to Monday, collected from the city location. The agent's first call is Check Inventory Availability for those products across that exact period at that location, which is a different question from how many cameras exist. If everything is free it calls Create Order for the period with the customer, locations, deposit and any discount, then Book Product On Order for each product and quantity, which creates the planning and the line together and actually allocates the units. Serial numbered kit that the customer asked for specifically goes through Book Stock Items On Order instead. Only when the order reads back clean does the agent call Transition Order Status to move it to reserved, which is the moment the inventory is genuinely held and the order number is assigned, and the confirmation to the customer quotes that number rather than an internal ID. If availability comes back short on any line, the flow does not improvise: it reports what is available for that window and asks.

Out on Friday, back on Monday, billed on Tuesday

Fulfilment is where a rental business either keeps its margin or loses it. When kit leaves the counter the agent calls Start Order Product to mark the booked units picked up or delivered, and List Plannings gives the warehouse view of what is out, what is due, and what has been started but not stopped. On return, Stop Order Product marks units back in, and the difference between the planned return and the actual one is the number the desk cares about. From there the paperwork follows the order rather than the other way round: Create Document issues the quote, contract or invoice against the order, Get Document returns it including its signature URL once signed, and Finalize Invoice closes the current pro forma invoice. A realtime On Booqable Event subscription on invoices and started or stopped orders drives the notifications, so the warehouse channel in Slack hears about a reserved order for tomorrow morning and finance hears about a finalised invoice, without either team polling a screen.

Customers and catalogue kept current from the systems that already know

Walk in customers, event enquiries and marketplace bookings all arrive somewhere other than Booqable. The agent reads them from a sheet in Google Sheets or a form and calls Create Customer with contact details, addresses and custom properties, or Update Customer where the person already exists, matching on email through the search filters on List Customers so the same customer does not accumulate three records. Lifetime revenue and balance metrics come back on the customer list, which makes it cheap to flag a booking from an account carrying an outstanding balance before the kit goes out rather than after. On the catalogue side, Create Product Group adds a rental item, sales item or service with its pricing model, Update Product Group adjusts pricing, SKU, store visibility or shortage rules, and Create Stock Item adds an individual unit including temporary or subrented stock, which is how a hire in for one busy weekend gets tracked like everything else. Archive Customer soft deletes without destroying order history, so a lapsed account can be tidied away without losing what it rented.

Human-in-Loop Highlight

The gate here is not an order status, it is a toggle. Changing a rental period, a quantity or a location can produce a shortage, meaning the units are already committed to somebody else for part of that window. Booqable does the right thing and returns an error. The relevant actions then expose a Confirm Shortage toggle that proceeds anyway, and that toggle only works when the affected product group is configured to allow shortage. Read that sequence again from an agent's point of view: the platform raised an objection, and there is a parameter whose entire purpose is to overrule it. An agent with a retry rule and a permissive prompt will find that parameter, because setting it makes the error go away and the flow complete. What it actually does is double book physical equipment. The consequence is not a failed API call, it is two customers arriving on Saturday morning for the same four lights, and the one who loses is whoever turns up second. Nothing downstream catches it either, because from Booqable's side the booking is now legitimate: the shortage was confirmed, the planning exists, the order reserved cleanly. So this connector's rule is simple. An agent may check, build, book and reserve on its own. It may never set Confirm Shortage. When Book Product On Order or Update Order comes back with a shortage, the agent gathers the evidence instead: Check Inventory Availability for the requested window, List Plannings for the reservations already sitting across it, and List Stock Items for the individual units and where they currently are. Then it posts to the rental desk in Slack: "Order 4471, Meridian Studios, Fri 14 Mar to Mon 17 Mar, city location. Booking 4 units of Aputure 600D came back short. 2 units are free for the full window. 1 unit is on order 4408 until Saturday 14:00 and could cover Sat evening to Mon. 1 unit has no coverage in the window. Confirm Shortage would book all 4 anyway and hold nothing back for order 4408. Book the 2 available, book 3 with the Saturday handover, sub rent the fourth, or call the customer?" A person answers, and the agent books exactly what was released and nothing more. Set Line Price belongs behind the same gate for a smaller reason with a similar shape, since it takes an amount in cents and switches the line to manual pricing, so a figure carried in as 95 rather than 9500 sets a four day hire to ninety five cents and the order still totals cleanly. This is the digital andon cord placed on the one parameter in a rental system that lets software promise the same object to two people.

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

29 actions

Orders

5
  • List Orders Returns paged orders with filtering by status, payment status, customer, rental period and free text search.
  • Get Order Fetches one order with its totals, deposit amounts, statuses and shortage flags. The shortage flags are the field worth reading after any booking write.
  • Create Order Opens a new order for a rental period, optionally assigning the customer, the pickup and return locations, a deposit and a discount.
  • Update Order Reschedules the period, reassigns the customer or locations, or applies a coupon. Rescheduling is one of the operations that can raise a shortage.
  • Transition Order Status Moves an order to draft, reserved, archived or canceled, or reverts it to an earlier status. Reserved is the transition that genuinely holds the inventory and assigns an order number.

Order fulfillment

6
  • Book Product On Order Books a quantity of a product, creating the planning and the line that allocate inventory. This is the correct way to add rental items, because lines created through the Lines resource are custom charge lines that allocate nothing.
  • Book Stock Items On Order Books specific serial numbered units of a trackable product, for when the customer needs a particular body rather than any body.
  • Start Order Product Marks booked units as picked up or delivered, which starts the rental in the operational sense.
  • Stop Order Product Marks started units as returned.
  • Set Line Price Overrides a line price with your own amount in cents and switches that line to manual pricing. The unit is cents, so 9500 is ninety five and 95 is ninety five cents.
  • List Plannings Returns booked quantities, reservation windows and start or stop progress per product, which is the warehouse view of what is out and what is due back.

Customers

5
  • List Customers Returns paged customers with search, email, legal type, tag and archived filters, including lifetime revenue and balance metrics.
  • Get Customer Fetches one customer with their defaults, tags and custom properties.
  • Create Customer Adds a customer along with custom fields and addresses.
  • Update Customer Changes contact details, defaults, tags or properties.
  • Archive Customer Soft deletes a customer while preserving their order history, which is why tidying an account does not lose what it rented.

Inventory

8
  • Search Inventory Searches product groups, product variations and bundles in a single request.
  • List Product Groups Returns the parent records that hold shared pricing, tracking and store settings.
  • Create Product Group Adds a rental item, sales item or service with its pricing model.
  • Update Product Group Changes pricing, SKU, store visibility, sort order or shortage rules. Shortage rules decide whether Confirm Shortage is even available on that product.
  • List Products Returns the bookable product variations, optionally scoped to one product group.
  • Check Inventory Availability Returns how many units of one or more products can be booked for an exact period at a location. This is the question to ask before promising anything, because it is about a window rather than a total.
  • List Stock Items Returns the individual physical units with their status and current location.
  • Create Stock Item Adds a unit to a trackable product, including temporary or subrented stock, which is how kit hired in for one weekend gets tracked properly.

Documents

4
  • List Documents Returns quotes, contracts and invoices with totals, payment state and due dates.
  • Get Document Fetches one document including its signature URL once it has been signed.
  • Create Document Issues a quote, contract or invoice for an order.
  • Finalize Invoice Finalises the current pro forma invoice of an order, which is the step that turns a working total into the number the customer is asked to pay.

Locations

1
  • List Locations Returns the pickup and return locations with their addresses and fulfilment capabilities. Availability is location specific, so this is not a cosmetic read.

Triggers

1 triggers

Event Triggers

1
  • On Booqable Event Registers a version 4 webhook endpoint and starts the flow when a selected event occurs. The supported events cover orders, including updated, reserved, started, stopped, canceled, archived, reverted and saved as draft, along with customers, invoices, quotes, contracts, payments, completed carts and products. The payload carries the event name, the resource type and the affected record under `data`, formatted as nested JSON rather than JSON:API, so it does not have the same shape as a read from this connector. Booqable does not document a signing secret or a signature header for webhook deliveries, so an incoming payload cannot be verified cryptographically. Treat the callback URL as the shared secret and keep it private, and treat an event as a prompt to re read the record with Get Order, Get Customer or Get Document rather than as evidence in itself.

Frequently Asked Questions

What can FlowRunner do with Booqable?

FlowRunner agents can run List Orders, Get Order, and Create Order in Booqable, plus 26 more actions.

Does connecting Booqable to FlowRunner require OAuth?

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

Can Booqable trigger a FlowRunner workflow automatically?

Yes. Booqable supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Booqable

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