All courses

Connected systems

Register the systems you operate with —your store, SAP, the warehouse, the ERP— with the key they call with and the endpoint Bruxel notifies, and check whether their channel is healthy.

What is a connected system and what is it for?

It's the record of a system in your company that talks to Bruxel: your online store, SAP, the warehouse (WMS), the ERP or a middleware. It lives in Channels → Connected systems and says two things: which Bruxel API key that system calls with, and which webhook endpoint Bruxel notifies.

With that, Bruxel knows who each notification and each call belongs to. Flows use it to mark the steps in that system's lane as done (guide “Flows and journeys”), and source reconciliation uses it to know which system reported each value (guide “Source reconciliation”).

No password or credential of your system is stored here, and registering it doesn't connect anything on its own: Bruxel never goes into your system. The system is the one that calls, with its Bruxel key, and Bruxel only notifies the endpoint you registered in Webhooks.

Who can see and register connected systems?

Seeing the list takes Operator or higher; a Viewer or an Editor sees a notice that their role isn't enough. Registering, changing the key and endpoint, running a check, pausing, reactivating and deleting take Administrator or Owner. A supplier doesn't see this screen.

If the screen says “This feature isn't available on your account yet”, your organization has it turned off.

How do I register a system?

In “Register a system”, fill in these fields and click “Register”:

  • Name: how your team recognizes it, for example “SAP middleware”.
  • Type: SAP, Warehouse (WMS), ERP, Other online store, Middleware or Other system. Adobe Commerce only appears if your organization has that connection (guide “Connect your Adobe Commerce store”).
  • Code (optional): the system's name in flows. Lowercase, starting with a letter, with digits and underscores allowed, up to 40 characters. Leave it empty and it comes from the name (“SAP middleware” → sap_middleware).
  • API key it calls with and Endpoint we notify (below).
  • Store address (optional): only store types ask for it.
Each organization can have up to 10 systems. The code and the type can't be changed after you register it: a flow names the system by its code.

How do I link a system's API key and endpoint?

The key is created in Channels → API keys and the endpoint in Channels → Webhooks: create them there first. Only valid keys are offered, neither revoked nor expired, and only the endpoint's domain is shown. A key and an endpoint belong to a single system: the ones another system already has don't appear.

A system that isn't a store can have only the key (if it only calls Bruxel) or only the endpoint (if it only receives notifications). To change them later, click “Change key and endpoint”, choose and click “Save”. What already arrived stays with the system it had at that moment: changing a link only moves what arrives afterwards.

An unlinked key counts by its name: what arrives with a key called “SAP” belongs to sap, unless sap already has its own linked key.

If a flow reads a system's notifications, you can't remove its endpoint or swap it for one that doesn't receive that notification: change that step or archive the flow first.

What does each system's status mean?

Each system shows which key it calls with and whom we notify, when it last called and who called, how many notifications are left to deliver, how many consecutive failures it has and the last error. Top right, its status:

StatusWhat it means
Up to dateThe channel is healthy. For a store it means the store came for the content, not that it wrote it: if something doesn't show up there, check it in your store's admin panel.
DeliveringEverything is healthy, but there are queued notifications not yet delivered. A few seconds is normal; if it lasts, check the system.
FailingThe endpoint is still on, but it's piling up consecutive failures. At 20 it turns itself off.
No channelIts endpoint turned itself off after too many failures or, for a store, it has no endpoint: no notification reaches it.
PausedSomeone on your team paused it on this screen.
Not linkedIt has no key and no endpoint: flows can't recognize what's theirs.

What do I do if a system isn't receiving notifications or shows failures?

“Run a check” checks, in order, that there's a valid key, that it has already called with it, that there's an endpoint, that it's on and that at least one notification has arrived. For a store it checks all five; for another system, only what it has linked. It tells you the first one that fails and what to do. It only reads: it doesn't send anything anywhere.

If the endpoint turned itself off, fix the system and click “Reactivate channel”: it turns it back on and its failure count starts from zero. If you already have the maximum number of active endpoints, turn off or delete another one in Webhooks first. Each delivery attempt is listed in Webhooks (guide “Webhooks”).

What happens if I pause or delete a system?

“Pause” marks it “Paused” on this screen and “Resume” brings it back. It doesn't turn off its webhook or revoke its key: that's done in Webhooks and in API keys.

“Delete” and then “Yes, delete” remove only the system's record: its webhook and its key stay as they are. A system whose notifications a flow reads can't be deleted: change that step or archive the flow first.