Integration · E-commerce
AI agents for Toast
Read a Toast restaurant's orders and checks, menus, out-of-stock items, employees, shifts and time entries, and its location details, through Toast's standard API access.
- Actions
- 9
- Read
- 9
- Write
- 0
Actions
What your agents can do in Toast
Read a Toast restaurant's orders and checks, menus, out-of-stock items, employees, shifts and time entries, and its location details, through Toast's standard API access (read-only credentials a restaurant creates in Toast Web).
Read 9
Look things up. Nothing changes.
Get restaurant details
Reads a location's details: general (name, location name, time zone, closeoutHour that ends the business day, currency), location.
List orders
Lists a location's orders for one business day (business_date, like 20261031) or changed within a time range (at most a month), a page at a time.
Get an order
Reads one order by its GUID with its checks, item selections and modifiers, discounts, payments (type, amount, tip, card brand and last four digits), totals, dining option, table, server and dates.
Get menus
Reads the location's published menus (menus API v2): each menu with its availability, menuGroups and their menuItems (name, guid, price, description, modifier groups), plus lastUpdated.
List out-of-stock items
Lists menu items whose stock is limited: out of stock (the default) or with a remaining quantity.
List employees
Lists the location's employees, or the ones with the given GUIDs.
List scheduled shifts
Lists the scheduled shifts that start and end within a time range (at most a month).
List time entries
Lists clock-ins for one business day (business_date, like 20261031) or that started within a time range (at most a month).
List jobs
Lists the location's job roles (server, host, line cook …).
Write 0
Create, change or send.
This tool only reads, so nothing in it changes.
Read only
Every action here only reads, so an agent can look things up in Toast but cannot change anything there.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the sign-in details Toast gives you for its API.
What you enter
- Client ID
- Client secret
Settings
- API access URL
- Restaurant GUID
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Toast data
Ask a question in plain words. The agent can get restaurant details, list orders or get an order in Toast, then answers with what it found.
- 02
Share what it finds in Slack
Give one agent Toast and Slack: it can get restaurant details in Toast and post a summary to a Slack channel in the same run.
- 03
Run it as a workflow step
Add "Get restaurant details" to a workflow, and it runs in Toast the same way every time, with or without an agent.
FAQ
Toast and MyDeepAgents
Can MyDeepAgents connect to Toast?
Yes. The Toast connector has 9 actions, all of which only read. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Toast?
Enter the sign-in details Toast gives you for its API. You'll need: Client ID and Client secret. The connection also asks for: API access URL and Restaurant GUID. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Toast without asking?
No. Every Toast action only reads, so an agent can look things up there but cannot change anything.
Can I use Toast in workflows as well as agents?
Yes. Every Toast action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Toast to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.