[ Oracle Fusion / Procurement ]

Requests in chat, requisitions in Oracle

Employees ask for what they need in Slack, Teams or email. engini has an AI agent turn each request into a complete requisition in Oracle Fusion Cloud ERP, asking for whatever is missing, and a scheduled run tells the requester when it becomes a purchase order. Approvals stay in Oracle.

Oracle Fusion Cloud ERPSlackMicrosoft TeamsOutlook or Gmail
See the Oracle Fusion Cloud ERP integration →
A request in Slack
  1. Slack logo
    "We need 6 laptops for the new hires"asked in #purchasing
  2. Agent fills the detailsitem, quantity, cost center, need-by date
  3. Oracle Fusion Cloud ERP logo
    Requisition createdOracle Fusion, your approval rules apply
  4. Slack logo
    PO number postedscheduled status check
Illustration of the flow on this page, not a product screen.
What it does
Chat and email requests become complete Oracle Fusion requisitions
Systems
Oracle Fusion Cloud ERP, Slack or Teams, Outlook or Gmail
Built with
A workflow with an AI agent step, plus a scheduled status check
Your control
Oracle approvals apply; the agent cannot approve
[ 01 / The problem ]

People ask in chat. Procurement re-keys it.

Blurred landscape photo with the words Requisitions and the labels Ask, Complete, Create, Update

Most purchase requests start as a message: we need laptops, renew this license, order more labels. Someone in procurement turns each one into a requisition in Oracle Fusion, chasing the requester for the cost center and the need-by date, and later answers "where is my order?" by looking up the purchase order.

Where requests stall

  • Requests missing the item, quantity, cost center or date.
  • Re-keying chat messages into Oracle.
  • Requesters asking for status by email.
  • Requests that never reach Oracle at all.

What the agent does

An AI agent reads each request in Slack, Teams or email, asks the requester for anything missing, and creates the requisition in Oracle Fusion through the Oracle user you connect, so your Oracle approval rules apply as usual. engini has no documented Oracle Fusion triggers yet, so a scheduled workflow checks requisition and purchase order status and tells the requester when something changes.

[ 02 / How it works ]

From a message to a purchase order

01 / Ask

A request arrives

A message in a Slack or Teams channel, or an email, starts the workflow.

02 / Complete

The agent fills gaps

An AI agent step reads the request and asks for the item, quantity, cost center or date if any is missing.

03 / Create

Requisition in Oracle

It creates the requisition in Oracle Fusion; Oracle approval rules apply as usual.

04 / Update

Status to the requester

A scheduled run reads requisition and PO status and posts changes back to the requester.

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

[ 03 / What the agent reads and writes ]

What the agent reads and writes

SystemRecordsAccess
Oracle FusionRequisitionsCreateRead
Oracle FusionPurchase orders (status)Read
Slack or TeamsRequests, questions and status updatesReadWrite
Outlook or GmailRequests by emailRead

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 requisition: request, details, purchase order

Editorial image: from a message to a purchase order.

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 someone posts a purchase request in the #purchasing Slack channel, use an AI agent to extract the item, quantity, cost center and need-by date, ask in the thread for anything missing, and create a requisition in Oracle Fusion Cloud ERP. Reply in the thread with the requisition number.
  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 requests from Slack or Teams become Oracle Fusion requisitions?

Yes. An AI agent reads the request, asks for missing details, and creates the requisition through engini’s Oracle Fusion Cloud ERP connector, which covers requisitions and purchase orders.

Who approves the requisition?

Your approvers, in Oracle Fusion, by your Oracle approval rules. engini adds no approval step and the agent’s Oracle user should not be able to approve.

How does the requester learn the status?

A scheduled workflow reads requisition and purchase order status and posts changes back to the requester in Slack, Teams or email.

Is there a setup guide?

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