Feature reference
What every part of FlowForge does — described plainly.
Below: each feature, what it actually does, where it pays off, and which plans carry it. The examples are live — the demo workspace behind them exercises the same code paths.
Drag-and-drop canvas builder
The builder is a real canvas, not a form with extra steps. Pull nodes from the palette, drop them where they belong, drag them around the grid, and connect ports — every link is drawn as a clean curve so the logic reads like a diagram. Pan, zoom to fit, and keep the whole workflow on one screen.
Where it pays off
A marketing lead capture: form trigger → score gate → SMS for hot leads, CRM update and nurture task for the rest — built in under five minutes.
Why it matters: Anyone on the team can read a workflow at a glance, and restructuring logic is a drag instead of a rewrite.
In the demo builder you can drag nodes, pan, zoom, wire ports, and save — the exact gestures this diagram abstracts.
Triggers that start the work
Every workflow begins when something happens: an external webhook posts in, a visitor submits a form, the schedule ticks to 09:00 on Monday, or a new record appears in a connected app with your chosen filter. Triggers are deliberately distinct on the canvas so the entry point of any automation is instantly obvious.
Where it pays off
The storefront's checkout webhook starts the cart-rescue sequence the moment an abandoned cart event lands.
Why it matters: Automations react to the real world instead of waiting for someone to remember to check.
See it running
This one is best understood live — the interactive demo drives it end to end with simulated triggers.
Conditions and branching
Condition nodes compare a field against your bar — a lead score over 65, a cart at fifty dollars, whether the clock sits inside business hours. Each condition gives you two exits, so a single workflow can serve different records differently: the hot path goes right to sales, the rest continues onward.
Where it pays off
Leads scoring above the gate alert the rep by SMS; everyone else gets staged in the CRM and queued for nurture the next morning.
Why it matters: One workflow handles both sides of a decision, and the reasoning of every run is recorded per branch.
True — matches the gate
Send SMS to the rep
Firing now — rep paged.
False — below the gate
Stage in CRM + queue nurture
Waiting (branch idle)
This is the exact behavior of the Compare-field node on the canvas: two exits, one verdict, every run.
Delays and scheduling
Not everything should happen instantly. Delay nodes park a run for a set number of hours or until a calendar moment — with weekend and holiday rules if you want them. Resumed runs re-enter the canvas exactly where they left off.
Where it pays off
Hold the run for an hour so the customer session cools down before sending the rescue email — no recovery message mid-checkout.
Why it matters: Sequences pace themselves across days without extra tooling.
See it running
This one is best understood live — the interactive demo drives it end to end with simulated triggers.
Execution logs you can audit
Runs are recorded step by step: the node, its kind, the branch taken, exact timing, and a rendered sentence of what was emitted. Filter the log by workflow, status, or node kind; open a run to walk its whole journey; export the history for an audit.
Where it pays off
A customer swears the email never arrived — you open the run, see the connector answered 502, and forward the proof.
Why it matters: Debugging stops being guesswork; the log shows exactly which step, why, and for which record.
Webhook received
Webhook accepted a POST payload from storefront events.
Cart value gate
Cart value ≥ 50 → took the true branch.
Cool down
Held for 1h — let the session cool down.
Send the rescue note
Email queued — "Your cart is waiting".
Connector directory
The directory lists the tools operations teams already run — Slack, HubSpot, Sheets, Gmail, Shopify, Zendesk, Linear and more. Enable a connector and its app options light up inside the builders; disable it and the workspace stops writing there.
Where it pays off
Enable Twilio when the SMS campaign starts, and every send-SMS node picks it up without re-editing workflows.
Why it matters: Credentials and integrations are managed in one obvious place instead of scattered per workflow.
Toggle connectors like the directory does — enabled tools appear inside action builders.
4 of 6 connectors enabled.
Ready-made workflow templates
Start from a blank canvas or from three field-proven shapes: the lead router, the cart rescue, and the weekly exec digest. Templates drop a complete, editable graph onto your canvas — nodes, config, and branches included — so a working draft exists before you finish your coffee.
Where it pays off
Spin up the cart rescue for a second storefront, then retarget its subjects and senders.
Why it matters: The blank-page problem disappears; best practice arrives pre-wired.
In the demo builder you can drag nodes, pan, zoom, wire ports, and save — the exact gestures this diagram abstracts.