Workflows
Stages, transitions with conditions, and actions on a timer. Built to describe how your shop really works, not to chain three triggers together.
Everything you can do with operations & automation
Shape the system around your process rather than the other way round.
Inside operations & automation
Every piece that makes this work, and what each one is actually for.
Forms
Public or internal, creating records and kicking off a process the moment they are submitted.
Inventory
Stock, reorder points, and movements, including adjustments for the items nobody thought to track first time round.
Vendors
Suppliers with payment terms, certifications, and purchase history, managed at the org level so terms stay consistent.
Imports & exports
Bulk load with validation, a full run history, and a recovery path when a file was wrong. Everything exports back out, because the data is yours.
Custom fields
Your fields on their records, across every module, without a developer and without forking the data model.
Calculated & rollup fields
Fields that compute from other fields, look up across records, and roll totals up the tree. The spreadsheet column moves into the record it was describing.
Webhooks & API
Outbound webhooks and developer access for the connections that are yours alone to build, on Business.
Requests become scheduled work
Tickets have their own typed stages and SLA clocks that pause while you are waiting on the requester, so the clock reflects your obligation rather than the calendar. Promoting a ticket to a task carries the attachments across, and the ticket resolves when its linked tasks are done. Client facing commitments and internal work are one graph, so SLA state and delivery state cannot tell different stories.
What this removesRe-typing a client conversation into a second tool, and the silent gap between what support promised and what delivery scheduled.
See how everything connectsThe questions this actually answers.
The long version, because this is where the category has real objections.
Can the system match how your shop actually runs?
Workflows here model a real process: stages, transitions with conditions, and actions on a timer, acting across modules rather than inside one. Automate assignments, updates, notifications, and the repeatable steps in between, with retries and a run history you can actually read when something needs explaining. This is process design, not three triggers chained together.
Conditions on every transition
Work moves when the rules say it can.
Timed and scheduled actions
The follow-up happens without a reminder.
A run history you can read
What fired, when, and why.
How does outside information become structured work?
Branded forms with conditional logic, shared publicly or embedded in any website, create records and start a process the moment they are submitted. An inquiry becomes a lead, a request becomes a ticket, an application becomes a task in the right queue, each routed by rules instead of by whoever noticed it first.
What if the data model does not fit your business?
Add custom fields to any module, build whole collections without a developer, and let calculated, lookup, and rollup fields do the math the spreadsheet used to do. You model what your organization actually tracks while keeping one consistent platform underneath it.
What about the day the import file was wrong?
Every import validates before it lands, every run is kept in history, and a bad one has a recovery path. Data moves in at scale, moves back out whenever you want it, and the mistakes are reversible instead of archaeological.
Questions people actually ask
What can workflows automate?
Assignments, status updates, notifications, and repeatable operational steps, across modules, with stages, conditions, timed actions, scheduled runs, and a full execution history.
Can forms be used on our own website?
Yes. Drop a branded form into any site with an embed snippet. Submissions create records in your workspace and can start a workflow on arrival.
Do custom fields work everywhere?
Yes. Custom fields extend every module, collections model anything that is not built in, and calculated, lookup, and rollup fields handle the math.
Is there inventory and purchasing?
Yes. Stock with reorder points and movements, suppliers with payment terms and certifications, and purchase orders with approvals and receiving.
Can we get our data out?
Always. Exports run alongside imports, and Business adds API access, API keys, and outbound webhooks for event-driven connections.
What happens when an import goes wrong?
Validation catches most problems before they land, every run is kept in history, and a bad import has a recovery path back out.
It does not stop at one capability.
Scrambl is one workspace, so the records here are the same records the rest of the platform reads. These pair with it most often.
.svg)
Ready to crack the chaos?
One workspace for projects, clients, finance, and everything in between. Try for free.