ERP & Finance · 9 pre-built actions
Oracle Cloud Integration B2B integration with Nexus
Bring Oracle B2B exchanges into governed operations. B2B, monitoring and trading actions let partner exchanges be checked, followed up and recorded as part of a wider process.
Pre-built actions
What you can automate
9 pre-built Oracle Cloud Integration B2B actions, grouped by what they work on.
9
PRE-BUILT ACTIONS
- 01B2B actions work with business-to-business documents and messages.
- 02Monitoring actions check exchange status.
- 03Trading actions work with trading partner information.
Workflow
How it fits into a Nexus workflow
Oracle Cloud Integration B2B steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Oracle Cloud Integration B2B API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Failed exchange follow-up
Monitoring finds a failed exchange and opens a ServiceNow incident with the details.
Partner onboarding checks
Trading partner data is validated before an exchange is enabled, with approval.
Exchange status reporting
Exchange status is summarised on a schedule for operations.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
FAQ
Oracle Cloud Integration B2B connector questions
- Which Oracle Cloud Integration B2B actions are pre-built?
- Nexus includes 9 pre-built Oracle Cloud Integration B2B actions across B2B (4), Monitoring (2) and Trading (3).
- Can Oracle Cloud Integration B2B start a workflow?
- Runs that use Oracle Cloud Integration B2B start from a webhook, a schedule or another trigger source. Oracle Cloud Integration B2B steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Oracle Cloud Integration B2B API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- ServiceNow connector
Incidents, changes and CMDB.
- SAP connector
Finance, procurement and sales orders.
- When there is no connector
API, protocol and code steps in one run.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Oracle Cloud Integration B2B fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.