What is Flero?
Flero is a visual workflow automation platform for the enterprise. You connect nodes on a canvas to describe an automation, "when an order arrives, post to Slack, write to the CRM, and email the finance team", and Flero runs it for you, every time the trigger fires.
If you've used Zapier, n8n, Make, or Power Automate, the concept will feel familiar. Flero's emphasis is on enterprise depth: 200+ built-in nodes, 40+ connectors, first-class AI/LLM and RAG nodes, multi-party approvals, sandbox mode for safe testing, real-time collaboration, and a serious execution-monitoring story.
πΈ Screenshot needed:
what-is-flero__hero.png, split image showing the editor canvas on one side and an execution detail page (with green-coloured nodes and the timeline) on the other.
What you can build
Three quick examples, from simple to ambitious:
1. Notify on event
A new Stripe charge arrives. Flero receives the webhook, formats the amount and customer name, and posts a message to a Slack channel.
[Webhook: Stripe charge] β [Transform: format message] β [Slack: send message]2. Scheduled data sync
Every hour, pull new HubSpot contacts created in the last hour, enrich each one by calling an external API, and upsert them into Salesforce.
[Schedule: hourly] β [HubSpot: list contacts] β [Loop] β [HTTP: enrich] β [Salesforce: upsert]3. AI-assisted approval workflow
A new purchase order is submitted. An AI agent reviews it against policy, drafts a summary, and routes high-value POs to a finance manager for multi-party approval. On approval, the workflow creates the PO in SAP; on rejection, it emails the requester with the rationale.
[Form: PO submitted] β [AI Agent: policy review]
β
[If: amount > $10k]
βββ true β [Approval: finance manager] β [SAP: create PO]
βββ false β [SAP: create PO]How Flero compares
| Flero | Zapier | n8n | Power Automate | |
|---|---|---|---|---|
| Visual editor | β | β (linear) | β | β |
| Self-hostable | β | β | β | Limited |
| Built-in AI nodes (multi-provider) | β | Partial | β | β (Microsoft) |
| Approval workflows | β multi-party | Limited | Limited | β |
| Real-time collaboration | β | β | β | Limited |
| Sandbox / mock-data testing | β | β | β | Partial |
| RAG / vector-DB nodes | β | β | Partial | Partial |
| Connector count | 40+ | 6,000+ | 400+ | 1,000+ |
Flero is the right choice when you need enterprise execution depth and self-host control. It's a less natural fit if you need every long-tail SaaS connector under the sun, Zapier still wins on raw breadth.
Key vocabulary (just enough to start)
These five terms will appear on almost every page. A deeper treatment is in Core concepts.
- Workflow, the automation itself: a graph of nodes and connections.
- Node, one step in the workflow (an HTTP call, an If/Else, an AI prompt).
- Trigger, the special node that starts the workflow (webhook, schedule, form submission, manual click).
- Execution, one specific run of the workflow, with its own ID, status, and outputs.
- Expression, dynamic text inside
{{ }}that pulls data from another node at runtime, e.g.{{ $node["HTTP"].json.body.email }}.
Where to go next
| You want to⦠| Go to |
|---|---|
| Get into Flero | Signing up and logging in β |
| Build your first workflow | Your first workflow β |
| Understand the model in depth | Core concepts β |
| Tour the app first | Tour of the app β |
Found something out of date? This page lives in the Flero docs content set.