All about AFAS

AFAS: Get customers from AFAS

Get customers and contact persons from AFAS, with address, e-mail address and VAT number, and send them to another system.

Updated November 9, 2026

This flow gets customers (debtors, debiteuren) from AFAS and sends them to another application, for example a B2B webshop or a CRM system. Use it when AFAS is the leading system for your customer data.

How it works

  • APIcenter gets the name, address and e-mail address of the contact and the company, and the VAT number. You can add more fields under Data mapping.
  • APIcenter filters on the modification date in AFAS: each run gets the customers that changed since the last run.
  • You choose the date from which APIcenter starts getting customers. Set it back in time to send customers again.
  • By default, APIcenter gets customers with their contacts. With a setting you choose whether you get customers, contacts or both.
  • Is a customer linked to a discount group (kortingsgroep) instead of a price list? Then APIcenter passes on the discount group as the price list of that customer.

What you need first

  • The connector set is imported and the GetConnectors are added to the App connector. See Connect AFAS to APIcenter.
  • The other application of the integration can receive customers.

Tips

  • Do you need customer fields that are not sent by default? Add them under Data mapping.
  • Is a customer missing in the target system? Check whether the customer changed after the date set for this flow. If not, set the date back.

You find all settings for this flow below, each with its own explanation.

Settings

The settings you see in the dashboard, with what each one does.

Determines what the Get Customer flow retrieves from AFAS.

  • Customers and Contacts: debtors (debiteuren) together with their contact persons (contactpersonen). This is the AFAS default.
  • Only Customers: debtors, without their contact persons.
  • Only Contacts: only the contact persons.

Use administration mapping table

General flow setting

Notifications frequency

Notifications

Receive Notifications

Notifications

Amount to process

Run behaviour

Last execution time

Run behaviour

Offset

Run behaviour

Run at specific times

Run behaviour

The date and time from which the flow retrieves records from AFAS, based on their modification date: for example articles, debtors, price lists, stock, payments or shipments that changed after this moment. APIcenter moves this date forward automatically after each run, so the next run continues where the last one stopped. Set it back in time to send records again, for example all stock after a stock count, because AFAS does not register a stock correction as a change. For AFAS the default is 1 January 2025.

Use page size

Run behaviour

Still need help?

Ask the support assistant in your dashboard or create a support ticket.

Go to support