Integrations
Connect the systems you already run.
Nexus runs system-to-system and multi-system processes as one governed workflow. 1,480+ pre-built actions across 43 product families, standard interfaces and Rules + Code cover each step, with approval and a complete record of what happened.
Integration patterns
Find the pattern for your systems
Each pattern defines which system owns what, which way changes move, where people approve and what evidence remains.
CRM & ERP
Salesforce + SAP
Commercial commitments reach ERP fulfilment and finance without re-keying.
Direction: Validated order context from a closed opportunity or approved CPQ quote.
- Salesforce · 73 actions
- SAP · 97 actions
HR & Identity
Workday + Okta
Employee lifecycle changes become governed identity and access changes.
Direction: Employee context for a joiner, mover or leaver, read through Workday Employee actions.
- Workday · 66 actions
- Okta · 42 actions
ITSM & Engineering
ServiceNow + Jira
Incidents and changes reach engineering with context, and status returns to service.
Direction: Incident or change context, affected CMDB items and priority.
- ServiceNow · 55 actions
- Jira · 36 actions
CRM & ERP
HubSpot + Salesforce
Marketing leads reach sales clean, deduplicated and correctly routed.
Direction: Contact, company and form context for a lead ready for sales.
- HubSpot · 69 actions
- Salesforce · 73 actions
Commerce & Finance
Shopify + NetSuite
Storefront orders and inventory stay aligned with ERP invoicing and items.
Direction: Order and customer context for invoicing and follow-up.
- Shopify · 39 actions
- NetSuite · 38 actions
Commerce & Finance
Stripe + Xero
Billing events become reconciled accounting entries with exceptions reviewed.
Direction: Payment, invoice and subscription context for the accounting entry.
- Stripe · 43 actions
- Xero · 41 actions
Cloud & IT Operations
AWS + ServiceNow
Cloud events become enriched incidents and approved changes.
Direction: Enriched event context, affected resources and CMDB matches.
- Amazon Web Services · 61 actions
- ServiceNow · 55 actions
Identity & Collaboration
Microsoft 365 + Okta
Identity changes and collaboration follow-up happen together, under policy.
Direction: Outcome of a user, group or role change for notification and scheduling.
- Microsoft 365 · 45 actions
- Okta · 42 actions
Cloud & IT Operations
SAP + ServiceNow
ERP exceptions reach service operations, and approved changes reach SAP.
Direction: Finance, procurement or HR exception context for resolution.
- SAP · 97 actions
- ServiceNow · 55 actions
Design questions
Four decisions define a trustworthy integration.
The connector choice comes after the operating model is clear.
Direction
Which system owns each object, and which writes are one-way or reciprocal?
Authority
Which changes can execute by policy, and which require named approval?
Exceptions
Where do validation failures, conflicts and unavailable systems wait for resolution?
Evidence
Which input, mapping, decision, action and outcome must remain reviewable?
Build your own combination
Your stack is not a pair.
Select the systems you run in the integration explorer to see pre-built actions, trigger sources and the workflow patterns that fit. When a step falls outside the pre-built actions, it runs through an API, protocol or database interface, or as code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript.
Multi-system workflows
Processes that cross three or more systems
Worked workflows that combine trigger sources, connector actions, standard interfaces, approval and audit.
AWS S3 or Azure Blob Storage, SAP, MSSQL or Oracle
Invoice intake and reconciliation with object storage, SAP and SQL
A file lands in object storage, SAP and a reconciliation database are checked, Rules + Code matches the result and exceptions go to a named reviewer.
ServiceNow, Okta, Microsoft 365 / Calendar
Governed employee access changes with ServiceNow, Okta and Microsoft 365
A ServiceNow request carries the context, an approver authorises the change, the identity step runs and the outcome returns to the ticket.
Salesforce, SAP
Salesforce to SAP order handoff without replacing either system
A Salesforce record detected by SOQL polling is validated, handed to SAP through the connector or an RFC call, and reconciled back.
Salesforce, ServiceNow, Jira
Customer issue escalation across Salesforce, ServiceNow and Jira
One governed run carries an escalation from the customer record to service operations and engineering, and keeps the handoff state visible.
AWS CloudWatch, SNS, SQS, ArgoCD, Kubernetes
Event-driven cloud operations with AWS, ArgoCD and Kubernetes events
CloudWatch, SNS, SQS, ArgoCD and Kubernetes events start a governed runbook, with approval before any change that policy marks as consequential.
HubSpot, Salesforce
Lead handoff from HubSpot to Salesforce with governed enrichment
A lead moves from marketing to sales with deduplication, enrichment and routing rules applied in one recorded run.
Stripe, PayPal Subscriptions, Salesforce, SAP
Payment and subscription events into CRM and ERP
A Stripe event or PayPal subscription change is validated and reflected in Salesforce and SAP under one execution record.
AWS CloudWatch, ServiceNow or Jira
Security incident enrichment and ticketing from cloud telemetry
An AWS CloudWatch event is enriched with Rules + Code and becomes a ServiceNow or Jira work item with the evidence attached.
Integration review
Discuss the systems you need to connect.
Bring the process. We will map ownership, direction, approval and the steps each system needs.