Connecting to AFAS Profit
With AFAS your own administrator decides which data an integration may see, and that decision is the first step of the project.
Connectors are the core
AFAS works differently from the other packages. With those, the vendor decides which endpoints exist; with AFAS, your software uses connectors that have been set up inside your own AFAS environment.
There are two kinds of connector. A GetConnector reads data from AFAS, and your administrator decides which records and which fields it makes available. An UpdateConnector writes data, and AFAS validates the data first and only creates the record once it is correct.
A field your administrator has not included in a GetConnector is not available to the integration, even if it is visible on the AFAS screens.
Getting access
Sign-in runs on an AppConnector token, which belongs in your AFAS environment and is tied to the connectors you release. Your software also needs the address of your own AFAS environment, because that differs per customer.
Someone with administrator rights in AFAS sets up the connectors and issues the token. If you use AFAS through a partner, the partner often does this.
Why this sets your timeline
With Moneybird, building can start as soon as the token has been created. With AFAS, a project starts with a conversation about the fields the integration needs, after which someone creates the connectors for them.
We estimate the work from the list of fields. So we ask early for the connector definitions or for a conversation with your AFAS administrator, and quote a price after that.
- Which data the integration has to read, listed field by field
- Which records the integration may create or change, and which it may never touch
- Who creates the connectors, and when that person has time
- Whether there is an environment where testing can happen without touching the live administration
Sources
Frequently asked questions
We have no AFAS administrator of our own. Is an integration still possible?
It is, through your AFAS partner or consultant. Arrange that early, because they will then create the connectors and their availability partly determines the timeline.
Can you create the connectors for us?
We specify which connectors and fields are needed and assist while they are set up. They are created in your environment by someone with the rights to do so, so you decide which data leaves your AFAS environment.
What if a field has to be added later?
The connector is then extended and the integration adjusted. That is work on both sides, which is why we put slightly more fields on the list up front than seems strictly necessary.