TakiFlo documentation
TakiFlo is a workflow platform for processes that people run. Design a process once, run every piece of work through it, and see exactly where each one has got to.
What TakiFlo is
A workflow is a directed graph. Each node is a stage of the process and each edge is a dependency, so a stage becomes available only once the stages feeding into it are done.
Processes branch, run stages in parallel, and come back on themselves when work is rejected and has to be redone. A workflow can express all three, which is the difference between modelling a real process and modelling a checklist.
The three things to know
| Nodes | Individual stages of work in your process. |
| Edges | Connections deciding which stages must finish before the next can start. |
| Jobs | A copy of the workflow taken when real work begins, tracked to completion. |
The third one carries the most weight. A workflow is a template, and each job takes its own copy of it. Publishing a change to a template never disturbs work already in flight, so a job that started last week still shows the process it started under.
What you can do with it
- Business processes. Approval workflows, onboarding, anything with stages and handoffs.
- Customer and stakeholder views. Shareable links that show progress on a job without an account.
- Outbound webhooks. Notify your own systems as stages change state.
- Versioned processes. Publish changes without disturbing jobs already running.
Where to go next
- Getting started takes an empty account to a running job.
- Workflows covers templates, versions and the stage types.
- API reference documents every endpoint, with samples you can run from the page.
- Embedding puts TakiFlo's screens inside your own application.
Need Help?
We're here to support you every step of the way.