🧰
Incident / near-miss
signal.incident with a site and topic → a toolbox talk for that site. Perfect for your incident or near-miss system.
Connector
Your systems know when someone needs inducting. Let them say so.
When a new starter is added, a site incident is logged, a policy changes or a refresher falls due, your other systems already know. Send that one fact to InductOnline and it becomes the right induction — offered to the right worker or site, with the proof captured as always.
How it works
Send a fact. Get the induction.
Your system posts a data point
New starter, site incident, policy update, refresher due — one signed HTTPS request. No login, no LMS integration project.
InductOnline works out the training
It matches your course library to the topic — a site induction, a toolbox talk, a policy acknowledgement — or flags that one should be created.
It surfaces where you work
The need shows on your Readiness board next to who's inducted and who's overdue; incidents feed your hazard/toolbox flow.
The endpoint
One webhook, signed with a shared secret.
Ask us for your workspace name and signing secret. Sign the request body with HMAC-SHA256 and send it as the x-inductonline-signature header. That's the whole integration — the same secure webhook the rest of the ecosystem uses, no separate API keys or user accounts.
# A site incident becomes a toolbox talk for that site
BODY='{"event":"signal.incident","data":{"site":"Site A","topic":"Manual Handling","severity":4}}'
SIG=$(printf '%s' "$BODY" | openssl dgst -sha256 -hmac "$SECRET" | sed 's/^.* //')
curl -sS https://www.inductonline.com/engine/v1/integration/<workspace>/webhook \
-H "Content-Type: application/json" \
-H "x-inductonline-signature: $SIG" \
-d "$BODY"
The endpoint is POST-only — opening it in a browser returns 404, which is expected. A correct request returns { "ok": true, "signalId": "…" }; a bad or missing signature returns 401.
What to send
The frontline signals InductOnline understands.
📝
Policy updated
signal.policy_updated → a policy acknowledgement sent to the affected workers or site.
🔄
Refresher due
signal.refresher_due → the right WHS refresher, offered before it lapses.
👷
New starter
signal.onboarding_gap from your HR/roster system → the site or employee induction they still need.
🪪
Credential lapsing
signal.credential_expiring with a worker and topic → shows on your Readiness board as a live gap, with the matching refresher.
📍
Visitor arriving
signal.visitor_arriving → a short visitor induction, ready to complete by QR on arrival.
New InductOnline workspaces come pre-mapped for these event types — send them and they just work. You can tune the mapping any time in your workspace settings.
Good to know
Built to be safe to call, often.
- Signed with HMAC-SHA256 — no API keys, no user accounts
- Idempotent — retries and re-syncs never create duplicates
- The source record stays in your system — InductOnline reacts, it doesn't own it
- Worker resolved by ID, email or roster key; no match → a whole-site need
- Explicit fields always override the workspace defaults
- Responds immediately; nothing blocks your system
Need more than induction?
If you need SCORM courses, custom forms, credential tracking, role/site/client readiness and deeper compliance workflows, Edifyd gives you the full worker readiness platform.
Wire it up in an afternoon.
Tell us your systems and we’ll give you a sandbox workspace and secret to test against.