The mechanism
Two tiers, one contract.
What a connector can do is inferred from the connector itself — the catalog can't drift.
Connectors
Two tiers · one contract
REST, file transfer and message bus built as code — or a new HTTPS partner from one reviewed JSON document.
Auth
Managed vault · oauth2
Secrets held in a managed vault — never in flow config.
Transform
Map & reshape
Visual pipelines map and reshape records, step by step.
Retry shield
Circuit breakers
Retries with circuit breakers — one bad partner can't flood the rest.
Run history
Replay failed · 3
Per-record errors, payloads kept — so failed records replay from the history.
Both tiers feed the same pipeline — compiled or manifest, every connector gets the same auth, transform, retry shield and run history, and what it can do is inferred from the connector itself.
Integrations architecture.
Connect
Pick a compiled connector or add a partner from one manifest
Bind
Credentials bind from the managed vault, never flow config
Transform
Visual pipelines map & reshape records, step by step
Run
Retries & circuit breakers keep one bad partner contained
Replay
Failed records replay from run history, payloads kept
Reliable pipes, not glue code.
For the people who own the pipes.
The details an RFP answer needs — all verifiable in a demo.
Conflict-aware sync
When both systems change, nothing gets silently overwritten.
xMatix detects record conflicts between the platform and the external system, applies declared merge rules where the answer is safe, and queues the rest for a person. Conflicts are resolved at field level in a dedicated workspace, and only the failed item replays — the successful work stays put.
Conflicts — Accounts sync
2 auto-merged · 1 queued for review
The capabilities, stated plainly.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix Integrations |
|---|---|
| Connector libraryTwo tiers — compiled (REST, file transfer, message bus) + reviewed manifest | Native |
| TriggersWebhook, schedule, record event, manual | Native |
| Transform pipelinesVisual, step-by-step, auditable | Native |
| Credential storageManaged secrets vault | Native |
| Capability | xMatix Integrations |
|---|---|
| Retries with circuit breakers | Native |
| Run history & per-record replay | Native |
| Sync profiles — keep two systems agreeing | Native |
| Conflict detection & governed merge | Native |
Everything in Integrations.
Integration apps
Connections managed like products.
Each integration is an app with its own flows, credentials, monitor and history — not a loose script.
Connector library (two tiers)
Engineered where it matters.
Compiled connectors for the heavy protocols; manifest connectors for the long tail of HTTPS partners.
Manifest connectors
A new partner without a project.
A reviewed JSON manifest describes auth and operations; the platform infers the rest.
Webhook / schedule / event / manual triggers
Flows start the way the job demands.
Real-time pushes, timed pulls, record events, or a button an admin presses.
Transform pipelines
Mapping you can read.
Visual transform steps show how every field travels — the next admin can audit it.
Run history & replay
Failures are recoverable, not fatal.
Per-record errors keep the payload. Fix the cause and replay just what failed.
Vault-managed secrets
Credentials, out of config.
Secrets live in a managed vault; rotate them once, every flow follows.
Retries & circuit breakers
One bad night can’t cascade.
Automatic retries with backoff, and circuit breakers that isolate a failing partner.
Sync profiles & monitor
Bulk sync, watched.
The scheduled sync engine has its own monitor — volumes, durations and failures at a glance.
Attachment sync
Files travel too.
Documents and images sync alongside records — invoices arrive with their PDFs.
Conflict-aware sync
Concurrent changes, resolved by rule.
Concurrent changes detected and resolved by governed merge rules, with a review queue for what rules can’t decide.
Asked in every integration evaluation.
What happens when the same record changes in both systems?
xMatix detects the conflict instead of overwriting either side. Declared merge rules resolve the cases where the answer is safe — latest approval wins, one system is the source of truth for a field — and everything the rules can’t decide queues in a dedicated conflicts workspace, where a person resolves it field by field. Once resolved, only the failed item replays; records that already synced correctly are never re-run.