This page defines which destination systems notifications are relayed to, and for which events. Each subscription links a source app (for example the iopole integration) to a destination system (another ERP, a Navision environment, a Power Automate flow, an internal tool).

What is a subscription for?

The Webhook Setup page enables sending; the Webhook Subscriptions page says whom to send to and for which events. Without an active subscription covering an event, the notification has no destination and is not relayed.

How it is organized

A subscription has two parts:

• The header — the destination: its address, authentication mode, and enabled state.

• The subscribed events — a subgrid listing the event types this destination should receive (for example EDOCUMENT_RECEIVED).

The events subgrid is shown directly under the subscription list and updates automatically when you select a different subscription.

Before you start

• An administrator role in Business Central.

• The HTTPS URL of the destination system, provided by the team that manages it.

• If applicable, an authentication secret agreed with that system (not needed when Auth Type is None).

Create a subscription

1. Click New.

2. Fill in the header:

   • Source App: the source app, for example iopole.

   • Subscription Code: a unique code for this destination, e.g. NAVISION or POWERAUTOMATE.

   • Description: a readable label, e.g. "Customer Navision environment".

   • Target URL: the destination's HTTPS address (a non-HTTPS address is rejected).

   • Auth Type: the authentication mode (None, HMAC signature, Bearer token, Basic).

3. In the Subscribed Events subgrid, add one line per event you want.

4. Tick Enabled to activate the subscription.

Choosing events

In the Subscribed Events subgrid, each line = one event type relayed to this destination. The Event Type field offers a lookup of the events declared by the source app (for iopole: EDOCUMENT_RECEIVED, EDOCUMENT_STATUS_CHANGED, INVOICE_INBOUND_INVALID). Each line's Enabled flag lets you mute one event without deleting the line.

A single destination can therefore subscribe to several events: add as many lines as needed.

Several destinations for the same event

The same event can be relayed to several destinations. Create one subscription per destination (each with its own Subscription Code and address), and add the same event type in each one's subgrid. For example, a received invoice can be notified to both Navision and a Power Automate flow: each destination is delivered and tracked independently (one may succeed while the other is retried).

Authentication to the destination

The Auth Type field says how the platform authenticates to the destination:

• None: no secret. Use it when the address authenticates itself — this is the case for a Power Automate flow, whose trigger URL already contains a SAS token. Nothing to enter.

• HMAC / Bearer / Basic: a secret is required. Open the subscription, click Set Subscriber Secret, enter the secret and confirm. It is stored securely and cannot be read back; Subscriber Secret Configured switches to "on".

The Set Subscriber Secret action is disabled when Auth Type is None, since no secret is expected.

Note: authentication between Business Central and the DyXit platform is separate and handled automatically by the app registration performed at install. The secret above only concerns the link between the platform and your destination system.

Good to know

• A disabled subscription receives no notifications, without being deleted.

• The destination address must use HTTPS.

• Delivery tracking is available on the Webhook Outbox page.