[ Oracle Fusion / Suppliers ]

New suppliers into Oracle Fusion, checked first

engini reads the documents a new supplier sends, checks Oracle Fusion Cloud ERP for an existing supplier, and prepares a clean record on the board procurement already uses. When procurement marks it ready, engini creates the supplier in Oracle Fusion through the Oracle user you connect.

Oracle Fusion Cloud ERPOutlook or Gmailmonday.comSlack
See the Oracle Fusion Cloud ERP integration →
A new supplier, start to Oracle
  1. Documents arrivetax form, bank letter, address
  2. AI extracts the detailslegal name, tax ID, address
  3. Oracle Fusion Cloud ERP logo
    Duplicate checkOracle Fusion suppliers: none found
  4. monday.com logo
    Ready for reviewprocurement board item
  5. Oracle Fusion Cloud ERP logo
    Supplier createdafter the item is marked Ready
Illustration of the flow on this page, not a product screen.
What it does
Supplier documents read, duplicates checked, supplier created after review
Systems
Oracle Fusion Cloud ERP, Outlook or Gmail, monday.com or Sheets, Slack or Teams
Built with
Two workflows: intake with an AI agent step, and create on Ready
Your control
Procurement marks each record ready; Oracle roles apply
[ 01 / The problem ]

Every new supplier starts as a pile of documents

Blurred landscape photo with the words Supplier onboarding and the labels Intake, Check, Review, Create

Adding a supplier to Oracle Fusion means collecting a tax form, a bank letter and an address, checking that the supplier is not already there under another name, and keying it in. It is slow, and mistakes are expensive: a duplicate supplier splits spend, a wrong bank account misdirects a payment.

What slows onboarding

  • Reading documents in different formats.
  • Searching for an existing supplier with a similar name.
  • Chasing the requester for missing details.
  • Keying everything by hand.

Where the agent helps, and where people decide

engini AI Tools extracts the details, and an AI agent step searches Oracle Fusion suppliers by tax ID and name, then prepares the record on your procurement board with anything missing called out. A person reviews it and sets it to Ready; that change starts a second workflow that creates the supplier in Oracle Fusion. engini adds no approval step of its own; the review is the status change.

[ 02 / How it works ]

Read, check, review, create

01 / Intake

Documents arrive

An email to the vendor inbox starts the intake workflow; engini AI Tools extracts the details.

02 / Check

Look for duplicates

An AI agent step searches Oracle Fusion suppliers by tax ID and name and flags close matches.

03 / Review

Procurement decides

The prepared record lands on a monday.com board or a sheet; procurement reviews it and sets it to Ready.

04 / Create

Supplier in Oracle

The status change starts a second workflow that creates the supplier in Oracle Fusion and writes the result back.

This is the flow you will build. Start free and connect your systems.

[ 03 / What the agent reads and writes ]

What the agents read and write

SystemRecordsAccess
Oracle FusionSuppliers (duplicate search)Read
Oracle FusionNew supplier recordCreate
Outlook or GmailSupplier documentsRead
monday.com or Google SheetsThe review itemCreateUpdate

Connect these systems in engini and give the agent only these tools.

[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the Oracle logo, the engini mark and a frosted tile joined by a thin line, labeled suppliers: documents, duplicate check, ready

Editorial image: one supplier, one clean record.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: when an email with supplier documents arrives in vendors@ in Outlook, extract the legal name, tax ID and address with engini AI Tools, search Oracle Fusion Cloud ERP suppliers for the same tax ID, and create an item on my "New suppliers" monday.com board with the details and any possible duplicates. Do not create anything in Oracle.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect Oracle Fusion Cloud ERP, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can new suppliers be created in Oracle Fusion through engini?

Yes. engini’s Oracle Fusion Cloud ERP connector covers suppliers. The create step runs only after procurement marks the record ready.

How are duplicates caught?

The agent searches Oracle Fusion suppliers by tax ID and similar name before preparing the record, and shows any matches for procurement to decide.

Who checks bank details?

Procurement, on the review board. The create workflow runs only when someone sets the item to Ready.

Is there a setup guide?

The help-center guide is being written. The engini Tool Catalog lists each Oracle Fusion tool and its permissions.