BC Event Bridge

BC Event Bridge publishes Business Central table changes as real-time JSON events, so external systems can react to what happens in Business Central without polling its API on a schedule. It works with any table you choose — it isn't tied to Time Track Central's own tables, and it doesn't require the rest of Time Track Central to be installed.

How it works

Event Bridge hooks into Business Central's global table triggers. Once you register a table, every insert, modify, rename, or delete against it fires an event — no matter what caused the change: a user typing into a page, an API call, a job queue task, a data migration, anything. You control, per table:

• Which event types are sent (insert / modify / rename / delete — each toggled independently).
• Which fields are included in the payload. Nothing is sent by default; you explicitly add each field, which keeps payloads small and means you never leak a field you didn't mean to expose.
• Whether previous values are included on modify/rename, so the receiving system can diff old vs. new.
• Filters on insert/modify, so an event only fires when the field values you care about actually match — not on every single change to the table.

See Event Tables for the step-by-step.

Example uses

• Sync CRM or project names and numbers into a local, on-premise folder structure the moment they change in Business Central — no polling scripts required.
• Run RabbitMQ at the edge as a gateway for legacy systems that shouldn't connect to Business Central directly.
• Feed a data warehouse or reporting tool in real time, without polling Business Central for changes.
• Send a Slack or Teams alert the moment a purchase order is deleted or another critical record is modified.
• Trigger a Zapier, Make.com, or Power Automate flow straight from a Business Central change — see Zapier, Make.com & Power Automate.

Where events go

One endpoint is configured company-wide on Setup:

• RabbitMQ — events are published to a RabbitMQ exchange via its HTTP Management API.
• API endpoint — events are POSTed as plain JSON to a URL you specify, with context in the request headers.
• Azure Service Bus — events are published to a Service Bus queue or topic.
• Azure Event Hub — events are published to an Event Hub.
• Azure Queue Storage — events are published to a Storage Account queue.
• Azure Event Grid — events are published to an Event Grid custom topic.

Each endpoint accepts a different set of authorization methods — see Authentication.

Getting started

1. Search Business Central for Set up BC Event Bridge (it's registered as a manual/assisted setup guide) or Event Bridge Setup directly, and configure your endpoint — see Setup.
2. On the same page, run Schedule Automatic Retries once. Delivery itself runs in the background regardless, but this recurring job is what recovers stuck or lost deliveries and prunes completed ones — without it scheduled, none of that self-healing happens. See Event Queue → How delivery works.
3. Register the tables and fields you want to publish — see Event Tables.
4. Verify what actually gets sent before relying on it — see Testing & Troubleshooting.

Licensing and access

Event Bridge is a separate AppSource listing from the main Time Track Central product, licensed per Administration User only — the people who actually configure the Setup Card and Event Tables. Standard users, automated processes, and the number of monitored tables are all unlimited and free, regardless of how much data flows through them.

Access is controlled through standard Business Central permission sets, not through Time Sheet Users like the rest of Time Track Central:

• Configuring Setup and Event Tables needs the Event Bridge Admin permission set assigned (directly, via a User Group, or already included if the user has broad D365 SETUP-level access) — this is the license-consuming role.
• Every other user gets basic Event Bridge User access automatically (bundled into standard D365 READ-level access) — this is what lets their everyday actions trigger events for tables you've registered, without needing a license of their own.