PRODUCTS
SalesField SalesCRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopersSENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse casesSOLUTIONS
FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →THE MECHANISM
Two tiers, one contract.
What a connector can do is inferred from the connector itself — the catalog can't drift.
TIER 1 · COMPILED CONNECTORS
RESTFile transferMessage bus
built and tested as code — the engine blocks
TIER 2 · MANIFEST CONNECTOR
{ "partner": "insurer-api",
"auth": "oauth2 · vault",
"operations": ["GET /claims", "POST /approvals"] }
"auth": "oauth2 · vault",
"operations": ["GET /claims", "POST /approvals"] }
one reviewed JSON document — a new HTTPS partner, no code
BOTH FEED THE SAME PIPELINE ↓
STEP 1
Auth
Secrets held in a managed vault — never in flow config.
STEP 2
Transform
Visual pipelines map and reshape records, step by step.
STEP 3
Retry shield
Retries with circuit breakers — one bad partner can't flood the rest.
STEP 4
Run history
Per-record errors, payloads kept.
REPLAY FAILED (3)
HOW IT WORKS
Connect→Bind→Transform→Run→Replay
01 · IN DEPTH
Reliable pipes, not glue code.
CONNECTOR LIBRARY
Real drivers where it matters
Deep compiled connectors for REST, file transfer and message-bus transports — and a reviewed-manifest tier that adds a new HTTPS partner without writing code. What a connector can do is inferred from the connector itself, so the catalog can’t drift from reality.
RELIABILITY
Built for the third retry
Secrets in a managed vault, retries with circuit breakers, run history with per-record errors and replay.
SYNC PROFILES
Keep two systems agreeing
A separate scheduled sync engine with its own monitor — including attachment sync.
FOR THE EVALUATORS
For the people who own the pipes.
The details an RFP answer needs — all verifiable in a demo.
TRIGGERS
Webhook, schedule, record event, or manual — each flow starts the way the job demands.
TRANSFORM PIPELINES
Visual, step-by-step mapping and reshaping — auditable by the next admin, not just the author.
ERRORS & REPLAY
Failures are per-record, with payloads kept. Fix the cause, replay exactly the records that failed.
SECRETS IN A VAULT
Credentials live in a managed vault, never in flow config — rotate once, every flow follows.
MANIFEST PARTNERS
A reviewed JSON manifest adds a new HTTPS partner without code — capabilities inferred, catalog can't drift.
SYNC PROFILES
A separate scheduled sync engine with its own monitor — attachments included.
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.
INTEGRATIONS AT A GLANCE
The capabilities, stated plainly.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix Integrations |
|---|---|
| Connector library | Two tiers — compiled (REST, file transfer, message bus) + reviewed manifest |
| Triggers | Webhook, schedule, record event, manual |
| Transform pipelines | Visual, step-by-step, auditable |
| Credential storage | Managed secrets vault |
| Retries with circuit breakers | Native |
| Run history & per-record replay | Native |
| Sync profiles — keep two systems agreeing | Native |
| Conflict detection & governed merge | Native |
FEATURE HIGHLIGHTS
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.
COMMON QUESTIONS
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.