attendo Flows

Your processes, automated and with a trail

Requests, approvals, onboarding and reviews that travel by email and spreadsheet today, turned into processes with stages, forms, tasks and signatures. You draw the process, or describe it to marIA, and attendo runs it.

  • Approval by link, no user account
  • History of every run
  • Inbound and outbound webhooks
Visual editor of a process with its states and transitions, the conditions of each step and the AI agents panel with its scoring.
The process editor: states, transitions and conditions, with AI Autopilot agents at each step.

If this sounds familiar, keep reading

The process exists. It lives in someone’s inbox.

A purchase request goes through three emails before it is approved. Onboarding a new hire depends on someone remembering to tell IT. The quarterly review happens when somebody remembers it.

Nobody knows which step anything is at. And when the person who runs it goes on vacation, the process stops.

  • Not approved

    Approvals that get lost

    Without an approval workflow, the approver never sees it, or approves it in passing. Later, nobody can find the yes.

  • Not logged

    A spreadsheet per department

    Purchasing, quality, HR and administration each keep their own log, and data is copied by hand from one to the next.

  • Missing requirement

    Steps that get skipped

    The document closes without the signature or the checklist. It comes out in the audit.

  • No traceability

    One tool for each thing

    One service for alerts, another for forms and another for signatures. Each with its own permissions and its own log.

How it works

From spreadsheet to a process that gets followed

Six steps to turn an email-driven process into one with stages, owners and a trail.

  1. Step 1

    Pick the process

    One that hurts today: a purchase request, onboarding, a nonconformity or a periodic review.

  2. Step 2

    Define the document

    A document type with its fields, its intake form and its statuses. No code.

  3. Step 3

    Set stages and requirements

    With Business Process Flow (BPF): what it takes to move to the next stage, who approves and what blocks closing.

  4. Step 4

    Add the rules

    With the Flow Builder: alerts, tasks, emails, calls to other APIs and AI at the step where you want it.

  5. Step 5

    Test it and switch it on

    The validator will not let an incomplete flow go live. You simulate it with no side effects, review it and publish it.

  6. Step 6

    Follow it

    Every run records the path it took, and the status board shows where work is piling up.

Flow Builder

If this happens, do that

A flow starts when something happens and acts without anyone having to remember. You draw it in a visual editor: trigger, conditions and actions.

If the owner is on vacation, the flow knows from the business calendar and passes the work to whoever is in.

  • Triggers: email, call, WhatsApp, form, webhook, time, button or status change
  • Also the life of an appointment (confirmed, rescheduled, canceled or no-show) and of a web quote (viewed, signed, paid or declined)
  • Conditions on the document, customer or contract, and routing by value
  • Actions: create, assign, change status, send an email, text or WhatsApp message, or call any API
  • Checks the business calendar and hands the work to whoever is available
  • Built-in flows ready to switch on
See the flows module

Business Process Flow (BPF)

Staged processes nobody can skip

BPF sets the path of a document: which stage it is at, what it needs to move forward and who has to approve. The approver gets a link and does it from their phone.

What the procedure requires no longer depends on anyone’s memory.

  • Stages visible on the record, each with its requirements
  • Closing is blocked until the checklist is signed
  • Approval by link from a phone, with a code and no user account
  • AI plays no part in execution: the process is exactly the one you design

AI-Flows

AI where you put it, and only there

AI is one more step in the flow, not a black box. An AI decision node reads the incoming email and picks the branch: complaint, order or inquiry.

And the AI status screen shows at a glance which provider you use, what budget it has and what is left to set up.

  • A flow step summarizes text, transcribes audio or detects tone
  • AI decision nodes: the flow takes the right branch based on what the message says
  • Describe the flow in plain language and marIA proposes it
  • Every AI operation is logged with its cost, under the monthly cap you set
AI status screen with the AI provider, monthly budget, email sending provider, ad accounts, public chatbot and LinkedIn, each with its status.
AI status: what is set up in your instance and what is missing, at a glance.

Forms, tasks and documents

Everything a process needs, already built in

A process is more than a diagram. It needs an intake form, tasks with owners, a checklist, a signature and a document generated at the end.

In attendo they are modules of the same platform, on the same document: no need to connect five tools to make one process work.

  • attendo Forms: public, internal or QR forms that create the document
  • Task templates per document type, with owner and due date
  • attendo Checklist with photo, signature and template version
  • Contracts and formal approvals signed with attendo eSign
  • Documents generated with your template and branding

Webhooks and integrations

What happens outside can start what happens inside

If your ERP sends a webhook for a new order, a flow gets the work ready in attendo. And when a document is approved, an outbound webhook lets whichever system needs it know.

Every call stays in the flow’s history, with what was sent and what came back.

  • Inbound webhooks: an external system starts a flow
  • Outbound webhooks, with history and resend
  • A step that calls any API, no code needed
  • Native connectors for Odoo, SAP Business One, Business Central, Holded and humaneo
  • MCP connectors inside flows
See API v4, webhooks and MCP

Control

If a flow does something odd, you can see it

Automating without seeing what happens just trades one problem for another. Every run leaves its trail, and marIA explains in plain language why a flow took a given path.

  • A validator that will not let an incomplete flow go live
  • The history of every run, step by step
  • Versions, restore and simulation with no side effects
  • Flows that write to your customers come switched off
  • Your flows are left untouched when attendo is updated
  • An attendo Flows dashboard: runs per flow, errors, approvals pending or about to expire, stalled documents and AI cost against the cap

By department

Processes you set up without code

  • Purchasing: a request through an internal form, approval by link and the purchase order to the supplier
  • Human resources: onboarding a new hire, with tasks for IT, administration and their manager
  • Quality: a nonconformity with root cause analysis, corrective action and a verified close-out checklist
  • Administration: expense approval with the receipt and a signature
  • Legal: a contract with review, approval and e-signature
  • Management: a report with the KPIs you choose, emailed on the schedule you set

See use cases by department

Who it is for

The most common industries. And any other.

attendo Flows adapts to any industry and any company, in any country, with its own document types, fields and vocabulary, and no custom development. These are the most common ones, not the only ones.

Types of business

  • Companies that sell to other businesses
  • Companies that sell projects or professional services
  • Companies with repeat or subscription customers
  • Organizations that maintain their own assets
  • Public administrations and agencies

marIA in your processes

Describe the process. marIA draws the flow.

  • Proposes the flow

    You describe it in plain language and marIA proposes the flow, or changes to an existing one. You review it before saving and undo it if it does not convince you.

  • Picks the branch

    An AI decision node classifies the message or document so the flow continues down the right path.

  • Summarizes and transcribes

    At the step you choose: a summary of a long email, the transcript of an audio file or the tone of a message.

  • Explains a run

    If a flow did something unexpected, marIA tells you why, step by step.

  • Agents that prioritize

    With AI Autopilot (Multiple AI Agents), every document in the process gets a score from 0 to 100 and goes to a person when it crosses a threshold.

What it does not do: run BPF processes, approve on anyone’s behalf or write to your customers by default. Without AI, attendo Flows works in full.

See the attendo AI

Integrations

Connected to what you already use

The connectors with the ERPs and with humaneo are native. Email from Microsoft 365 or Google, WhatsApp, Teams and Slack come in as triggers. And anything without a connector comes in through API v4, a webhook or MCP.

It all runs on the automation layer shared by every attendo solution: the same statuses, the same SLAs and the same business calendar. We cover it in detail on the automation page.

See integrations

Honest comparison

Where it fits (and where it does not)

We would rather you know now than at the third meeting.

If your priority is…attendo Flows
Processes that touch documents, customers, contracts or assets already in attendoattendo FlowsThis is its home turf: the process and the data are in the same place
Approvals, forms, tasks and signatures for any department, with no codeattendo FlowsA good fit
Connecting hundreds of third-party apps to each other, without the data passing through attendoattendo FlowsAn integration platform is the better choice. attendo connects to it by webhook
Automating clicks on other programs’ screens (RPA)attendo FlowsAn RPA tool is the better choice

Use cases: purchasing, quality and human resources. If your process is about compliance, see attendo Compliance.

Compare attendo vs. Excel, calculate the return on attendo and read how to go from three systems to one. In the glossary: escalation.

Frequently asked questions

Frequently asked questions

What is business process automation software?

Software that turns a process run over email and spreadsheets into steps that run on their own: the request comes in, tasks are assigned, approval is requested and a trail is kept. attendo Flows does this on the same platform where your documents, customers and contracts live.

Is it a BPM tool?

It does the job of a BPM tool: with Business Process Flow (BPF) you define a process’s stages, their requirements and who approves, and with the Flow Builder you add the rules. It is configured without code.

What is the difference between the Flow Builder and BPF?

The Flow Builder reacts to what happens: if this comes in, do that. BPF marks the stages of a document and what it needs to move forward. The same process often uses both.

How can someone approve without a user account?

The approver gets a link, enters a code and approves or rejects from their phone. Who did it and when is logged.

I do not know how to design flows. Can I set it up myself?

Yes. You describe it in plain language, marIA proposes the flow and you review it before saving. Without AI the editor works the same, and there are built-in flows ready to switch on.

Does it connect to my ERP and other applications?

Yes. The connectors with Odoo, SAP Business One, Business Central, Holded and humaneo are native. Everything else comes in through API v4, inbound and outbound webhooks or MCP.

Do I lose my flows when attendo is updated?

No. Configuration lives in data, not in custom code. Your flows are left untouched, and the built-in ones are only restored when you ask.

Can I create flows through the API?

No. Flows are configured in the editor. The API reads and writes the data they work with.

Request a demo

Bring the process that generates the most email

A purchase request, onboarding or a periodic review. We will show it to you set up in attendo, with its stages, its approvals and its trail. If it is not a fit, we will tell you.

  • With your operation, not a generic demo
  • A real person from our team replies
  • No cold calls afterwards

Would you rather talk first?

Which area do you want to see in the demo?

With your work email we prepare the demo around your case.

In one or two sentences.

If you chose Maintenance (CMMS)

If you chose Field work (Field Service)

If you chose Facility Management

If you chose any other area

Only if you would rather we call you.

Data protection. Controller: AxisOne Group SL. Purpose: preparing the demo you request and replying to you. Legal basis: your consent and the request you make. Recipients: we do not disclose your data; Cloudflare (website) and Brevo (email notices and confirmation) process it on our behalf. Rights: access, rectification, erasure, objection, restriction and portability, at privacy@attendo.me. More information in the privacy policy.

What happens when you send it. Someone from our team reads what you tell us and writes to you to agree on a time for the demo. Our hours: Monday to Thursday 9:30 AM to 6:30 PM and Friday 9:30 AM to 2:30 PM, Spain time.