Business process management (BPM), built into the same platform
Forms, approvals, and task routing run as native steps on the same platform that runs your integrations, not a separate BPM product wired on afterward.
The problem
Most BPM and iBPMS tools live apart from the systems they are meant to coordinate: a forms product bolted onto an integration platform, a case-management suite that needs certified specialists to extend, or a BPMN modeler that produces a diagram which then hands off to yet another tool the moment the process has to touch a real system.
Every hand-off is a place work stalls, a translation layer that can drift out of sync, and one more audit trail that does not talk to the others.
How business process management works on Neblex
Business process management in Neblex Integration Fabric runs forms and human approvals as native steps on the same platform that runs your data sync and system integrations, with apps as the front end whose every action runs a flow.
A process that starts with a structured intake form can call an API, wait on a manager's approval with an SLA timer, write the result to your ERP, and post a summary in Slack, all as steps in one flow with one event-sourced history.
Every task lands in a task inbox with full assignment history, and every approval decision sits on the same tamper-evident audit trail as every other action Integration Fabric takes on your behalf.
The deterministic parts of a process, the API calls, the transforms, the retries, the rollback, are workflow capability. Business process management is the human layer on the same platform: the forms, the approvals, the task queues, and the SLAs.
How you build it in Neblex
Flows are built three ways, and you can move between them on the same flow:
- Natural language. Describe the flow to Matt, the Neblex AI Assistant built into the builder. Matt drafts the canvas, maps fields, and explains steps. It runs on the platform's builder model by default, or on a model you connect for the building experience only. That setting never supplies a model or credential to deployed agents, their tools, knowledge search, apps, or flows.
- Native builder. Assemble steps, branches, and connectors on the visual canvas.
- MCP. Create, change, publish, and run flows programmatically, so an external client or agent can build on Neblex directly, with consent scopes for operating, authoring, and publishing.
Agents, forms, apps, data tables, and connections have their own builders and the same MCP surface.
Business process management capabilities
- Form builder for structured intake, with validation and conditional fields, plus an app builder whose every action runs a flow
- Approvals with SLA timers, reminders, and automatic escalation when a step stalls
- Task inbox with assignment, reassignment, delegation, and full history per task
- Route a task to a pool of people, or only to those holding the required skills, with round-robin or least-loaded auto-assignment, and let anyone eligible claim it
- Sequential or parallel approval routing based on amount, department, or any rule you define
- Emailed task links that open the form directly, for approvers who rarely open Neblex
- Run detail with a step inspector: every task, decision, and piece of data for one process instance in one place
- Process versioning: in-flight instances finish on the version they started, new ones use the latest
- Every approval decision on the same audit trail as system-to-system steps in the same flow
Worked example
A real process teams build on day one, with the actual step-level detail.
New vendor from intake form to approved ERP record
Procurement submits a new vendor request. The process collects documents, routes for finance and legal sign-off, creates the vendor in the ERP, and notifies the requester, with each step on one history.
- Intake: a form captures vendor name, tax ID, banking details, and a W-9 upload, with field validation.
- Branch: if annual spend is under 25,000 USD, route to finance only. At or above that, route to finance and legal in parallel.
- Approve: each approver gets a task-inbox item and an emailed link that opens the task, with a 2-business-day SLA and a reminder at day one.
- Escalate: an approval still open after the SLA runs the escalation flow, which reassigns it to the approver's manager.
- Create: on all approvals, an action creates the vendor record in NetSuite and stores the returned
internal_id. - Notify: the requester gets the vendor number in Slack, and the documents are filed to the vendor's folder.
Frequently asked questions
Do we need a separate BPM product alongside Integration Fabric?
No. Forms, approvals, and task routing are native step types on the same platform that runs your integrations, so a process that needs both human judgment and system automation does not have to cross a product boundary to get both.
How is business process management different from Workflows on Neblex?
Business process management is the human-task layer: approval tasks, a task inbox, SLA timers, escalation, and routing to pools or by skill. Workflows are the deterministic parts around it: the branching, the API calls, the writes, and the rollback, with no person in the path. Forms and apps are shared between the two, whether a form starts a flow or collects input inside a task. Both run on the same platform, and most real processes use both, so a BPM process is a workflow with human steps in it.
Can approvers act without logging into Neblex?
Yes. A task can email a sealed link that opens its form to the people on its notify list, so an approver who rarely opens Neblex can respond from the message. A no-login link carries no identity to compare, so a step with separation of duties enabled routes its deciders through the internal queue instead.
What happens if an approval stalls?
Each task has an SLA that sets its due time, the queue shows what is overdue, and an escalation flow you choose runs when the SLA passes, for example reassigning the task to a manager or a fallback pool, so a single unavailable approver does not stall the whole process.
Can a process combine human approval with system automation in one flow?
Yes, that is the point. A single flow can call an API, wait on a human approval step, and write results back to another system, all with one shared history and audit trail.
Bring one real integration
We will build it with you against your own systems, with the run log open.