The job of this console
See which connector last ran, open errors, and retrigger or fix source data. Do not treat this as a generic iPaaS designer — that lives under Integrations.
HRMS · Leave
Leave Integrations
Register view of leave connectors, run history, and error queues — no self-serve write UI; seed and triage via API.
Register view — seed via API. Flowcharts: inspect connectors → runs → errors.
Leave connectors
Runs and errors, seeded and triaged with care
Leave integrations is the register of connectors, run history, and error queues. There is no self-serve write UI for inventing connectors; seed and triage via API and this view.
Admin → Leave integrations
Route
/admin/leave/integrations
HR Admin · Org Admin · integration owner
Seat at the table
Administrators and integration owners. Employees never open connector errors.
The working rhythm
Scan run history, open the error queue, fix the employee or calendar at source, rerun. Escalate to Integrations hub if the adapter itself is down.
Moments that bring you here
A failed absence feed. After a legal calendar import. When balances diverged from an HRIS. Overnight connector failure.
ⓘ
Triage, not a second leave store
Successful runs update leave/attendance sources. Errors are queues, not a place to type balances.
Flowcharts
Each diagram auto-plays steps when it scrolls into view. Use Play / Pause, or click a step to jump.
1 — Integration run
Connector executes, writes results, surfaces errors.
flowchart TD
C[Connector register] --> R[Runs register]
R --> S[Sync evidence]
S --> Ok{Success?}
Ok -->|Yes| Done[Healthy]
Ok -->|No| Err[Error / DLQ]
Err --> Fix[Triage via API]
- 1Connector registerInspect seeded connectors — create/update via API (no self-serve write UI).
- 2Runs registerExecution history for scheduled or API-triggered runs.
- 3Sync evidenceBalances, requests, or status payloads recorded on the run.
- 4Success?All rows accepted by remote or local.
- 5Error / DLQFailed rows with reason codes.
- 6Triage via APICorrect mapping/data and replay through API or ops tooling.
2 — Ops monitoring
Where admins look when sync stalls.
flowchart TD
Ops[Integrations hub] --> Runs[Integration runs]
Ops --> Err[Integration errors]
Runs --> Health[Last success time]
Err --> Triage[Triage queue]
- 1Integrations hubAdmin → Leave → Integrations.
- 2Integration runsHistory of executions and durations.
- 3Integration errorsFailed payloads needing action.
- 4Last success timeSLA signal for payroll cutoffs.
- 5Triage queueReview DLQ rows; replay/fix via API.
Overview
These screens are register views for leave connectors, run history, and error queues. No self-serve write UI — seed and triage via API. Keep credentials in approved secret stores and never paste raw PII into audit notes.
How to use
1. Open Integrations
Admin → Leave → Integrations (connectors register).
2. Review connectors
Inspect registered connectors; create/update via API.
3. Inspect runs
Use Integration runs for execution history.
4. Triage errors
Review Integration errors / DLQ; replay or fix via API.