Connect systems · Understand the evidence
AI automation integrations for European businesses
Which connection could fit your workflow? This directory brings together publicly documented routes and questions to resolve before a proposal.
Directory updated:
In short
Listing a product does not imply partner certification or a ready-made integration. A linked vendor source describes a function, interface or route to investigate. We first check whether the available access supports the required operation.
Your software is not listed? Industry software, for example for hotels, insurance brokers or workshops, is not checked here yet. Tell us the product and version. We check the documented access and reply in writing. office@modernagents.ai
Three different levels of evidence
- Documented route
- A linked vendor source describes a function, interface or route to investigate. All 15 entries currently have only this status.
- Tested configuration
- Requires a dated test naming version, licence, operation, cases and outcome. No entry in this directory currently claims this status.
- Delivered integration
- Requires documented acceptance and permission to publish the specific scope. No entry in this directory currently claims this status.
01 / 15
Microsoft Outlook
Status: documented route
Source checked:
- Integration route
- The n8n connector documents operations for messages, calendars, events and contacts. Name the exact operation in the proposal.
- Access and licence checks
- Suitable Microsoft account, registered access and required permissions. Authorise shared mailboxes and calendars separately.
- Limitations and pending test
- A connector does not cover every Graph feature. Sending, calendar changes and access to other mailboxes each need separate review.
02 / 15
Google Calendar
Status: documented route
Source checked:
- Integration route
- n8n documents availability queries and creating, retrieving, updating and deleting events.
- Access and licence checks
- Approved Google calendar, suitable OAuth permissions, booking rules and time zone. Limit write access to required calendars.
- Limitations and pending test
- An available slot is not yet a binding booking. Concurrent requests, retries and cancellations need their own rules and tests.
03 / 15
Microsoft Teams
Status: documented route
Source checked:
- Integration route
- The connector describes messaging, team and channel operations. A notification and an actual approval step are different functions.
- Access and licence checks
- Teams in the relevant tenant, suitable Microsoft permissions and an approved application. Identify the target channel and responsible people.
- Limitations and pending test
- Sending a message does not prove human approval. The workflow must record identity, response and expiry.
04 / 15
Microsoft SharePoint
Status: documented route
Source checked:
- Integration route
- n8n documents file and list operations. A knowledge assistant additionally needs source selection, refresh and permission checks.
- Access and licence checks
- SharePoint access, appropriate site and library permissions, approved application and defined content. Check Microsoft licensing first.
- Limitations and pending test
- File access alone does not preserve user permissions in a search index. Test deletion, permission withdrawal and metadata access separately.
05 / 15
HubSpot
Status: documented route
Source checked:
- Integration route
- The n8n connector documents contacts, companies, deals and tickets among other resources. Connect only agreed objects and actions.
- Access and licence checks
- Suitable HubSpot account scope, application access and required scopes. Define properties, associations and allowed write actions first.
- Limitations and pending test
- Plan, API limits and endpoint changes remain relevant. Updating a contact requires reliable matching and a duplicate rule.
06 / 15
Pipedrive
Status: documented route
Source checked:
- Integration route
- n8n documents activities, deals, leads, notes and organisations among other resources. A callback task is a bounded use case to evaluate.
- Access and licence checks
- Pipedrive account, approved API access and permission for target objects. Define owner, pipeline and required fields.
- Limitations and pending test
- Compare available node operations with the current API version. Redelivery must not create a second task or lead.
07 / 15
itellicoAI
Status: documented route
Source checked:
- Integration route
- The vendor describes call handling, callback and appointment requests, and forwarding. Its product page describes forwarding an existing number.
- Access and licence checks
- Suitable plan, phone-number country, carrier forwarding and approved conversation flow. Clarify calendar and CRM requirements for each destination.
- Limitations and pending test
- Direct calendar booking is scoped per customer. Vendor claims are not a modernagents acceptance test or blanket compatibility commitment.
08 / 15
3CX
Status: documented route
Source checked:
- Integration route
- 3CX documents configuring its own AI agents with OpenAI. Native functionality and forwarding to external services are separate options.
- Access and licence checks
- Supported version and edition, suitable licence, administrator access and any required model account; verify before quoting.
- Limitations and pending test
- The guide does not prove a tested connection between 3CX and every external phone assistant. Test return handoff, routing and concurrent calls separately.
09 / 15
n8n
Status: documented route
Source checked:
- Integration route
- n8n offers cloud and self-hosted deployment routes for workflows. Connectors and HTTP requests connect specifically approved systems.
- Access and licence checks
- Check deployment model, edition and licence terms, plus access to connected services. Assign operations, backups and updates for self-hosting.
- Limitations and pending test
- Self-hosting does not make external model or SaaS calls local. Node documentation does not prove a complete process tested by modernagents.
10 / 15
BMD
Status: documented route
Source checked:
- Integration route
- BMD publishes technical documentation. Agree the specific exchange route for documents or master data with the supporting BMD partner.
- Access and licence checks
- Identify product, version, licensed modules and approved import or export format. Obtain partner confirmation and a test client before implementation.
- Limitations and pending test
- The public documentation index does not prove universal BMD API access. This is therefore a route to investigate, not a ready-made connector.
11 / 15
DATEV
Status: documented route
Source checked:
- Integration route
- DATEV describes data services for different transfers. Match the service to the destination; documents and posting data are different transfers.
- Access and licence checks
- Suitable data service, ordering or activation, DATEV permissions and agreement with the firm. Check access requirements for the specific service.
- Limitations and pending test
- No general write access to all DATEV products. Successful transfer replaces neither professional approval nor checks in the target system.
12 / 15
bexio
Status: documented route
Source checked:
- Integration route
- bexio offers a development route for custom API integrations and a separate marketplace route. The vendor page links API documentation and a sandbox.
- Access and licence checks
- Use the designated sandbox for development. Confirm endpoints, permissions and production account scope for the required records.
- Limitations and pending test
- API availability alone proves neither the desired posting operation nor a finished modernagents integration. Plan client separation and duplicate checks.
13 / 15
Abacus / AbaConnect
Status: documented route
Source checked:
- Integration route
- Abacus publishes AbaConnect documentation by version and application. Select mapping for the installed system.
- Access and licence checks
- Confirm installed version, application, interface permissions and required licences with the Abacus partner. Define test data and acknowledgements.
- Limitations and pending test
- A documented interface is not a universal REST connector. Direction, fields and acknowledgements depend on version and application.
14 / 15
Xero
Status: documented route
Source checked:
- Integration route
- Xero invoice processing can use the documented n8n contact and invoice operations. For supplier invoices, confirm the payable type and required state before choosing an operation.
- Access and licence checks
- Approved Xero application access to the correct organisation, suitable account entitlements and a reviewed mapping for supplier, currency, tax codes and document state. Authorise the exact write after review.
- Limitations and pending test
- Keep unapproved extracted values outside the accounting write path. Test unknown suppliers, duplicate invoices, wrong-organisation selection and uncertain acknowledgements. No live Xero acceptance test is claimed here.
15 / 15
QuickBooks Online
Status: documented route
Source checked:
- Integration route
- For automated supplier invoice processing, n8n documents Bill and Vendor operations in QuickBooks Online. Customer Invoice operations are a different resource; identify the intended transaction first.
- Access and licence checks
- A supported QuickBooks Online country edition and company, approved API access, suitable plan and object permissions, and reviewed vendor, currency and account mappings. Keep approval before the permitted write.
- Limitations and pending test
- Do not assume that another product’s draft state or approval model carries over. Test required fields, duplicates and recovery in the intended company. Bill creation does not authorise payment, and no live QuickBooks acceptance test is claimed here.
Your software is not listed? We check it in writing
Tell us the system, version, country, intended action and approval route. You get a written assessment of whether and how the connection works, usually within one working day and without a call first. We first check whether the available access supports the required operation. Please do not send credentials or confidential documents.
Robert Van Ysendyck · Founder & Managing Director