Automate & measureBeta

Describe a workflow. Autopilot builds the Loop.

Loops is becoming your n8n: a visual builder where CRM events, schedules and manual triggers flow into data, agent and action nodes. The AI only proposes; a human approves every row before anything happens. Describe what you want and Autopilot scaffolds the graph.

Get started
A visual builder
AI proposes, never fires
You approve each row
Fondaro LoopsFondaro Loops
Automation you can switch on

AI proposes. You approve every row.

Loops is becoming your n8n: a visual builder where CRM events, schedules and manual triggers flow into data, agent and action nodes. Agent nodes can only propose, and every proposal queues in an approval inbox where you approve, edit or dismiss it before anything touches your CRM.

  • Real triggers and nodes. Start from a CRM event, a schedule or a manual run, then flow into data, agent and action nodes on a canvas.
  • AI proposes, never fires. Agent nodes can only propose, and an empty run fails loudly instead of doing nothing quietly.
  • A human approves each row. Every proposal waits in an inbox for you to approve, edit or dismiss before any side effect.
How the AI stays in your control
What you get

Automation you can switch on without losing control

Real triggers

Start a Loop from a CRM event, a schedule, or a manual run, then flow into data, agent and action nodes on a visual canvas.

AI proposes, never fires

Agent nodes can only propose. An empty run fails loudly instead of doing nothing quietly.

A human approves each row

Proposals queue in an approval inbox where you approve, edit or dismiss each one before any side effect.

Real actions, with undo

Approved actions hit real CRM mutations: email, status, task, note and tag, with a 30-second undo on the reversible ones.

Autopilot builds it for you

Describe a workflow in plain language and the Loops agent scaffolds the graph for you to refine.

See what every run did

Display nodes surface a run's results and each proposal keeps its record in the inbox, so an automation is never a black box.

How a Loop runs

Trigger, propose, approve, act

  1. 1

    A trigger fires

    A CRM event, a schedule or a manual run starts the Loop and flows through its nodes.

  2. 2

    The agent proposes

    Agent nodes draft what they would do. They can only propose, and an empty run fails loudly.

  3. 3

    You approve each row

    Proposals queue in an inbox where you approve, edit or dismiss each one before anything happens.

  4. 4

    The action runs, with undo

    Approved actions hit your real CRM, with a 30-second undo on the reversible ones.

From demand to deal

From the first lead to the front-door keys, one place.

The operating system for selling Spanish property abroad. One place for buyer demand, your CRM, the phone, brochures, and your website.

Get Started

We use cookies

We use cookies to ensure you get the best experience on our website. For more information on how we use cookies, please see our cookie policy.
Learn more.

Fondaro Help

Docs & support

Hi there, how can we help?

Browse popular articles or ask a question below.

Popular articles

Powered by Claude

Or ask a question