Workflow Builder

Draw your process.
Watch it run.

Build a process out of connected nodes on a drag-and-drop canvas. Not brittle if-this-then-that, but the real shape of work: branches, approvals, waits, and handoffs between teams.

Start free View pricing

The canvas

Left to right, exceptions branch off

Drag nodes on, connect them, configure each one in a side panel, and validate before it runs. Every workspace has its own workflow, so Work Orders and Accounts Payable never share a process they don't agree on.

The happy path runs straight across: exceptions peel off the top or bottom, so a flow reads like a diagram, not a maze

Per-node config in the inspector: fields, conditions, recipients, email bodies with {{field}} tokens

Validation before it runs, so a half-wired flow tells you at save time

Work Orders · workflow

Await reply

missing info

Email in

Branch

Approval

Send email

Resolve

Escalate

rejected

The node types

TriggerActionBranchSwitchWaitApprovalAwait replyChecklistLoopResolveCross-workflow node

Gates

Work that waits, on purpose

Most automation tools treat waiting as failure. Real processes wait constantly: on a manager, on a customer's reply, on someone walking the site. RouteWrk makes waiting a first-class state: a ticket parks at a gate, and the gate says what it is waiting for.

A parked ticket always names its gate, so nothing is ever silently stuck

Every gate has a matching action on the ticket: approve, check items off, review the drafted email, pick the photos

It un-parks itself when the condition clears: a reply lands, a timer expires, the missing step is reconnected

Trouble parks too, it doesn't vanish: an email that can't send, a mailbox not connected yet, a workflow looping on one recipient: the ticket waits and says so, instead of failing quietly

WO-1042 · parked

Waiting for approval

Parked at Manager sign-off since 9:14 AM. Nothing moves until someone decides.

ApproveReject

What a ticket can be waiting on

A timerA human approvalA checklistAn email replyPhoto selectionDraft email review

The details that decide whether it survives contact with reality

Anyone can draw boxes and arrows. These are the parts that matter on day 200.

Branches that test more than one thing

A branch node can check several conditions at once with a Match: All / Any toggle (amount over 5,000 AND priority urgent), each with its own field, operator and value.

Triggers that know the channel

A ticket enters at the trigger matching how it was created: routed email at the Email trigger, cross-workflow tickets at Automation, everything else at Manual.

Editing a live workflow is safe

Delete a step and the tickets parked on it say "Workflow Step No Longer Exists" with a Move to Step… action. Leave a step unconnected and it runs once, then waits, and resumes by itself the moment you draw the edge.

Handoffs between departments

A cross-workflow node in one workspace opens a ticket in another. A closed work order starts the invoice in Accounts Payable, fields carried across, and it can never fire twice.

One executor per step

Open the app in ten tabs on three machines and a step still runs exactly once. No duplicate emails.

Retries with a cap

A loop node sends a ticket back around a bounded number of times, then takes the exhausted edge, so a vendor who never answers lands in front of a person instead of in an endless reminder cycle.

What an action node can do

Send emailReply emailUpdate fieldsStatus changeBid invitation

More of the platform

Smart Inbox

Auto-route email to the right flow

Ticket Detail

One job, start to finish

Kanban Board

Tickets by stage, one board

Analytics

Spot bottlenecks, track trends

See it run on your own process.

Build your first workflow free. No credit card, no setup call.