Automation · Builder
Internal betaDraw the process, then prove it.
A canvas of steps — approvals, tasks, conditions, delays and sub-workflows. Validate it, run it in a sandbox, then publish.
- Approval and automation workflows
- Conditions with AND, OR and NOT
- Validate, test, then publish
- 01Draft
- 02In review
- 03Testing
- 04Ready
- 05Published
The canvas
Drop in a step, set who decides.
Add an approval, choose its rule — one, any, all, or at least N — and who can approve. Validation checks the graph, the conditions and the steps; a test run plays it through in a sandbox.
01Drop in a step
02Set who approves
03Validate
04Test run, in a sandbox
Logic
Branch it, join it, nest it.
01
Conditions
AND, OR and NOT groups over record fields: equals, greater than, contains, in, between, before, within N days.
02
Parallel paths
Branches that meet again: wait for all, go on with the first, or when N have finished.
03
Sub-workflows
Call one workflow from another, and wait for it to finish if you need its result.
Drafts and tests
Test it before it's real.
Drafts move through review and testing before they publish. A test run streams node by node with outside calls mocked, so nothing real is touched.
The rest of Automation
Where to go next.
- OverviewDraw a workflow; it runs inside Fyboard.
- AnalyticsRuns, success, time — and every run's timeline.
- Deadlines & escalationApproval timeouts, escalation, delays.
- Starting points29 module operations that wait on a workflow.
- Webhooks & APISigned webhooks in, HTTP calls out.
- Use casesLeave, purchase orders, contracts, budgets.
- PricingPlans from billing's catalogue.
Questions
Asked and answered.
Is Automation available now?
It's on internal beta, by invitation. Workflows run inside Fyboard modules — 29 operations across People, Materials, AlphaCore, Projects and Finance can wait on one; Materials, Projects and Finance themselves are still in the pipeline.
What can a step do?
Update, insert or delete records, set a status, change fields, send an email or a notification, call an API, wait, approve, or start a sub-workflow.
Can I loop?
A path can go back on itself if it has a way out; there's no for-each step yet.
Is there version history?
Workflows have versions and a draft lifecycle; a history view in the builder isn't there yet.
Automation
Draw it, test it, ship it.
Start from a blank canvas or a module operation, and run it in the sandbox before anyone waits on it.