Integrations
How connections work
Every platform in the catalog connects in one of three ways: OAuth, an API key, or a webhook. Which one applies is a property of the platform, not a choice you make — the catalog entry for each integration says which it uses.
Where connections live
Connections are managed from Integrations in your Brand Space — the page titled Connected Apps. It is organised into four tabs:
Integrations
The catalog itself. Search by name, filter by category and status, and connect, configure, or disconnect a platform from its card.
API Keys
Keys you have stored, for the platforms that authenticate with one.
Webhooks
Endpoint URLs, signing secrets, and the event selection for each webhook-based connection.
Activity Logs
A record of what each connection did — timestamp, integration, event, status, and response code — with search, filtering by integration, refresh, and export.
Connections are scoped to one Brand Space
A connection belongs to the Brand Space it was made in. Connecting Shopify for one brand does not connect it for another, and data from one brand's connection never appears in another brand's audience, campaigns, or reporting. If you run several brands, connect each platform separately inside each Brand Space — including when the same underlying account serves more than one brand.
This is also why it matters which account you authorize with. When a platform offers a chooser — an ad account, a property, a store, a workspace — pick the one that belongs to the brand whose Brand Space you are in.
The three connection types
The steps below are the same for every platform that uses that connection type. Anything specific to one platform is on that platform's own page.
OAuth
You approve the connection on the platform itself. En Garde never sees your password — the platform hands back a token scoped to the permissions shown before you approve.
- Open Integrations in your Brand Space. The page is titled Connected Apps.
- Find the platform on the Integrations tab, using the search box or the category filter.
- Click Connect. A dialog lists the permissions En Garde will request.
- Continue to the platform. A popup opens on their site where you sign in and approve. If nothing appears, your browser blocked the popup — allow popups for En Garde and try again.
- Leave the popup open until it closes on its own. En Garde then checks the connection status and the card moves to Connected.
API key
You generate a key in the platform and paste it into En Garde. The key is tested against the live API before it is stored, so a wrong or under-scoped key fails at setup rather than silently later.
- Generate an API key in the platform, with the permissions its documentation lists for third-party access.
- Open Integrations in your Brand Space and find the platform on the Integrations tab.
- Click Connect. Paste the key into the API key field — the eye toggle reveals what you pasted so you can check it.
- Click Test Connection. En Garde calls the platform with the key and reports whether it worked.
- Save. The Save button will not store an untested key, so a failing test has to be fixed first.
Webhook
The platform calls En Garde when something happens, rather than En Garde polling it. You supply an endpoint URL and a shared signing secret, and choose which events get sent.
- Open Integrations in your Brand Space and go to the Webhooks tab.
- Enter the endpoint URL the platform should call.
- Generate a signing secret, or paste the one the platform gave you, then copy it into the platform so both sides agree on it.
- Select which events should be delivered. Only the events you tick are sent.
- Save, then use the test action to fire a sample payload and confirm it arrives.
Disconnecting
Disconnect from the same place you connected: find the platform on the Integrations tab and choose Disconnect. A confirmation dialog appears before anything happens, and spells out what disconnecting does:
- The access token En Garde holds is revoked.
- Data synchronization stops.
- Data already synced is preserved — disconnecting does not delete history.
- You can reconnect at any time.
Reconnecting is the same flow as connecting the first time. For an API key connection, this is also how you rotate a key: disconnect, then connect again with the new one.
When a connection errors
Start at the Activity Logs tab. Filter by the integration in question and read the most recent entries — each row carries a timestamp, the event, a status, and the response code the platform returned. That response code usually identifies the problem on its own.
- Authorization failures — the token or key is no longer valid. Passwords changed, keys rotated, and revoked app access all land here. Disconnect and connect again.
- Permission errors — the connection works but the account lacks access to what was requested. Check the role of the account you authorized with, then reconnect with one that has the access.
- Rate limiting — the platform is throttling requests. These usually clear on their own; repeated entries over a long window are worth reporting.
- Nothing in the logs at all — for a webhook connection this points at the platform side. Confirm the endpoint URL and signing secret match on both ends, and that the events you expect are actually selected.
If a popup never appeared during an OAuth connection, that is a browser popup blocker rather than a platform error. Allow popups for En Garde and start the connection again.