Automation
Internal betaApprovals and automation, built into the work.
Draw a workflow and publish it: approval chains, record updates, emails and HTTP calls, run by an engine that keeps its place — inside the Fyboard modules your team already uses.
- 29 module operations can wait on a workflow
- Approve by one, any, all, or at least N
- Retries, timers and idempotency built in
- 01Draft
- 02In review
- 03Testing
- 04Ready
- 05Published
End to end
Draw it once, it runs every time.
A leave approval drawn on the canvas and published: the manager decides, a condition sends long leave to HR, the record is updated and the employee is emailed — step by step, in the run log.
01Draw the flow
02Publish it
03A request arrives
04It runs, step by step
Where it's wired in
Leave, purchase orders, contracts and budgets wait for their workflows.
- module operations that can wait on a workflow
- 29
- module operations that can wait on a workflow
- modules: People, Materials, AlphaCore, Projects, Finance
- 5
- modules: People, Materials, AlphaCore, Projects, Finance
- ways to start: a record change, an operation, a schedule, a webhook, by hand
- 5
- ways to start: a record change, an operation, a schedule, a webhook, by hand
- approval rules: one, any, all, or at least N
- 4
- approval rules: one, any, all, or at least N
The pieces
Approvals, triggers, and runs that last.
01
Approval chains
One, any, all, or at least N approvers — a person, a role or a manager — with send back.
02
Five ways to start
A record changes, an operation waits, a schedule ticks, a webhook arrives, or someone presses Start.
03
Runs that recover
Retries with backoff, idempotency keys that skip repeats, timers that survive a restart.
The engine
It keeps going when things don't.
Every run is kept as state, not just a log, so a restart doesn't lose it.
- 01State in the databaseRuns, steps, timers and signals are stored; a run resumes where it stopped.
- 02Retries and timeoutsFixed or exponential backoff, a 30-second default per action, heartbeats on long steps.
- 03No double workIdempotency keys skip repeats; loops across chained workflows are stopped.
- 04Branches that meetRun paths in parallel and join them: wait for all, the first, or a quorum.
The rest of Automation
Where to go next.
- BuilderSteps, conditions, joins; validate and test.
- 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.
Can it connect to other tools?
Through webhooks both ways: signed inbound webhooks start workflows, and HTTP steps call any API. There are no pre-built app connectors yet.
What happens when a step fails?
It retries with backoff if you've set retries. After that the workflow halts, carries on, or takes an error path — you choose per step.
Does it track SLAs?
Not as SLA policies. Approval steps can time out and bring in an escalation approver, and analytics show how long each step takes.
Automation
Draw your first workflow.
Start with an approval your team already asks for, publish it, and watch the first run go through.