Every flow starts as a sentence.
Brief NgageFlow in plain words, then shape the steps it drafts. Each step names its system, and you choose which ones wait for a person.
A plain brief becomes the steps of a flow
Each step names its system: IBM Maximo, IFS, SAP, another ERP or an app.
- Logic
- Branches, loops and a code step for edge cases.
- Agents
- Read, check and draft with your tools.
- People
- An approval holds the run for a yes.
“When a purchase order line is priced more than 5% above contract, hold it and ask the buyer in Teams.”
- 1 A purchase order line changesIFS Trigger
- 2 Find the contract price for the partIFS Read
- 3 More than 5% above contract?Rule Branch
- 4 Write the buyer a two-line summaryModel Agent
- 5 The buyer releases or holds the lineTeams Approval
- 6 Update the line and log the decisionIFS Write
Five ways a flow can start
A change in IFS, an invoice in the inbox or a sensor alarm can each start a run.
ERP record
A purchase order line changes in IFS
Email
An invoice reaches the AP inbox
Schedule
Each morning, or on a cron rule
Webhook
A pump sensor raises an alarm
App event
A supplier submits a form
A history of every run, step by step
Draft, publish and roll back versions of a flow. Retry a failed run from the step that failed.
| Run | Flow | Result |
|---|---|---|
| 1042 | PO price check | Waiting for the buyer |
| 1041 | PO price check | Released |
| 1040 | Invoice flow | Posted for approval |
| 1039 | Overdue work orders | Sent to Teams |
| 1038 | Supplier check | Retried at step 3 |
Run 1042Waiting for the buyer
- 1 Line changedIFS PO-20447, line 2, 108.00
- 2 Contract price foundIFS 100.00
- 3 Above contract?Rule Yes, by 8%
- 4 Summary writtenModel 2 lines
- 5 Buyer approvalTeams Waiting
- 6 Update the lineIFS Not started
Controls every flow has
The six things a reviewer asks about first.
- Approvals
- The writes you choose wait for a yes.
- Budgets
- One for each flow.
- Kill switch
- Pauses one flow, one tenant or everything.
- Projects
- One per team, with its own connections.
- Roles
- Who builds, who publishes, who only views.
- Audit trail
- Who started it, what ran, what came back.
Questions about building a flow
Can we roll back a change to a flow?
Yes. Each flow keeps its versions: you draft, publish and roll back to an earlier one.
What happens when a step fails?
You retry the run from the step that failed. The run history shows each step and what came back.
Can a flow include code?
Yes. A TypeScript step covers the rare edge case. Read the build or buy guide
Can a flow use an ERP other than IBM Maximo, IFS or SAP?
Yes. IBM Maximo, IFS and SAP are ready today. For any other application, including a homegrown one, we teach Ngage how it works in weeks.
Where does NgageFlow run?
In your own cloud, or managed by EX10.
Describe one process you want automated
Write it in a sentence or two. We draft its steps with you, live, in a safe test setup.
Or write to hello@ngagesuite.com