Introduction

Dime.Scheduler ships with first-class connectorsConnectorAn integration that links Dime.Scheduler to a back-office system, routing data in and scheduling decisions back out. for the systems most customers use - Business Central, NAV, Exchange. The webhook connector is the answer for everything else. It is the generic way to push every appointment change out of Dime.Scheduler, as JSON over HTTP, to any application that can stand up an endpoint and receive a POST.

That covers a lot of ground: a custom-built ERP, a CRM that no standard connector targets, an internal microservice that wants to react to planning events, a Power Automate flow, a Slack notifier, a Tetris game. Whatever sits on the other side of an HTTPS URL can become part of the planning loop.

What gets published

Every time someone changes an appointment on the planning boardPlanning boardThe main graphical scheduling surface where dispatchers drag tasks onto resources across a timeline. (create, update, delete), the connector fires a POST to the configured URL with the full appointmentAppointmentA task scheduled to a resource for a specific period - the scheduled instance you see on the planning board. payload as JSON. The receiver decides what to do with it - persist it, transform it, forward it, ignore it. Dime.Scheduler does not need to know.

Unlike the BC or NAV connectors, the webhook connector is intentionally generic: it does not try to interpret the payload, link it back to a record on the receiving side, or run a back-office workflow on success. The contract is simpler. Dime.Scheduler delivers the message; the receiver does the rest.

Where it fits in the publishing flow

Dime.Scheduler routes every transaction by the appointment's Source AppSource appAn identifier Dime.Scheduler attaches to data so it can route a change back to the correct back-office system. against the registered connectors. The webhook connector takes its turn in that same flow - register it with a source app, and every appointment whose source app matches will land at its URL.

The standard connectors (BC, NAV) then route further by Source TypeSource typeAn identifier that, together with the source app, tells Dime.Scheduler which back-office table a record belongs to. to run the right back-office workflow. The webhook connector stops at the HTTP POST and hands control to the receiving system.

Where it goes from here

What you build on the other side is up to you. A receiver that turns appointments into Outlook calendar items, a flow that posts them to Slack, a data lake that ingests every change for analytics, an experimental UI that visualises planning as something else entirely. Like, say, a game of Tetris: