Connect AFAS Profit to your webshop, CRM and other systems

What you connect with AFAS Profit

• Keep business relations and contact persons in sync with your CRM
• Webshop orders as a sales order or invoice in Profit
• Items and prices from Profit to your webshop
• Pass new employees and leave on to planning or other HR systems
• Collect data from Profit for reporting and dashboards

How the integration works

AFAS works with connectors that are set up in Profit and called with a token for an app connector. Together with you and your AFAS administrator, I agree which connectors are needed, with exactly the fields the integration uses. In n8n, an HTTP step talks to those connectors. Error handling, logging and a failure email in plain language are included as standard.

Facts about the AFAS Profit API

Checked on 2 November 2026 against the official documentation. Limits, prices and versions change; the source is listed per row.

Fact	What the documentation says	Source
Authentication	A token in the header (AfasToken, Base64) that belongs to an app connector. The app connector determines which GetConnectors and UpdateConnectors are reachable. TLS 1.2 is mandatory.	AFAS Help: REST API
Token lifetime	No expiry in the documentation; a token stays usable until the administrator deletes it.	AFAS Help: Token
Rate limits	No fixed number of calls; AFAS Online applies a fair-use policy. There are hard limits: a maximum of 75 MB per call, URLs up to 2,048 characters and a timeout after about 15 minutes.	AFAS Help: REST API
Webhooks	Only for dossier items and workflows. The message says that something changed, not what; you fetch the data afterwards with a GetConnector. Signed with X-Profit-Signature-256.	AFAS Help: Webhooks
Test environment	Separate test and acceptance environments (resttest and restaccept in the URL). Demo environments only for licence holders.	AFAS Help: API
Version	No version number in the URL. REST and SOAP can do the same; the FileConnector only through REST.	AFAS Help: REST
Objects	GetConnectors (self-defined data views with filters and paging), UpdateConnectors (insert, update, delete), ReportConnector, FileConnector and metainfo.	AFAS Help: GetConnector
n8n	No built-in node and no community node found; the integration runs through an HTTP step in n8n.	n8n documentation

What you need on your side

• An AFAS administrator who can create an app connector with a token and set up the required GetConnectors and UpdateConnectors
• A test environment (resttest) to build against before production is touched
• Per connector a list of exactly the fields the integration reads or writes
• A fixed key per relation (for example the debtor number) to prevent duplicate relations

Where it often goes wrong, and how I prevent it

• Free fields: every Profit environment has its own fields. I record them in advance, so an integration does not quietly fill an empty field.
• Permissions that are too broad: a connector only gets access to what the integration actually reads or writes.
• Duplicate relations: without a fixed key, duplicate relations appear. I match on a fixed number, not on name.
• Testing on production: AFAS has separate environments. The integration runs against a test environment first, where that is possible.

In practice

The pattern is the same as in the WooCommerce and Exact Online integration for Mercabilis: one source per data item, the other systems follow, and an alert for every deviation. Read the case →

What it costs

I build an AFAS Profit integration as one scoped process for a fixed price, from €750. Maintenance and monitoring are a monthly fee: n8n management from €250 per month, server management €145 per server. In the free assessment we work out your process. All prices and what is included →

What I do not do

• I do not configure AFAS Profit itself; your AFAS administrator creates the connectors and permissions, based on my specification.
• I do not pull complete tables; a GetConnector always gets filters and paging.
• I use webhooks on dossiers and workflows only as a signal, never as the source of the data.

Frequently asked questions about connecting AFAS Profit

Does n8n have a built-in AFAS integration?

No. n8n has no official AFAS node. I connect AFAS through the AFAS connectors with an HTTP step in n8n. That is custom work, but it is fully readable and exportable, and it runs on your own server.

Does anything need to be set up in AFAS itself?

Yes. Your AFAS administrator sets up the connectors and an app connector with a token. I specify in advance exactly which connectors and fields are needed, so no more permissions are granted than necessary.

What happens if AFAS changes something?

The integration is monitored. If a field changes or a connector returns an error, you get an alert instead of silent failures. With maintenance, I adapt the integration.

Does AFAS limit API calls?

There is no fixed number; AFAS Online applies a fair-use policy. Hard limits do apply, such as 75 MB per call and a timeout after about a quarter of an hour. That is why the integration fetches data in batches, with filters and sorting.

Can AFAS notify me when something changes?

Only for dossier items and workflows. AFAS then sends a message that something has changed, without the content; the integration fetches the data itself afterwards. For relations, items and orders the integration checks at fixed intervals.