Connect Make, Zapier and n8n to Exact Online

Automation platforms do not sign in themselves; they use the MCP address with a bearer token. That turns your administration into a building block for any scenario, from invoice checks to weekly overviews.

How to set up the connection

1. Open your connection page in the app and pick Make or Zapier in the setup guide.
2. Copy the MCP URL and the bearer token. No token yet? Generate one with a single click.
3. Create an MCP connection in your platform with that URL, and send the token as the Authorization header: Bearer followed by the token.

The token and the administration

The token belongs to exactly one administration, so your scenario always works in the right environment. Treat it like a password. If you regenerate it, the old token stops working and you update your scenarios with the new one.

Limit what an automation can do

An automation does not ask for approval in a chat; it does exactly what the scenario says. So choose deliberately which tools are enabled for the connection: whatever is off cannot be invoked through the token either. How that works is in Team, access and audit log.

Example scenarios

• Check every incoming invoice and report possible duplicates in your team channel.
• Every Monday, put the open items in a spreadsheet for the stand-up.
• Create a task when a customer exceeds their credit limit.

Also for n8n and other MCP clients

n8n and other MCP clients with token support use the same URL and the same token. The setup guide spells out Make and Zapier; the fields are the same two everywhere.