Plugins
Each capability is a plugin your venue switches on, with settings your assistant can read and change (asking first). A service you already use plugs in the same way, and your assistant uses its tools beside the venue’s own.
Nothing here depends on you using the rest. A venue that keeps every tool it has and adds only the record and the rules has the whole product.
Showing the copy saved on 12 October 2026. 27 plugins. The hosted service will publish the live list.
Where guests find you and buy from you.
A website for the venue: pages built from ready-made blocks, your brand, hours and menu, on your own domain or a free Pipedline address.
Needs
Reads menu, hours, specials. Writes pages, brand, redirects.
page_copy — Read the words on a page of the venue's site.page_update_copy — Change the words on a page, after the owner says yes. Asks first.A QR code on each table that opens the menu. At the next stage, guests order and pay from the table.
Needs
Reads menu, specials. Writes table sessions, orders.
Pickup and table orders from the venue's own site: cart, time slots paced to the kitchen, checkout, payment, and the kitchen order screen.
Needs
Reads menu, hours. Writes orders, payments, kitchen tickets.
orders_list — Orders in progress or from a day, with their status.order_decide — Accept or decline an order that is waiting, after the owner says yes. Asks first.Delivery from the venue's own site: zones you draw, courier quotes, dispatch timed so food leaves when it is ready, and tracking for the guest.
Needs
Reads orders. Writes deliveries.
deliveries_summary — How deliveries went over a period: count, on time, failed.Guests book a table for a time and party size on the venue's site or through an assistant; staff confirm, seat and manage bookings. Capacity is counted in guests per time slot and per service, without a floor plan.
Needs
Reads hours, guests. Writes bookings, messages.
bookings_today — Today's bookings by service, with covers.bookings_list — Bookings for a date range, by status.booking_availability — Which times still have room for a party size.booking_confirm — Confirm a booking that is waiting for the venue. The guest is sent a confirmation. Asks first.booking_decline — Turn down a booking that is waiting. The guest is told, with the reason if one is given. Asks first.booking_cancel — Cancel a booking for the guest. The guest is told and the places are freed. Asks first.booking_add — Add a booking taken over the phone or at the door. Asks first.Lists the venue on Pipedline's public assistant connection, so a guest using ChatGPT or Claude can find it, read the menu and hours, book a table and start a pickup order. Payment always happens on the venue's own order page. Alcohol is never orderable this way.
Needs
Reads menu, hours, booking availability, pickup slots. Writes bookings, carts.
The menu, and what goes with it.
One menu for the website, the QR codes, online ordering and guests' assistants: sections, items, options, prices and what is sold out. Part of every venue.
Writes menu.
menu_list — The menu as guests see it, with prices and what is sold out.menu_set_availability — Mark an item sold out or back on, after the owner says yes. Asks first.Daily or weekly specials a manager posts with a name, a price and the days they run. Guests see the ones running today.
Needs
Writes specials.
specials_list — The specials running or scheduled.special_post — Post a special with a name, a price and the days it runs, after the owner says yes. Asks first.special_end — Take a special off the board now, before its last day. Asks first.Offers and vouchers with a unique code per guest: click-to-claim offers, creator offers, and redemption at the counter.
Needs
Reads guests, sales. Writes offers, codes.
offers_summary — How offers performed: claimed, redeemed, and what they brought in.Who they are, what they agreed to, how you keep them.
Who your guests are, how they are recognised across visits, and what each one has agreed to. Part of every venue.
Writes guests, consents.
guest_lookup — Find a guest by name, email or phone, and see their visits and what they agreed to.Points, tiers and rewards across the venue group, earned on sales and redeemed at the counter.
Needs
Reads sales, guests. Writes points, rewards, messages.
loyalty_summary — Members, points earned and redeemed, and who is close to a reward.Reviews from connected listings, with replies drafted for a person to approve before anything is posted.
Needs
Reads reviews. Writes reply drafts.
reviews_list — Recent reviews, with rating and whether a reply is waiting.review_reply_draft — Draft a reply for a person to approve. Nothing is posted until they do. Asks first.Messages that go out, with a yes first.
Groups of guests, emails that send themselves (welcome, after a visit, win-back, VIP, birthday) and one-off campaigns, each batch approved by a person.
Needs
Reads guests, consents, sales. Writes campaigns, messages.
campaigns_summary — What went out, to how many, and what came back.message_draft — Draft a message to a group of guests. It is sent only after a person approves the batch. Asks first.The outbox every message goes through: email and texts, templates, who it is sent as, unsubscribes and delivery results. Part of every venue.
Needs
Reads consents. Writes messages.
The record, and the numbers from it.
The measures a venue needs, each defined once: sales, guests, menu, campaigns, saved views and a weekly digest, for people and for assistants. Part of every venue.
Needs
Reads sales, guests, orders, events. Writes saved views, digests.
metrics_catalogue — Every measure, with its exact definition.metrics_query — Any measure over a period, with comparisons.sales_summary — Sales for a period against the one before.customers_summary — New, returning and lapsed guests.menu_performance — Which items sell, and when.funnel_report — From a visit to the site to an order or booking.campaign_outcomes — What a campaign brought in.insights_digest — The weekly digest in plain words.event_dictionary — Everything that is recorded, and what each entry means.saved_view_run — Run a report the venue saved.The record of what was sold, kept as it happened: every sale and its lines, from the till or from online ordering. Nothing in it is ever edited or deleted. Part of every venue.
Needs
Writes sales.
connection_start — Give the owner a sign-in link for a service such as Square. The assistant never handles a password. Asks first.The assistant connection, approvals, and going live.
The connection the venue's own assistant uses: sign-in, access keys, a log of every call, a yes from a person before any change, and services that plug in. Part of every venue.
Reads everything the connected assistant is allowed to read, by role. Writes the log of what the assistant did.
ops_status — Is everything running: connections, queues, the last digest.The queue of things waiting for a person's yes, and the record of what was decided. Part of every venue.
Writes approvals.
What is done, what is next, and what only the owner can answer. Menu import from a link, a file or the till. The checks before a venue goes public, and go-live. Part of every venue.
Reads venue details, menu, connections. Writes menu, the venue's live status.
setup_status — What is done, what is next, what only the owner can answer. The first thing an assistant calls.menu_import_start — Bring a menu in from a link, a file or the till. Asks first.menu_import_review — What the import found, for the owner to check.menu_import_confirm — Save the imported menu, after the owner says yes. Asks first.go_live_check — What is missing before the venue can be public.go_live_test_email — Send a test email to the owner, to prove sending works. Asks first.go_live_confirm — The owner confirms the checks. Asks first.go_live — Make the venue public, after the owner says yes. Asks first.The venue's name, address, hours and time zone, its domains, which plugins are on, and what is connected. Part of every venue.
Writes venue details, hours, which plugins are on.
venue_status — Open or closed now, today's hours, and what is switched on.venue_describe — Name, address, hours, time zone, cuisine.venue_update — Change the venue's details, after the owner says yes. Asks first.hours_set_exception — Set different hours for one day, such as a public holiday. Asks first.plugins_list — Every plugin: what it does, what it needs, whether it is on.plugin_enable — Switch a plugin on, with settings checked against its rules. Asks first.plugin_configure — Change a plugin's settings. Asks first.plugin_disable — Switch a plugin off. Its data and settings are kept. Asks first.connections_list — What is connected, its health, what it can read and write.Who can sign in and what they may do: staff and their roles, guest sign-in, and paired kitchen screens. Part of every venue.
Writes staff, roles.
team_invite — Invite a staff member with a role, after the owner says yes. Asks first.Services you already use, plugged in.
Connects to Square
Sales, line items and refunds from Square, online card payments, and online orders sent to the Square till.
Needs
Reads sales, refunds. Writes online orders, sent to the till.
Connects to Klaviyo
Keep your Klaviyo flows. We push guests who agreed to marketing, their consent and their orders, and bring Klaviyo unsubscribes back.
Needs
Reads unsubscribes from Klaviyo. Writes guests who agreed to marketing, their consent and their orders, to Klaviyo.
Connects to Criota
Creator campaigns for the venue: campaigns, applications, drafts to review and results, from the venue's own Criota account.
Needs
Reads campaigns, applications and drafts, from Criota. Writes campaign outcomes, to Criota.
Connects to Meta Conversions API
Tell Meta about purchases by guests who agreed to it, so ads are measured on real sales. Hashed email and phone and the amount only.
Needs
Writes purchases by guests who agreed, hashed, to Meta.
Connects to Uber Direct
Uber couriers for orders placed on the venue's own site. Quotes, dispatch, tracking and proof of delivery.
Needs
Reads quotes and courier status, from Uber. Writes delivery requests, to Uber.
Connects to DoorDash Drive
DoorDash couriers for orders placed on the venue's own site. Quotes, dispatch, tracking and proof of delivery.
Needs
Reads quotes and courier status, from DoorDash. Writes delivery requests, to DoorDash.
Plugins are open. A capability that needs the venue’s own records is a module merged into the engine; a service you already run is a plug with its own tools. The guide is written for a developer who has never seen the repository.
Start a venue, connect Claude or ChatGPT, and say “set my venue up”. It lists these plugins, asks what you want, and switches each one on when you say yes.