Integrations

attendo is not your ERP. It talks to it.

Operations live in attendo and accounting lives in your ERP, with nothing typed twice. Connectors for the most widely used ERPs in Spain, for Microsoft 365 and Google, for the leading AI providers, and API v4 for everything else.

  • Every connection with its real status
  • You decide what data travels
  • API v4 with per-key permissions

The problem

The same customer, entered twice

The back office retypes into the ERP a delivery note that already existed. The customer is in there twice, with two different addresses. And the technicians’ hours never get invoiced, because they live in another program.

The principle

Operations in attendo, invoices in your ERP

attendo runs operations: tickets, work orders, service reports, quotes, orders and delivery notes. The invoice is issued by your connected ERP, with its official numbering, which flows back to attendo automatically. Nobody types anything twice.

One by one

The most requested integrations, explained one by one

What each one solves, what travels and in which direction, what you need to get it live and what it does not do.

API v4, webhooks and MCP

Is your system not on the list? This is for you

API v4, a REST API documented with OpenAPI, is organized in packages: read-only, field, sales, ERP and AI assistant. Each key can only perform the operations you allow, and this is checked on every request. If a key leaks, the possible damage is limited to what you decided.

And if you work with an AI assistant, attendo as an MCP server lets it query your operations with each person’s permissions.

  • Documents, customers, contracts, assets, projects, checklists and attachments
  • Keys with expiry, rate limits and revocation
  • System accounts for your integrations
  • Outbound webhooks with history and resend, and inbound webhooks into your flows
  • A flow step that calls any API, without coding
  • MCP server: query attendo from Claude or ChatGPT, with each person’s permissions and write access turned off
  • MCP client: attendo connects to third-party MCP servers from flows and from the record
See the API and webhooks

How an integration is done

No surprises in production

Four steps, from mapping to production.

  1. Step 1

    Mapping session

    Number series, taxes, products and which records travel, with your team.

  2. Step 2

    Testing in your test environment

    Nothing touches your live ERP until it works.

  3. Step 3

    You decide what travels

    In Odoo, Business Central, SAP Business One and Holded you flag which records are synced. If you untick one and tick it again, syncing resumes with no duplicates.

  4. Step 4

    In production, with a safety net

    Changes are queued with retries. If the ERP goes down, they wait and are applied when it comes back.

Limits

Where it fits (and where it does not)

  • Invoicing, accounting and payroll

    attendo is not an ERP or accounting software: it does not issue invoices or replace your accounting or payroll software.

  • Document management

    It does not use OneDrive, SharePoint or Google Drive for document management.

  • App catalog

    We do not have a huge app catalog. We have the connectors for the Spanish market, and if you depend on a specific app, tell us.

Frequently asked questions

Frequently asked questions

Does it replace my invoicing?

No. attendo is not an ERP or accounting software. The invoice is issued by your connected ERP, with its own numbering, and the ERP handles tax filings. attendo passes it what is billable, and the connector is validated against your test environment.

Who gets each integration live?

You set it up with your credentials, and we help you get it live: setup, testing in your environment and validation before going to production. “Custom” is a connector built for your system on top of the API, webhooks or the MCP client.

Does it connect in one click?

No, and be wary of anyone who tells you so. Mapping number series, taxes and products takes a session with your team. After that, it runs on its own.

What if our ERP goes down?

Changes are queued and applied when it comes back.

Our system is not on the list.

API v4, webhooks, the HTTP step in flows and the MCP client, which connects attendo to third-party MCP servers, cover most cases. If not, a connector is built as a project.

Does it connect to our corporate directory?

Your team logs in with Microsoft Entra ID, Google or Auth0.

We already use Microsoft 365 Copilot.

Connect it as the AI provider for attendo and use attendo as an MCP server from your assistants.

Can it coexist with our current CRM or help desk?

Yes, through the API. You can consolidate step by step.

Request a demo

Tell us what you use. We will tell you how it fits.

Tell us about your ERP and your tools, and we will show you what would travel, in which direction and how it is tested.

  • 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.