AI Agents for CRM and ERP: Copilot Studio, Agentforce, n8n or Custom
Choosing AI agents for CRM and ERP integration is less about the model and more about where your data lives, because this is the point where an agent stops answering questions and starts changing customers, orders, stock and invoices. The question founders and operations leads actually bring us is rarely "which agent is best?". It is which of these platforms connects to the CRM and ERP we already run, without putting invoicing at risk. This guide answers it with a decision table by stack, each option on its own terms, and a connector matrix for HubSpot, Salesforce, Business Central, SAP, Odoo and Sage checked against the official directories on 2 November 2026.
TL;DR:
- There is no single best AI agent platform for CRM and ERP: you pick by stack. Microsoft 365 and Business Central → Copilot Studio (plus Business Central's own Sales Order Agent); Salesforce → Agentforce; SAP → Joule; CRM and ERP from different vendors → an orchestration layer such as n8n, or a custom agent on the APIs.
- Native connectors thin out fast below the big names. On 2 November 2026, n8n had no built-in Business Central, SAP or Sage node, Zapier's Business Central app was read-only, and Power Platform listed no Odoo or Sage connector.
- What separates a demo from production is the control layer, not the platform: a least-privilege service user, draft-first writes, a log of every action, human approval on critical steps, and idempotency.
- Never let an agent post or issue invoices on its own. It prepares a draft and a person posts it. Where invoicing must run through certified software, as in Portugal, an issued invoice is a tax document from the moment it exists, not a draft you can quietly fix.
- For mixed stacks such as HubSpot + Business Central or a Portuguese ERP, Unlocking Tech (Lisbon) builds custom agents with human approval and every action logged, for a one-off setup from €1,500 per agent or a fixed monthly fee.
Which AI agent platform is best for CRM and ERP integration?
None is best in general; the right one is the one that fits the stack you already run. A good agent for this job reads business data, takes actions in your systems and respects each user's permissions — so the deciding factor is where that data lives. This is the table we use in a first conversation, built on the stacks we see in European mid-market companies:
| Your stack | Pick | Why | Watch out for |
|---|---|---|---|
| Business Central + Microsoft 365 | Copilot Studio; for email orders, Business Central's Sales Order Agent | Native Microsoft connectors in the same tenant | Billed in Copilot Credits; anything outside Microsoft needs a custom connector |
| HubSpot + Business Central | n8n or a custom agent; Make has native apps for both (its Business Central app needs the Enterprise plan) | CRM and ERP from different vendors: no native agent covers both | n8n reaches Business Central only over HTTP; Zapier's Business Central app is read-only |
| HubSpot + Sage | Make or Zapier for Sage Accounting (cloud); a custom agent for other Sage products | Sage Accounting has native apps on Make and Zapier | Other Sage products differ by product and country — confirm the API before you budget |
| Salesforce + SAP S/4HANA | Agentforce on the CRM side, Joule on the SAP side, MuleSoft or code in between | Each vendor's agent works on its own data | A process that spans both needs a layer above, and you pay two consumption meters |
| SAP Business One | A custom agent, scoped with your SAP partner | On 2 November 2026 we found no native SAP Business One app in the n8n, Make, Zapier or Power Platform directories (Zapier lists it as not yet available) | Effort depends entirely on the API your installation exposes |
| Odoo | n8n, Make or Zapier | Native Odoo connector in all three (Zapier's ERP app is for self-hosted Odoo; for Odoo Online it only has a CRM app) | No Odoo connector in Power Platform |
| Pipedrive + an online invoicing tool | Zapier or Make | Native apps on both sides in most cases | "Create invoice" actions exist — and are exactly the ones to gate |
| A Portuguese ERP (PHC, Primavera) | n8n or a custom agent over the API | Zapier has apps for PHC GO and Jasmin; n8n, Make and Power Platform have none | PHC CS needs scripts written inside PHC; the full matrix is in the Portuguese version of this guide |
Across every row the rule is the same: the model interprets and proposes; the integration layer validates and executes. You don't replace your CRM or ERP — you put a layer between the agent and your systems that enforces the rules, which is what our AI integration services build.
What does an agent need to work safely with CRM and ERP data?
Six things, and the platform only solves part of them. Use this list to assess any option, including the one being sold to you:
- Reads production data, not exports — the live CRM and ERP, through their APIs.
- Writes with validation and a dry-run — deterministic checks run in code before anything is saved, and a dry-run shows what would be written.
- Respects permissions — a service user with the least privilege the task needs, never an admin account. It is the design Microsoft uses for the Business Central Sales Order Agent, which operates within the permissions and profile an administrator assigns.
- Logs every action — what it read, what it proposed, who approved and what it wrote.
- Asks for human approval on critical steps — orders above a threshold, price changes, anything that touches the books.
- Recovers from errors without duplicating — idempotency, an error queue with replay, and respect for API rate limits.
Unlocking Tech launches every agent with a person in the loop — approval on risky steps, a cost ceiling per run and every action logged — and raises autonomy only when measured accuracy justifies it. In a demo these six look optional; in production they are the job, which is the argument of why your AI agent isn't reliable enough to scale.
What are the options, one by one?
There are three families — the CRM and ERP vendors' own agents, orchestration platforms and custom agents — plus RPA for systems with no API. For each: what it is best for, where it breaks, how it is priced (figures are in the cost section) and how it reaches an ERP outside its own ecosystem.
Microsoft Copilot Studio
Microsoft's platform for agents built on Power Platform connectors, HTTP requests, agent flows and MCP — and, where no API exists, computer use from a virtual machine, according to Microsoft's integration guidance (checked 2 November 2026). The request for information action pauses an agent flow and collects a reviewer's input by email in Outlook.
- Best for: companies on Microsoft 365 and Dynamics 365, Business Central included.
- Where it breaks: every system outside Microsoft without a prebuilt connector becomes a custom connector that someone builds and maintains.
- Pricing model: Copilot Credits, in packs or pay-as-you-go.
- Other ERPs: through the connector list where one exists (SAP ERP, SAP OData, Business Central), otherwise a custom connector or HTTP.
Salesforce Agentforce
Salesforce's agent layer. Salesforce describes MuleSoft as the automation layer that connects Agentforce to any system, with MCP and A2A as the open protocols (Agentforce platform). Its interoperability guide gives a clean rule: if the other side is modelled as a tool, use MCP; if it is a collaborating agent, use A2A.
- Best for: companies where Salesforce is the central CRM.
- Where it breaks: the value sits in Salesforce data; the ERP is still an integration project.
- Pricing model: Flex Credits per action, or per-user add-ons.
- Other ERPs: MuleSoft, middleware or code.
SAP Joule
SAP's assistant and family of agents. Joule Base comes at no additional cost, and Premium agents are consumption-priced in AI Units (SAP Learning).
- Best for: processes that start and end inside SAP.
- Where it breaks: once a non-SAP CRM sits in the middle of the process, Joule stops being the natural layer.
- Pricing model: Base included; agents in AI Units.
- Other ERPs: not its job.
HubSpot's agents (Agent Hub)
HubSpot groups its agents in Agent Hub — Customer Agent, Prospecting Agent, Data Agent, marketing agents and an Agent Builder for your own — with Breeze Assistant as one place to reach them (HubSpot AI, checked 2 November 2026).
- Best for: work that starts and ends in HubSpot — service, prospecting, data quality.
- Where it breaks: when the process needs the ERP (stock, balances, orders), it cannot get there on its own.
- Pricing model: included in Starter, Professional and Enterprise editions; many agents consume HubSpot Credits.
- Other ERPs: no.
n8n
A workflow platform with AI agents that you can host on your own infrastructure. It advertises 500+ native integrations and "any API via HTTP" (n8n.io), and it can require human review before an agent uses a tool: the workflow pauses, someone approves or denies in Slack, Teams, Outlook or WhatsApp, and the tool only runs if approved (n8n docs).
- Best for: mixed stacks — HubSpot on one side, an ERP from another vendor on the other — and teams that want data on their own servers.
- Where it breaks: business logic spread across dozens of nodes is hard to test and review; log streaming to external logging tools is not in the free Community Edition.
- Pricing model: per workflow execution; the self-hosted Community Edition is free.
- Other ERPs: a native Odoo node; Business Central, SAP and Sage through the HTTP Request node (the Dynamics CRM node covers accounts only). The build pattern is in how to build an AI agent.
Make and Zapier
The most widely used no-code platforms for connecting SaaS apps. Make lets you choose an EU data centre when you create an organisation, and that choice cannot be changed later (Make Help Center); Zapier has a Human in the Loop app to request approval mid-workflow.
- Best for: simple flows between SaaS tools, at low volume, built by people who don't code.
- Where it breaks: credit, pricing and exception rules buried in visual scenarios are hard to version and test.
- Pricing model: credits (Make) or tasks (Zapier), plus model usage.
- Other ERPs: Make has native apps for Business Central and SAP S/4HANA Public Cloud (both on its Enterprise plan), Odoo and Sage Accounting in its official app docs; Zapier has apps for most of them, plus PHC GO and Jasmin for Portugal.
RPA: UiPath and Power Automate
RPA mimics clicks in the user interface and exists for systems with no API. UiPath's Action Center pauses a process until a person reviews or approves, and UiPath offers a self-hosted install on its Standard and Enterprise plans (UiPath).
- Best for: legacy ERPs with neither an API nor file import.
- Where it breaks: it breaks when the screen changes, and maintenance never ends.
- Pricing model: per user or per robot.
- Other ERPs: through the interface — and if an API exists, almost always the worst option.
Custom agent (model APIs and code)
Your own code: a language model called through its API (Claude, GPT or Gemini, priced per million tokens), typed tools that call your CRM and ERP APIs, and an orchestrator such as LangGraph, MIT-licensed, which can pause before a critical action and ask for approval.
- Best for: when the logic is the business (credit, margins, stock rules), when the process spans three or more systems, when the ERP only exposes SOAP or an extensible API, or when the audit trail has to satisfy a reviewer.
- Where it breaks: it needs software engineering — authentication, tests, monitoring — and someone to maintain it.
- Pricing model: development, plus tokens and hosting.
- Other ERPs: any surface that exists.
Unlocking Tech, a Lisbon-based AI engineering company, builds custom agents wired into HubSpot, Dynamics 365, Sage and Outlook, and into Portuguese ERPs such as PHC and Primavera, and the code stays with the client. At Grupo Filtrarte, two of its agents run in production across HubSpot, Outlook and WhatsApp.
Copilot Studio vs Agentforce vs n8n vs custom: how do they compare?
None wins on every criterion; the question is which loses least on the one that matters to you. Checked against official pages on 2 November 2026. "Not verified" means we found no public documentation either way — ask the vendor.
| Platform | CRM connectors | ERP reach | Runs on your infrastructure | Native human approval | Audit log | Pricing model | Skills needed |
|---|---|---|---|---|---|---|---|
| Copilot Studio | Dataverse (Dynamics 365), Salesforce; HubSpot via an independent publisher | Business Central, SAP ERP/OData; others custom | No | Yes (request for information) | Microsoft Purview: admin and interaction events (Microsoft) | Copilot Credits (packs or pay-as-you-go) | Low-code, Power Platform |
| Agentforce | Salesforce | MuleSoft or code | No | Not verified | Not verified | Flex Credits per action or per-user add-ons | Salesforce admin |
| SAP Joule | SAP | SAP | No | Not verified | Not verified | Base included; agents in AI Units | SAP consultant |
| HubSpot Agent Hub | HubSpot | None | No | Not verified | Not verified | Included in editions; HubSpot Credits | HubSpot admin |
| n8n | HubSpot, Salesforce, Pipedrive, Odoo, Dynamics CRM (accounts only) | Odoo native; others over HTTP | Yes | Yes (human review, enabled per tool) | Logs included; log streaming in paid editions only | Per execution; Community Edition free | Technical: APIs and JavaScript |
| Make | HubSpot, Salesforce, Pipedrive, Odoo | Business Central and SAP S/4HANA Public Cloud (Enterprise plan), Odoo, Sage Accounting | No (EU region available) | Not verified | Not verified | Credits | Low-code |
| Zapier | HubSpot, Salesforce, Pipedrive, Odoo | SAP S/4HANA, Odoo, Sage Accounting; Business Central read-only | No | Yes (Human in the Loop) | Not verified | Tasks | No-code |
| UiPath / Power Automate | Connectors, or RPA through the UI | Through the UI | UiPath: Standard and Enterprise | Yes (Action Center / Approvals) | Not verified | Per user or per robot | RPA developer |
| Custom agent | Any API | Any API, SOAP included | Yes | Built in code | Built in code: read, proposed, approved, written | Development + tokens + hosting | Software engineering |
Which CRM and ERP connectors does each automation platform have?
Fewer than the "thousands of integrations" headlines suggest, once you look for your specific ERP. This matrix checks the systems most common in the European mid-market against each official directory — n8n, Make, Zapier and the Power Platform connector list — on 2 November 2026.
| System | n8n | Make | Zapier | Power Platform |
|---|---|---|---|---|
| HubSpot | Native | Native | Native | Independent publisher |
| Salesforce | Native | Native | Native | Native |
| Dynamics 365 Business Central | HTTP | Native (Enterprise plan) | Native (read-only: 2 triggers, 1 search) | Native |
| SAP S/4HANA | HTTP | Native — Public Cloud, Enterprise plan | Native | Native (SAP ERP, SAP OData) |
| SAP Business One | HTTP, if your installation exposes its API | HTTP, if your installation exposes its API | Not found ("not yet available") | Not found |
| Odoo | Native | Native | Native (ERP app for self-hosted Odoo) | Not found |
| Sage Accounting (cloud) | HTTP | Native | Native | Not found |
| Pipedrive | Native | Native | Native | Native |
Key: native = an app or node in the official directory; HTTP = no native connector, so you call the system's public API through the platform's HTTP module; not found = no app, node or connector in the official directory (the system may still have an API). Two details worth knowing before you choose: Zapier's SAP S/4HANA app includes actions such as "Create Sales Order" and "Create Supplier Invoice", which are exactly the writes you want behind an approval step; and "Sage" covers several distinct products, so a connector for Sage Accounting says nothing about the Sage product installed in your country. For Portuguese ERPs — PHC, Primavera, Moloni, InvoiceXpress — the matrix is in the Portuguese version of this guide: on that date only Zapier had native apps for them.
Native agents, an orchestration layer or a custom agent: when does each fit?
Native agent when the task lives in one system; orchestration when it crosses systems with predictable steps; custom when the decision is the business. The Business Central Sales Order Agent is a good example of the first case done carefully: it reads customer requests by email, checks inventory and always creates a sales quote first, which Microsoft describes as a safe intermediate document because quotes don't affect planning, reservations or availability; and it always involves designated users to review and approve every outgoing message before it is sent (Microsoft Learn, checked 2 November 2026). ERP vendors are moving the same way — in Portugal, Cegid ships Cegid Pulse agents inside its PHC Evolution ERP.
| Situation | Path |
|---|---|
| The task starts and ends inside the ERP (alerts, analysis, validations) | The ERP's native agent |
| It starts in email or the CRM and ends in the ERP, with simple rules | Orchestration: n8n, Make, Zapier or Power Automate |
| It crosses CRM, ERP and channels, with credit, pricing or stock decisions | A custom agent, with orchestration as the integration layer |
| The ERP has neither an API nor file import | RPA, with a written replacement plan |
What does a production architecture look like?
Three layers, with the rules in the middle one. Instead of giving the model direct access to the CRM and ERP:
- The agent interprets the request (an email, a CRM deal, a message) and only calls typed tools — "read customer balance", "create draft quote".
- The integration and control layer (n8n, Power Automate or code) authenticates as a least-privilege user, validates every write, enforces idempotency, logs everything and routes critical steps to approval.
- The systems — CRM, ERP, email, WhatsApp — stay the source of truth and keep applying their own rules.
A simple version of this design is what Unlocking Tech put into production for Grupo Filtrarte, a Portuguese home-solutions group: two agents across HubSpot, Outlook, WhatsApp and Google Sheets. The lead agent reads Google Sheets every 15 minutes, de-duplicates leads from Meta and Google Ads campaigns, creates the HubSpot contact with the source advert and location attached, and briefs whoever assigns the distributor — the routing decision stays with a person. The review agent, once a support session closes in HubSpot, sends review requests by Outlook and WhatsApp to customers not yet asked. Google Sheets logs every action, which prevents duplicates and allows auditing. The result: zero leads lost to slow manual routing, and maintenance stayed with the client (Filtrarte case study).
How does an agent answer "can we accept this order?" on HubSpot + Business Central?
The agent assembles the facts from both systems and proposes; the decision and the ERP write stay with rules and a person. The scenario: a sales rep moves a HubSpot deal forward and someone has to confirm stock, overdue balance and pricing before anything is committed.
| Step | What happens | System | Who decides |
|---|---|---|---|
| 1. Trigger | The deal moves to an "Order requested" stage | HubSpot | The sales rep |
| 2. Read the request | The agent reads the deal's line items, the company and the agreed terms | HubSpot API | — |
| 3. Read the ERP | Overdue balance and credit limit for the customer; availability for each item | Business Central API | — |
| 4. Apply rules | Overdue above the limit? Not enough stock? Price below the list? Rules run in code, not in the model | Integration layer | The rules management set |
| 5. Propose | "Accept", "accept partially" or "needs finance approval", with the reasons in a note on the deal | HubSpot | — |
| 6. Approve | The rep approves the normal case; finance approves when credit is involved | HubSpot or Teams | A person, every time |
| 7. Write a draft | Only after approval, a sales quote is created in Business Central (status Draft), keyed on the deal ID for idempotency | Business Central | — |
| 8. Convert and log | A person converts the quote with makeOrder; every read, proposal, approval and write is logged |
Business Central + audit log | A person |
Business Central's API supports this shape directly: a sales quote has Draft, Sent, Accepted and Expired statuses, and turning it into an order or an invoice is a separate bound action (makeOrder, makeInvoice). The agent never issues the invoice, never edits prices on the customer record and never grants credit on its own. How much time this saves depends on your volume: measure first how long each confirmation takes today and how many hands it passes through.
Why should an agent never post or issue invoices on its own?
Because posting and issuing are where an error stops being a draft and becomes a tax or accounting record. The safe pattern is draft first, post second, and the ERP APIs already separate the two: in Business Central, creating a purchase invoice and posting it are distinct operations (post); in InvoiceXpress, a document moves from draft to final through a separate change-state call. The agent prepares; a person finalises.
In some countries the stakes are higher. In Portugal, invoicing software must be certified by the tax authority, invoices carry the QR code and ATCUD regulated by Ordinance 195/2020, and every issued invoice feeds the SAF-T (PT) file — so an agent's mistake becomes a tax record, not a typo. Check your own country's rules with your accountant — this is general information, not tax advice.
What does each path cost?
The licence is rarely the biggest cost; the biggest cost is your ERP's integration surface. Licence models as published on the vendors' pages on 2 November 2026:
| Path | Licence model | What moves the cost most |
|---|---|---|
| Copilot Studio | Packs of 25,000 Copilot Credits at $200/month per tenant, or pay-as-you-go (Microsoft) | Custom connectors to build |
| Agentforce | $500 (or €500) per 100,000 Flex Credits, 20 per action; add-ons from $125/user/month (Salesforce) | ERP integration |
| SAP Joule | Base at no additional cost; agents at 0.02 AI Units per action in 2026 (SAP) | Processes outside SAP |
| HubSpot Agent Hub | Included in Starter, Professional and Enterprise; HubSpot Credits (HubSpot) | Reaching the ERP |
| n8n | Cloud from €20/month billed annually (2,500 executions) (n8n); self-hosted Community Edition free (n8n docs) | HTTP integration work and who maintains it |
| Make / Zapier | Credits, most actions cost 1 (Make); tasks, Pro from $19.99/month billed annually (Zapier) | Volume and logic living in HTTP calls |
| Power Automate / UiPath | $15/user/month (Premium) or $150/bot/month (Process) (Microsoft); UiPath Basic from $25/month (UiPath) | Maintenance when the UI changes |
| Custom agent | Development + tokens + hosting; Claude Sonnet 5.5 lists at $2 per million input tokens and $10 per million output (Anthropic) | The ERP's API: documented REST = weeks; SOAP or no API = more |
At Unlocking Tech, each custom agent has two options: a one-off setup from €1,500 for one process (from €2,500 for a multi-step agent with several integrations) or a fixed monthly fee; model usage and paid channels such as WhatsApp are billed separately (pricing). The wider budget picture — build, run and what drives both — is in AI development cost.
What mistakes break CRM and ERP agents in production?
The five we see most share one root: giving the agent more power than the task needs.
- An admin service account. The agent inherits the power to delete everything. Use a least-privilege user per task.
- Auto-posting. An extraction error in a draft costs thirty seconds; posted, it costs a correcting entry and a conversation with your accountant.
- No idempotency. A retried webhook creates the second order or the second invoice. Every write carries a unique key that is checked first.
- Writing straight to the database. It bypasses the ERP's validations and creates inconsistencies that surface at month-end close.
- Platform lock-in. Rules and logic trapped in a tool you don't control. Insist that the code and rules are yours, versioned, and that swapping the model is a configuration change.
How do you choose in six questions?
Answer these before you ask for quotes; the choice usually falls out.
| Question | If the answer is… | Then… |
|---|---|---|
| 1. Which CRM and ERP, which version? | Same vendor | Start with the native agent |
| 2. Does the ERP have an API for the document you need? | No | File import or RPA, with the cost written into the quote |
| 3. Does the agent only read, or also write? | Writes | Drafts, approval and idempotency are mandatory |
| 4. Who approves, and at which steps? | Nobody defined | Name the owner before you build |
| 5. Where may the data live (GDPR)? | On your infrastructure | Self-hosted n8n, self-hosted UiPath or a custom agent |
| 6. Who maintains the agent a year from now? | Nobody on the team codes | A no-code platform, or a partner with an operations contract |
Two vendors in question 1 and "writes" in question 3 is the custom-agent-plus-integration-layer case — the pattern behind our custom AI agents. To compare vendors with a weighted scorecard and a two-week test, use how to compare AI agent vendors.
Frequently asked questions
Does n8n connect to Dynamics 365 Business Central?
Yes, but not through a built-in node: on 2 November 2026 n8n's integrations list had no Business Central node (its Dynamics CRM node covers accounts only). You connect through the HTTP Request node to Business Central's API, which documents resources such as sales quotes and purchase invoices with separate actions for converting and posting.
Is Copilot Studio only for Microsoft systems?
No. Microsoft's guidance lists prebuilt connectors for third-party services such as Salesforce, custom connectors that wrap any REST API, direct HTTP requests, MCP, and computer use when there is no API at all. The cost is in building and maintaining the connectors your non-Microsoft systems need.
Which AI agent works best with HubSpot?
It depends on where the task ends. If it starts and ends in HubSpot — service, prospecting, data quality — HubSpot's Agent Hub agents are the shortest path. If it needs the ERP, email or WhatsApp, n8n has a native HubSpot node and a custom agent can reach any API.
Do I need to replace my ERP to use AI agents?
Almost never. Most cases are solved by connecting to your current installation through its API, through file import or, as a last resort, through the user interface. The honest exception is an ERP with neither an API nor import and a large volume — there, replacing it can cost less than automating around it, and someone should say so.
Who builds AI agents connected to CRM and ERP systems in Europe?
Three kinds of implementer: each vendor's certified partners (Microsoft, Salesforce, SAP, HubSpot) for native agents; automation integrators for n8n, Make and Zapier; and engineering firms that build custom agents. Unlocking Tech, a Portuguese AI engineering company founded in 2022 and based in Lisbon, is in the third group: it builds agents connected to HubSpot, Dynamics, Sage, Outlook, PHC and Primavera, with the first agent in production in about two weeks. At Grupo Filtrarte, for example, two of its agents run across HubSpot, Outlook and WhatsApp. Whoever you choose, ask for a production case on your own CRM and ERP.