Get restaurant
Read selected configuration for one active restaurant, including its business-day cutoff.
Connector library
Toast connector.
Read Toast restaurant configuration, menu-publication metadata and revenue-center references through four named scoped actions with managed credentials and bounded token pages.
Connector download
Download Toast
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
v0.2.0.0 Choose version
- Release
- 2026-10-04
- Package
- Implemented source
- Schema credentials
- Bearer token
- Connection settings
- Restaurant GUID, Toast API Hostname
- Package size
- 11 KB
- SHA-256
921332c5988a5feeafe8198b4cf1d1859547b3ca6aac97bafce02163018ed807
Version history
What's new
- v0.2.0.0Latest · 2026-10-04 · Implemented source
Read Toast restaurant configuration, menu-publication metadata and revenue-center references through four named scoped actions with managed credentials and bounded token pages.
- v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Historical readable HTTP scaffold.
Included in this version
Included actions
Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.
Get menu metadata
Read the published menu timestamp for one exact restaurant; no menu content is fetched.
List revenue centers
Read one bounded configuration page and its documented next-page header.
Get revenue center
Read one exact revenue-center reference within the requested restaurant scope.
Vendor API
API and access
Implementation considerations
- Restaurant configuration: Inspect selected restaurant settings and the local business-day cutoff.
- Menu publication timestamp: Read lightweight menus V2 metadata for the exact restaurant without fetching menu content.
- Revenue-center references: Read one checked header-token page or inspect an exact revenue center.
- Invoke configuration reads from flows; no webhook trigger is included.
- Use the trusted API hostname supplied by Toast, an issued managed OAuth token and a connected restaurant GUID. Every request uses the restaurant scope header.
- Configuration pagination uses Toast-Next-Page-Token, without deprecated fixed-size page/pageSize queries. Each list action returns one checked page.
- Configuration and publication timestamps do not establish current availability. Orders, payments, full menu retrieval, token renewal and writes are outside this package.
Related connectors
More in Restaurant & Hospitality
Support
Need help with Toast?
Tell us what you need to connect or change.