Contents14 sections ↓
NetSuite workflows and SuiteFlow: why they matter more than most people think
Updated October 27, 2026 with the SuiteWorld 2026 announcements.
If you've spent any time inside NetSuite, you've probably noticed that manual processes don't scale. Someone forgets to approve a purchase order. An expense report sits in limbo for two weeks. A sales order ships before finance signs off on the credit terms.
SuiteFlow is NetSuite's answer to this problem. It's the visual workflow engine built directly into the platform, and it lets you automate business logic without writing a single line of code. Drag-and-drop states, point-and-click conditions, and a visual canvas that even non-developers can understand. When used well, approvals and notifications stop depending on someone remembering.
Some workflows are simple two-state approval chains. Others are multi-department routing with a lot of conditional logic. The tool is flexible enough to handle both — you just need to know what you're doing.
Core concepts: the building blocks of every workflow
Before you build anything, you need to understand the five components that make up every SuiteFlow workflow.
States
States represent where a record currently sits in a process. Think of them as stages: Pending Approval, Approved, Rejected, Under Review. Every workflow has at least one state, and exactly one entry (start) state. Within a workflow, a record is in one state at a time.
Transitions
Transitions are the paths between states. They define how a record moves from Pending Approval to Approved, or from Approved back to Under Review. Each transition can have conditions attached — so the record only moves when specific criteria are met.
Actions
Actions are the tasks attached to a state. They run on the trigger you choose: when the record enters or leaves the state, when it loads or is saved, or when a user edits a field. Send an email, set a field value, create a related record, lock the record from editing — these are all actions. They're the "do something" part of the workflow.
Conditions
Conditions are the gatekeepers. They evaluate whether a transition should fire or an action should execute. You can build conditions based on field values, roles, formulas, or combinations of all three. For example: "Only allow the transition to Approved if the user's role is CFO and the PO amount exceeds $10,000."
Triggers
Triggers determine when the workflow runs. A workflow starts either on a record event (the record is created, updated or viewed) or on a schedule. For event-based workflows, the server trigger sets the moment: Before Record Load, Before Record Submit or After Record Submit. Inside the workflow, actions and transitions can also run on Entry and Exit of a state, and on client triggers such as Before Field Edit. The trigger you choose affects when the workflow engine evaluates your states and transitions.
Common workflow use cases
These are the patterns that come up most. If you're wondering whether a workflow is the right approach for your problem, chances are good that one of these patterns applies.
Purchase order approval routing
The classic starting point. Route POs through one or more approvers based on amount thresholds, department, or vendor. Low-value POs get auto-approved. High-value ones require VP or C-suite sign-off.
Sales order approval
Hold sales orders until credit checks pass, margin thresholds are met, or a sales manager reviews non-standard terms. Without this, orders hit the warehouse before finance has signed off on the credit terms -- and unwinding a shipped order is painful for everyone.
Expense report approval
Manager approval first, then finance if the amount exceeds a threshold. The workflow can also flag policy violations automatically -- meals over $75, missing receipts -- and bounce them back to the employee without a human reviewer needing to catch it.
Vendor bill approval
This closes the loop on procure-to-pay. After goods arrive, route vendor bills through the appropriate cost center manager, then to AP for final processing.
Record status management
Not everything is an approval. Workflows handle record lifecycles too: moving projects through stages, updating opportunity statuses based on activity, closing out stale quotes after 90 days. Any process that follows a predictable sequence of states is a candidate.
Building your first workflow: PO approval step by step
Here's a practical example: a purchase order approval workflow with three states, role-based routing, and email notifications.
Step 1: Create the workflow
Navigate to Customization > Workflow > Workflows > New. Select Purchase Order as the record type. Give it a clear name like "PO Approval Routing" and set the trigger to Before Record Submit (this ensures the workflow evaluates before the record is saved, so you can block unapproved POs from processing).
Step 2: Define your states
Create three states on the canvas:
- Pending Approval — the initial state. Every new PO lands here.
- Approved — the PO has been signed off and can proceed to fulfillment.
- Rejected — the PO was declined and needs revision.
Set Pending Approval as the entry state. Every new PO starts here.
Step 3: Add transitions
Draw two transitions from Pending Approval:
- Pending Approval -> Approved: This fires when an authorized approver clicks the Approve button.
- Pending Approval -> Rejected: This fires when the approver clicks Reject.
Add a transition from Rejected back to Pending Approval, so employees can revise and resubmit.
The buttons come first: add Approve and Reject with the Add Button action on the Pending Approval state, then select each button on its transition.
Step 4: Configure conditions
On the Approved transition, add a condition: the current user's role must be Purchasing Manager (or another role you allow to approve). You can also add an amount condition — for POs over $50,000, require a second approver by routing to an intermediate "VP Review" state instead.
Step 5: Add actions
On the Pending Approval state entry, add a Send Email action that notifies the designated approver. On the Approved state entry, add a Set Field Value action to update the PO status field and a Send Email action to notify the requestor. On the Rejected state entry, send an email to the requestor with the rejection reason.
Step 6: Test in sandbox
Deploy the workflow to your sandbox account first. New workflows start with the release status Testing, which means they run only for the workflow owner; switch to Released when it should run for every user with access to the record type. Create test POs at various amounts, log in as different roles, and verify every transition and action fires correctly. Only then move it to production.
Workflow actions: what you can actually do
SuiteFlow provides a solid library of built-in actions. Here are the ones you'll use most often.
Send Email — The backbone of approval workflows. Notify approvers, requestors, or any recipient, pulling field values from the record into the email template (PO amount, vendor name, due date).
Set Field Value — Update status fields, stamp approval dates, flag records. Accepts static values or formulas for dynamic computation.
Create Record — Generates a new record when a state is entered, and it doesn't have to be the same record type as the workflow. Create a follow-up task when an expense report is rejected, for example. To turn one transaction into another, there is a separate Transform Record action.
Lock Record — Locks the whole record for the workflow instance once it reaches a certain state. Critical for approved POs and finalized invoices. To lock only some fields, use Set Field Display Type and set them to Disabled.
Add Button — Puts a button such as Approve or Reject on the form. A transition can then run when that button is clicked.
Custom — Runs a workflow action script (SuiteScript) when built-in actions fall short. This connects no-code workflow logic to full programmatic control. More on this later.
Moving a record between states is the job of transitions, not actions. Auto-approval is a transition from Pending Approval to Approved with a condition, such as the PO total being under $500, and no button.
Transition conditions: controlling the flow
Conditions determine whether a transition fires. SuiteFlow gives you several ways to build them.
Role-based conditions — Only allow certain roles to trigger a transition. "Only the CFO can approve POs over $100,000." Approval workflows lean on these heavily.
Field value conditions — Evaluate a field on the record. "If department is Engineering, route to the Engineering VP." You can compare against static values, other fields, or the current user.
Amount-based conditions — Set thresholds that change the approval path. Under $5,000 goes to a manager. $5,000-$50,000 goes to a director. Over $50,000 goes to the VP of Finance.
Formula conditions — Write a formula when the condition builder can't express the logic. Fields go in braces by their ID, and you can use SQL functions: for example {total} > 10000, or LENGTH({memo}) > 10 to require a longer memo. SQL functions run on the server, so pair them with server triggers.
Combined conditions — Stack multiple conditions with AND/OR logic. "The approver must have the Purchasing Manager role AND the PO must be under $25,000 AND the vendor must not be on the restricted list." SuiteFlow handles all of this visually.
Scheduled workflows: automation on a timer
Not all workflows are triggered by record events. Scheduled workflows run at defined intervals — from every 30 minutes to daily, weekly, monthly or yearly — and start one workflow instance for each record a saved search returns. They're easy to overlook.
Recurring cleanup tasks — Close stale opportunities that haven't been updated in 90 days. Deactivate vendors with no activity in the last year.
Periodic status updates — Every Monday morning, flag each open PO older than 30 days and email its buyer. This keeps things from falling through the cracks without anyone having to remember to check.
Escalation workflows — If an approval has been pending for more than 48 hours, escalate it. Send a reminder email, CC the approver's manager, or reassign the approval to someone else. These keep your processes moving even when people are busy or on vacation.
To create a scheduled workflow, set Initiation to Scheduled, pick a saved search and define the frequency. The saved search decides which records get processed: it must use the workflow's record type and have at least one criteria filter, because you can't set an initiation condition on the workflow itself. Keep it narrow — you don't want it running against your entire transaction history every time. Scheduled workflows only run once the release status is Released.
Workflows vs SuiteScript: when to use each
Both tools automate business processes, but they excel in different areas. Picking the wrong one costs you time on the build and time on maintenance.
Use workflows when:
- The business logic is likely to change frequently (approval thresholds, routing rules, notification recipients)
- Non-developers need to understand or modify the logic
- The process is primarily about routing, approvals, and notifications
- You want an auditable, visual representation of the process
- The automation involves a single record type with straightforward state transitions
Use SuiteScript when:
- You need to interact with external systems (API calls, webhooks)
- The logic involves complex calculations, loops, or data transformations
- You need to process multiple record types in a single operation
- Performance is critical and you need fine-grained control over execution
- The automation requires features workflows don't support (file operations, advanced search manipulation, custom UI)
Use both together when:
- You want the visual state management of workflows with the power of SuiteScript for specific actions
- The approval routing is best handled visually, but one step requires a complex calculation
- You need workflows for the business team to manage, with SuiteScript custom actions for the technical bits
In practice, we usually combine them. Workflows handle the high-level process orchestration, and SuiteScript handles the heavy lifting at specific steps.
Performance considerations
Workflows aren't free. They execute during record save events, and poorly designed workflows can noticeably slow down your system. Here's what to watch for.
Execution order matters. When several workflows run on the same record type and Workflow B depends on a field that Workflow A sets, the result depends on which one runs first. Don't build on that. Oracle's own SuiteFlow best practice is to combine workflows that share the same logic into one; within a single workflow, actions and transitions run in the order they're listed, and you can reorder them.
Nested workflows create complexity. A workflow that triggers another workflow that triggers a third workflow is a recipe for performance problems and debugging nightmares. Keep your workflow hierarchy as flat as possible. If we find ourselves nesting more than two levels deep, we reconsider the architecture.
Record save times are directly affected. Every Before Record Submit workflow adds time to the save operation. Users will notice. If you have five workflows all firing on every sales order save, those milliseconds add up. Audit your workflows periodically and disable or consolidate any that overlap.
Watch your governance. Workflow actions consume governance units, like SuiteScript. NetSuite's troubleshooting guide says the actions in a state must stay within 1,000 usage units, or the workflow stops with "Workflow Execution Usage Limit Exceeded". A state with many actions, or a heavy custom action script, can hit it. Check the workflow execution log, linked from the Workflow History subtab on the record when logging is on.
Common mistakes (and how to avoid them)
These are the ones to watch for.
Infinite loops. An infinite loop happens when one operation triggers another and the second triggers the first again. A classic example is a Set Field Value action on an After Field Edit trigger that sets the same field the user just edited, so it fires again and again. NetSuite also stops a workflow that transitions back into the same state more than 50 consecutive times, with a "Workflow Execution Usage Limit Exceeded" error. Always check whether your workflow actions could re-trigger the same or another workflow. Use conditions to break the cycle.
Missing conditions on transitions. A transition with no condition doesn't check who is acting or what the record says. Tied to an Approve button, it lets the person who submitted the PO approve it. Add role-based or field-based conditions to every transition, and to the Add Button action that shows the button.
Testing only in production. Building and testing workflows directly in the production account is risky: one misconfigured transition can auto-approve every PO that passes through it. Always build in sandbox, test thoroughly, then deploy to production. NetSuite's SuiteCloud Development Framework (SDF) can help manage this deployment process.
Overcomplicating a single workflow. If your workflow canvas looks like a subway map, it's probably doing too much. Break complex processes into smaller, focused workflows. A PO creation workflow, a PO approval workflow, and a PO receipt workflow are easier to manage than one monolithic workflow that handles all three.
Forgetting about edge cases. What happens when an approver leaves the company? What happens when a PO is edited after approval? What happens when the amount changes during the approval process? Build transitions and conditions for these scenarios from the start, not after they cause problems in production.
Advanced patterns
Once you're comfortable with basic workflows, these patterns let you build more sophisticated automations.
Child workflows
The Initiate Workflow action starts another workflow (the child) from the current one (the parent). The parent can wait for the child to finish by selecting it in the Wait for Workflow field of a transition. The child must use the same base record type as the parent and runs on the same record, so this is a way to split one record's process into smaller workflows. It doesn't share approval logic across POs, expense reports and vendor bills: each record type needs its own workflow.
Custom action scripts
When built-in actions aren't enough, write a Workflow Action Script in SuiteScript. This script runs as a workflow action but has full access to the SuiteScript API. Common uses include calling external APIs for validation, performing complex calculations, or creating multiple related records in a single step.
/**
* @NApiVersion 2.1
* @NScriptType WorkflowActionScript
*/
define(['N/record', 'N/email'], (record, email) => {
const onAction = (context) => {
const poRecord = context.newRecord;
const amount = poRecord.getValue({ fieldId: 'total' });
const vendor = poRecord.getText({ fieldId: 'entity' });
// Custom logic: create a task for high-value POs
if (amount > 100000) {
const task = record.create({ type: record.Type.TASK });
task.setValue({ fieldId: 'title', value: `Review high-value PO: ${vendor}` });
task.setValue({ fieldId: 'assigned', value: poRecord.getValue({ fieldId: 'custbody_finance_reviewer' }) });
task.save();
}
return 'success';
};
return { onAction };
});Workflow-initiated SuiteScript
One pattern that works well: the workflow manages the state machine and user interactions (approve/reject buttons, email notifications, field locking), while a SuiteScript User Event script watches for state changes and handles the complex backend logic. The workflow sets a custom field like custbody_wf_state, and the User Event script triggers different logic based on that field's value. This gives you the best of both worlds — visual process management for the business team and full programmatic control for the development team.
The SuiteFlow Agent (announced at SuiteWorld 2026)
At SuiteWorld 2026 (October 26), Oracle announced the SuiteFlow Agent: you describe a workflow in plain language in Ask Oracle, review the configuration it proposes, confirm, and it creates the workflow. According to Oracle's press release, it is planned for a future NetSuite release, with no release date, so nothing here is something you can use today.
The keynote demo showed the shape of it. The user described a sales-order approval policy:
- Orders over $100,000 need the Sales Director's approval.
- Customers more than 30 days overdue, or with an overdue balance over $10,000, need the CFO's approval.
- If both apply, the Sales Director approves first, then the CFO.
- Otherwise the order is approved automatically.
Ask Oracle restated the conditions and named the approvers, showed a summary before creating anything, and then created the workflow in a Suspended state so it could be reviewed and tested before release. The point Oracle's presenter made was that approval policies often live in a PDF and get enforced when someone remembers.
What to do now, before it ships:
- Write down your approval rules. Thresholds, who approves, in what order, and what happens when none apply. That is the input an agent needs, and it is the same input a person building the workflow in SuiteFlow needs.
- Review the workflow in its suspended state before you release it. A suspended workflow doesn't run. Check every transition condition, the approver on each state and the auto-approve path, then set it to Testing (it runs only for its owner) and try it in sandbox with records at each threshold. A workflow generated from a sentence is still a workflow that can approve the wrong order.
- Keep the states and transitions model in your head. You will be reviewing what the agent built on the same canvas described in this guide.
Wrapping up
SuiteFlow workflows are one of the most practical tools in NetSuite. They solve real operational problems — missed approvals, forgotten notifications, inconsistent processes — without requiring development expertise for every change. The key is starting simple, understanding the core concepts, and building complexity only when you need it.
If you're just getting started, build that first PO approval workflow. Get it into sandbox, test it, iterate on it. Once you see a purchase order route itself to the right person, send the notification email, and lock itself after approval — all without anyone touching a line of code — you'll understand why workflows are worth the investment.
Need help designing a workflow architecture that scales with your business? Reach out to our team — we've been building these for years and we're happy to help.
Sources
- NetSuite Help Center: Creating a Workflow, Release Status for Workflow Instances, Workflow Triggers, Workflow Actions Overview, Initiate Workflow Action, Scheduling a Workflow, Viewing Workflow Activity, General Workflow Issues, FAQ: SuiteFlow, SuiteFlow Best Practices
- SuiteFlow Agent: Oracle NetSuite press release of October 26, 2026, NetSuite Advances Vision for an Autonomous Suite, and the SuiteWorld 2026 opening keynote demo
What clients ask before signing
Lucia · BrokenRubik
Replies by email within 24 hours
Lucia
Not working the way this guide describes? Tell us what you see in your account and we'll reply with what we'd check first.

BrokenRubik
NetSuite Development Agency
Independent NetSuite consultancy specializing in NetSuite ERP, SuiteCommerce development, and enterprise integrations. 100+ companies served since 2017, from mid-market to enterprise OneWorld deployments.
