Skip to content

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 idea will feel familiar. Flero focuses on enterprise depth: built-in nodes for data, logic and code, connectors for dozens of business platforms, AI Agent and RAG nodes, human approvals, sandbox mode for safe testing, a full log of every run, and an AI builder that builds workflows from a plain-language description.

The lower half of an execution detail page: the last timeline row, the Workflow Structure diagram with Start, HTTP Request and Log each marked with a green tick, and the execution and workflow information cards.The lower half of an execution detail page: the last timeline row, the Workflow Structure diagram with Start, HTTP Request and Log each marked with a green tick, and the execution and workflow information cards.

What you can build

Three quick examples, from simple to ambitious:

1. Notify on event

Your payment system sends a webhook when a charge succeeds. Flero receives it, formats the amount and customer name, and posts a message to a Slack channel.

Workflow: Charge succeeded to Format message, Format message to Post to #sales Charge succeededAPI/Webhook TriggerFormat messageSet Post to #salesSlack

2. Scheduled data sync

Every hour, Flero pulls new HubSpot contacts and upserts each one into your database. When the loop finishes, it posts a summary to Slack. The scheduled data sync recipe builds this step by step.

Workflow: Every hour to Find new contacts, Find new contacts to Each contact, Each contact to Upsert contact, Upsert contact to Each contact, Each contact to Post summary Every hourScheduler Find new contactsHubSpot CRMEach contactLoopUpsert contactDatabase Post summarySlack

3. AI-assisted approval workflow

A purchase order is submitted. An AI agent reviews it against policy and drafts a summary. Orders over £10,000 go to a finance manager for approval. Approved and low-value orders are sent to your ERP; rejected ones get an email back to the requester.

Workflow: PO submitted to Policy review, Policy review to Over £10,000?, Over £10,000? to Finance sign-off, Over £10,000? to Create PO in ERP, Finance sign-off to Create PO in ERP, Finance sign-off to Tell the requester PO submittedForm Trigger Policy reviewAI Agent Over £10,000?IfFinance sign-offApproval Create PO in ERPHTTP Request Create PO in ERPHTTP RequestTell the requesterEmail

How Flero compares

Flero Zapier n8n Power Automate
Visual editor ✅ ✅ (linear) ✅ ✅
Self-hostable ✅ ❌ ✅ Limited
Built-in AI nodes (multi-provider) ✅ Partial ✅ ✅ (Microsoft)
Approval workflows ✅ Limited Limited ✅
Build from a description (AI builder) ✅ Partial Partial Partial
Sandbox / mock-data testing ✅ ❌ ❌ Partial
RAG / vector-DB nodes ✅ ❌ Partial Partial
Connector count Dozens 6,000+ 400+ 1,000+

Flero fits best when you need enterprise execution depth, control over where it runs, and a record of every decision. It's a less natural fit if you need every long-tail SaaS connector. Zapier still wins on raw breadth. For a service without a connector, the HTTP Request node calls its API directly.

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, an AI Agent).
  • Trigger: the node that starts the workflow (webhook, schedule, form submission, or the Start node for manual runs).
  • Execution: one run of the workflow, with its own ID, status and outputs.
  • Expression: a lookup inside {{ }} that pulls data from another node when the workflow runs, for example {{ $node["HTTP Request"].output.response.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.