Introduction
Sample documentation (demo only)
This is an incomplete, outdated docs snapshot shipped with the playground — screenshots were removed on purpose.
For the full, current manuals go to voodflow.com/docs.
Voodflow is self-hosted, data-sovereign workflow automation for Filament. You design automations visually inside your Laravel admin — triggers fire, nodes transform data, integrations call external systems, and approvals pause for humans when needed.
Your workflows, credentials, and execution logs stay in your infrastructure. There is no required third-party automation cloud.
Why teams use Voodflow
| Theme | What you get |
|---|---|
| Data sovereignty | Credentials and run data remain on your servers |
| Filament native | Resources, navigation, and branding match your panel |
| AI-ready | Call any LLM or HTTP API from integration nodes |
| Portable | Import / export workflow definitions as JSON |
| Observable | Structured logs per execution and per node, with retention controls |
| Extensible | Custom PHP nodes via the package node APIs |
| Webhooks | Inbound endpoints and outbound pushes with signing support |
Typical uses
- Notify teams when a Filament model changes
- Sync records to third-party APIs
- Gate publishing or fulfilment on approvals
- Orchestrate scheduled maintenance with structured logs
- Connect AI APIs for classification, summarisation, or enrichment
Relationship to VoodBuilder
Voodflow and VoodBuilder share the Filament panel and branding story, but solve different jobs: automation vs public site. Install either or both depending on the product you are shipping.
Editions note
Product editions (for example Whitelabel / OEM) exist for branded and multi-tenant distributions. This documentation covers the public product surface. Commercial questions: sales@voodflow.com.
Next: Installation.