Post: 5 Make.com Scenarios Every HRIS-L&D Integration Runs
Five Make.com scenarios form the orchestration layer for a production-grade HRIS-L&D integration. Each scenario maps to one stage of the 5-stage architecture, runs on its own cadence, and owns its own error handling.
Why split into five scenarios
Combining all integration logic into a single mega-scenario produces an integration that is impossible to debug and impossible to selectively retry. Split by stage. The HRIS + L&D API Integration — Complete 2026 Guide details the underlying architecture.
- Identity sync scenario. Triggers on the HRIS employee webhook. Reads the changed employee record, normalizes the payload, upserts the learner on the L&D side. Runs continuously. Retry: 3 attempts at 60-second intervals.
- Role + tenure push scenario. Triggers on the HRIS role change webhook. Pushes job title, department, manager, hire date to the L&D learner profile. Runs continuously.
- Completion write-back scenario. Triggers on the L&D completion webhook. Validates the completion against the employee record, deduplicates, writes the learning history record to HRIS. Runs continuously. Hourly fallback job catches any webhook misses.
- Daily reconciliation scenario. Scheduled at 02:00 local time. Pulls full employee list from HRIS, full learner list from L&D, compares, reports drift to an HRIS admin queue. Runs once per day.
- Termination handler scenario. Triggers on the HRIS termination event. Revokes L&D access, finalizes the learning record, writes the termination event to both sides. Real-time priority — no delay.
Sent_from and sent_to discipline
Every HTTP POST in every scenario carries a sent_from field (the scenario URL) and a sent_to field (the endpoint receiving the data). When a failure surfaces three months later, the audit log immediately shows which scenario wrote what to where. Without this discipline, troubleshooting requires guesswork. The real-time webhooks guide covers the webhook patterns underlying scenarios 1, 2, 3, and 5.
Expert Take — five scenarios is the floor, not the ceiling
Production HRIS-L&D integrations rarely stop at five scenarios. Mature deployments add scenarios for skill signal push, enrollment rule evaluation, credential expiry alerts, and audit report generation — often reaching 10 to 14 distinct scenarios. The five above are the floor; anything less is incomplete.
FAQ
What happens when a scenario fails mid-execution?
Each scenario uses the 4Spot standard error handler — builtin:Break with 3 retry attempts at 60-second intervals, then notification to an operations channel via the scenario’s executionUrl. The scenario does not silently fail.
How are the scenarios versioned?
Each scenario is exported to JSON and stored in a Dropbox backup folder weekly. The version history supports rollback when a change introduces a regression.
Can scenarios run on multiple Make.com organizations?
Yes. Production scenarios run in one Make.com organization; staging scenarios run in a parallel organization with read-only credentials to the HRIS staging environment. The two organizations do not share connections. The full Make.com HR stack integration guide expands the multi-org pattern.
RELATED POST
