For developers & operators
Every integration,
documented honestly.
All 28 connectors: what they do, what they need, and which ones push to a real system today versus which run the full pipeline in simulate mode while we finish the transport.
Live and Simulated mean specific things
Live means this connector has a real transport: give it what it asks for and it talks to the real system. Square pushes your dishes into a real Square catalog; a website embed serves your menu on every page view; Google Sheets fetches your published CSV; a Zapier, Make, n8n or webhook target really receives an HTTP POST. Live describes the code, not your account. A live connector with no credentials saved yet has nothing to send to, so it simulates and says so in the sync log until you fill it in.
Simulated means the connector runs the whole pipeline for real: it validates your credentials' shape, builds the exact payload it would send, counts the items and writes the result to your sync log. It just doesn't make the outbound call, because that system's transport isn't finished. Nothing is faked and nothing is hidden: the panel says so, the sync log says so, and this page says so. When the transport lands, the connector flips to Live and your configuration keeps working.
Every integration
Point of sale (10)
Push the menu you already wrote into the till, so names and prices match at the pass and on the receipt.
Reservations & guests (6)
Keep your menu current inside the booking journey, so diners decide faster when they can see tonight's menu.
Websites (6)
One snippet, any platform. Always-live: the menu is pulled on every page view, so there is nothing to sync and nothing to go stale.
Data & automation (6)
Bring menus in from where they live today, and push events out to wherever you need them tomorrow.
Keep reading
- REST API reference: when no connector fits, build it yourself.
- Webhooks: drive anything you run from Carte's events.