Integrations overview

Everything the platform talks to on your behalf — messaging providers, delivery networks, point-of-sale systems, image hosting, maps — is configured in one place, in the same shape.

Where to find it

Dashboard → Settings → Integrations → Plugin Config (/configuration/integrations/integration/list) — Admin, Co-Admin

The three screens

Screen	Route	What it holds
Essential	/configuration/integrations/basic-integration	The credentials the platform cannot run without: maps, image hosting, and your primary payment keys
Plugin List	/configuration/integrations/integration/plugin-list	Which integration types are offered in the dropdown when adding one
Plugin Config	/configuration/integrations/integration/list	Your actual connections, one entry per provider

Payment gateways are configured separately, under Finance — see Gateway setup.

What is available

Category	Providers
SMS	Twilio, Telnyx, SMSLink
WhatsApp	Twilio
Voice	Twilio, Telnyx
Email	SendGrid, or your own SMTP server
Push	OneSignal (configured with your app credentials rather than here)
Delivery networks	DoorDash Drive, Uber Direct, Shipday, Nash
Point of sale	Toast, Square — and Clover, which connects through an app on the Clover devices rather than on this screen (see POS integrations)
Images	Cloudinary
Maps	Google Maps

Adding a connection

1. Get credentials from the provider. Every integration needs an account with that provider — the platform connects to your account, it does not resell one.

2. Create the integration and pick its type.

3. Enter the configuration. Fields differ per provider; anything marked private is stored as a secret and never shown back to you in full.

4. Set the conditions — leave it platform-wide, or scope it to particular business types, zones, outlets or franchises. This is how one outlet can use a different SMS sender or delivery network from another.

5. For messaging, set the per-purpose flags. See below — this is the step people miss.

6. Activate it, then test with something real and small.

Per-purpose flags on messaging integrations

A messaging integration is not simply “on”. Each one carries separate switches for what it is allowed to send:

Flag	Covers
Order Notification	Order receipts, status updates, one-time passcodes
User Login and Verify	Sign-in codes
Broadcast	Broadcast campaigns
Marketing Autopilot	Voucher campaigns — both Autopilot and Promotions
Global Notification	Platform-wide announcements

They are independent on purpose: many operators send transactional messages through one provider and marketing through another, because the pricing and the sender reputation are different problems.

This is the number one support question

“My campaigns never send” is almost always an integration that has Order Notification ticked and Marketing Autopilot or Broadcast not. Receipts keep arriving, so the integration looks healthy, and nothing marketing-related ever goes out. Check the flags before anything else.

Scoping

Every integration carries conditions. Left empty, it applies everywhere; filled in, it applies only where it matches. Two integrations of the same type with different scopes is a normal setup — a local SMS provider for one country and a global one for the rest.

Where several could apply, the most specific scope wins.

Testing and health

• POS connections (Toast and Square) have a Test Connection action, and a circuit that opens after repeated failures so a broken POS cannot slow down ordering. It can be reset from the dashboard once the cause is fixed. Clover has no connection here to test: its health shows on the outlet’s Clover page and on the Clover devices themselves.
• Delivery networks have their own connection test and the same circuit behaviour, plus a per-provider performance report at /reports/delivery-network-summary.
• Messaging failures show up as undelivered messages in the campaign reports rather than as an error on this screen — a wrong key looks like poor engagement until you look.

Credentials hygiene

• Rotate provider keys on your own schedule, and update them here immediately afterwards — the old key stops working the moment it is rolled.
• Use a provider account that belongs to the business, not to a person who might leave.
• Give each integration the narrowest permissions the provider allows.

Troubleshooting

Symptom	Try this
Receipts send but campaigns do not	The per-purpose flags — see above
Nothing sends on any channel	Confirm the integration is active and its conditions are not scoping it away from the outlet in question
A provider works in one outlet only	That is scoping working; widen the conditions
Toast or Square sync stopped	Test the connection; if the circuit is open, fix the cause and reset it
Clover sync stopped	Check that a Clover device at the outlet is on and online, and which one is primary — see POS integrations
An integration type is missing from the dropdown	It is not enabled in Plugin List
Deliveries are not being offered to a network	Check the network’s own priority and connection test

Related: Messaging providers · Delivery networks · POS integrations · Gateway setup