Integration observability is missing from Workato. We add it.
We answer “is it alive?” at a glance — then the harder question that actually matters: “did record X sync to Xledger, and exactly when?” On top of the answers, Nexus heals problems and keeps connectors current before they break.
Built for Workato today — Boomi, Power Automate & DevOps functions next
Serviceability
Liveness plus record-level sync proof — “did Customer-ID XYZ reach Xledger?” Customised per customer and per integration, right in the tool.
Nexus auto-heal
Precise fixes for specific errors — and cost auto-optimize that does the SEK math and stops you paying to sync data that didn’t change.
Data privacy
Row-level pseudonymization and encryption for sensitive HR and finance fields, decrypted only in runtime — plus a scan that cleans forgotten PII.
Living Connectors
Proactively warns when a connector’s auth or API is about to change — with the fix and the steps already prepared.
Is it alive?
The baseline glance — every integration’s health, last run and throughput in one board. Table stakes, and where everything starts.
Did record X actually sync — and when?
Anyone can prove a single record reached Xledger — search by Customer-ID, get an unmistakable answer with the exact timestamp and trace. Then ask why, in plain language.
Employee #4471 (Anna Berg) synced to Visma HRPlus at 23:31. Provisioning to System X stopped — the IAM update API returned “Connection timeout” at 23:47. The HR record is current; IAM provisioning is retrying now.
Warned before it breaks.
Living Connectors flags an auth or API change months ahead — here, Visma HRPlus moving to OAuth 2.0 — with the affected recipes and the fix already prepared.
- 1Register OAuth 2.0 app in Visma
- 2Add redirect URI · nexus.se/oauth/cb
- 3Swap connection auth on 2 connections
- 4Re-test 6 recipes in DEV
- 5Schedule deploy before 2026-09-01
A precise, ready-to-apply fix.
Nexus spots that an existing retry handler missed “Connection timeout,” and writes the exact to-do to close the gap — alongside cost-saving suggestions.
Add “Connection timeout” to the retry watch on IAM-009
The internal IAM update API intermittently returned Connection timeout. A retry handler already exists on IAM-009 — but it only watches 500 Internal Server Error, so these failures slipped through.
- 1Open recipe IAM-009 · error-retry step
- 2Add “Connection timeout” to watched errors
- 3Keep existing “500 Internal Server Error”
- 4Set max retries 3 · backoff 30s
- 5Re-test in DEV with replayed payloads
NS-012 polls every 5 min — source changes ~hourly
Switch the trigger to a 30-minute schedule. Same freshness, ~104k fewer tasks / year.
Fixed, propagated, and gated on human review.
Nexus applies the change in DEV, finds 3 more recipes on the same API and fixes them too, deploys to TEST — then stops at a strict human review gate before PROD.
on_error:
- watch: ["500 Internal Server Error"]
+ watch: ["500 Internal Server Error",
+ "Connection timeout"]
+ max_retries: 3
+ backoff: 30sStop paying to sync data that didn’t change.
Per-task billing punishes waste. Nexus spots that 94% of a nightly Quinyx sync re-writes unchanged people, does the SEK math at your own task price, and prepares the change — saving real money at the same data freshness.
You’re paying to re-write 526 unchanged people, every night.
The first task does a GET from the Quinyx API, which already mirrors Visma HRPlus. We compared it against the last sync: 94% of records were identical — yet every person still ran all 12 tasks. Add a change-detection gate after the GET and skip the unchanged ones.
Sensitive fields, pseudonymized — and old PII cleaned out.
Row-level encryption and surrogate replacement keep HR and finance fields safe at rest, decrypting only in runtime for the destination. A continuous scan finds and purges forgotten PII still sitting in Workato.
One observability & self-healing layer — for every engine you run.
We start where the pain is sharpest: Workato. The same layer extends to every other place integrations live.