FAQ
Quick answers to questions we hear often.
Is Flero self-hostable?
Yes. Flero runs as a Docker Compose stack or in Kubernetes. See the operator guide for setup. Your data and credentials stay on your infrastructure.
Can I use Flero without writing code?
Yes, the visual editor, expression language, and node catalogue cover almost everything. You'll occasionally drop into a Code node for something specialised, but that's the exception.
Does Flero support TypeScript / Python in Code nodes?
Code nodes support JavaScript, Python, and Dart. JavaScript is the default; pick from the language dropdown per node.
Can a workflow call another workflow?
Yes, use the Sub-Workflow node. The parent waits (or fires-and-forgets) for the child to complete.
Are workflows version-controlled?
Each Save creates a new version, retained for the configured retention period. You can restore any prior version from the toolbar's History dropdown.
For deeper Git-style version control, export workflows as JSON (workflow settings → Export) and check them into your repo manually.
Can I migrate workflows between workspaces?
Workflow JSON exports can be imported into another workspace (Workflow list → + Create workflow → Import). Credentials, however, are scoped, you'll re-bind them in the destination workspace.
Does Flero send my data to AI providers?
Only if your workflow uses an AI node configured to call an external provider. Pick a self-hosted provider (Ollama) if you want to keep AI calls local.
Is there an API to manage Flero programmatically?
Yes. Every UI action has an API equivalent, create workflows, trigger runs, manage credentials. See /api-docs for the full reference.
How is my data isolated between workspaces?
At the database level. Cross-workspace queries are admin-only on enterprise plans and are audit-logged.
Can I use Flero with my company's SSO?
Yes, SAML 2.0 and OIDC. Configure under Settings → Organization → SSO. See the operator guide for IdP-specific walkthroughs (Okta, Azure AD, Google Workspace, OneLogin).
What happens to my running workflows if I upgrade Flero (self-hosted)?
Running executions are drained before the upgrade. Workflows on schedules pick up at the next scheduled fire after restart. Long-paused approvals survive across upgrades.
Can I export my execution history?
Yes, from /logs, click Export to get a CSV or JSON dump. For programmatic access, use the /api/executions endpoint.
What's the difference between "draft", "active", and "inactive"?
| State | Triggers armed? | Can run manually? |
|---|---|---|
draft |
No | Yes |
active |
Yes | Yes |
inactive |
No | Yes |
archived |
No | No |
Can two people edit the same workflow at the same time?
Yes, real-time collaboration with shared cursors and field locking. See Collaboration.
How do I share a workflow with someone outside my workspace?
Three options:
- Invite them as a workspace member with
Viewerrole. - Export the workflow JSON and send it to them; they import into their own workspace.
- For approvals only: use a public approval link.
There's no "guest read-only link" for the full editor.
Why does my workflow's URL change between dev and prod workspaces?
Webhook URLs are workspace-scoped. Each workspace generates its own URL prefix. Update the external service to point at the prod URL when you promote.
Where does Flero store secrets?
In an encrypted credential vault, separate from workflow JSON and execution history. Secrets are never returned via the API, never visible in the UI after creation, and never logged. See Security & MFA.
Can I run Flero on my laptop?
Yes, the Docker Compose dev setup runs comfortably on 8 GB RAM. See the operator guide.
Is there a free tier?
Yes for individual / small-team use, with caps on executions and members. Pricing details on the marketing site.
Can I sandbox a single node without sandboxing the whole workflow?
Yes (the inverse, too), each node has a Disable sandbox for this node toggle in its Advanced settings. Use sparingly; it's a foot-gun.
How long are executions retained?
Default 30 days. Configurable per workspace (Settings → Data & privacy → Retention). Plans differ on maximum retention.
Does Flero support webhooks from services like Stripe / GitHub natively?
Yes, through connector triggers for each. They handle signature verification, retries, and event typing for you. See Connector event triggers.
Can I unit-test a workflow?
Not formally, Flero is a runtime, not a test framework. Use sandbox mode for safe iteration, and save mock data to capture known-good responses. For workflows you really want to test, build a parent workflow that asserts on outputs (Schema Validator Guard + Terminal with failed status).
What's the difference between a connector and a plugin?
A connector is a first-party (or partner) integration with a specific service. A plugin is a marketplace package that may include connectors, nodes, or templates. All connectors that exist in the public catalogue are effectively plugins under the hood.
Where do I report bugs?
File issues with your support contact or via GitHub if your instance is the open-source build. Include execution IDs whenever possible.
Related
Found something out of date? This page lives in the Flero docs content set.