The IFS workflow automation platform
NgageFlow is an IFS workflow automation platform with a visual builder at its core: start flows from webhooks, schedules, app events or IFS record changes, shape the logic with branches and loops, and publish versioned flows your whole team can see running. Part of the Ngage Suite by EX10.
Start flows from anywhere work starts
A flow begins where the work begins — an inbox, a schedule, another app, or a record changing inside IFS Cloud.
Webhooks
Any system that can send an HTTP request can start a flow. Each flow gets its own endpoint the moment you create it.
Schedules
Run flows every five minutes, nightly, or on a cron expression — for digests, reconciliations and batch syncs.
App events
A new email in a shared inbox, a form submission, a Slack message, a file in a drive — events from 700+ connectors.
IFS record triggers
The native IFS Cloud connector fires when records are created or updated — purchase orders, work orders, suppliers, any entity.
The IFS record trigger comes from the native IFS Cloud connector — no polling scripts, no middleware.
Shape the flow without writing code
Branches, loops and — when an edge case demands it — a code step. The visual model stays readable even when the process is not simple.
Branches
Route work down different paths based on the data — amount thresholds, record states, who the supplier is. Conditions are configured visually, not coded.
Loops
Iterate over invoice lines, order rows or query results, and run the same steps for each item without duplicating the flow.
Code steps
For the edge cases, drop in a TypeScript step with full access to the flow data. Use code where it earns its place — nowhere else.
AI agents are steps too. Drop an agent into any flow to read documents, make judgment calls and act through your connectors — with approvals where you want them.
Explore AI agentsVersioned publishing, observable runs
A flow that touches the ERP should behave like software, not like a macro. NgageFlow treats it that way.
- Draft, then publish. Edit safely while the published version keeps running; go live only when you choose to.
- Every version kept. Reopen any earlier version and roll back when a change misbehaves.
- Step-by-step run history. Each run shows the input and output of every step — so debugging means reading, not guessing.
- Retry with context. Failed runs can be retried from the failing step once the cause is fixed.
Projects keep teams and customers apart
One NgageFlow instance can serve many teams — finance, supply chain, maintenance — or many customers, each in a sealed project.
Isolated projects
Flows, connections and run history live inside a project. The finance team never sees maintenance credentials — and vice versa.
Role-based access
RBAC decides who builds, who publishes and who only views. Builders iterate; only the right people put flows in front of the ERP.
Governance built in
Credentials are stored encrypted, scoped per project, and the platform runs in your cloud or EX10-managed. See security & hosting.
The platform, in plain answers
Is NgageFlow a no-code platform?
Yes. Flows are built in a visual builder with triggers, branches and loops, and most automations need no code at all. When an edge case calls for it, you can add a TypeScript code step inside the same flow — so the platform never becomes the limit.
How do flows get triggered?
Four ways: webhooks that any system can call, schedules including cron expressions, app events from 700+ connectors such as a new email or form submission, and a native IFS Cloud trigger that fires when records are created or updated.
How do multiple teams share one NgageFlow instance?
Through projects. Each team or customer gets an isolated project with its own flows, connections and run history, and role-based access control decides who can build, publish or only view. Nothing leaks between projects.
Weighing platforms? The guides in Learn cover build vs buy for ERP automation and more.
What the platform plugs into
AI agents
Agents that read, decide and act inside your flows — with human approval before writes.
AI agents for IFSIntegrations
700+ connectors, led by a native IFS Cloud connector for records, actions and events.
IFS Cloud integrationsTemplates
400+ ready-made flows to copy into a project and adapt — minutes to first automation.
IFS automation templatesSee the builder on your IFS scenario
Bring one process that hurts — we will model it live in NgageFlow against a realistic IFS Cloud setup.