API integration · connecting existing systems
AFAS integration: Profit as the source of truth for your portal, shop or app
AFAS Profit is the leading system for contacts, projects, HR and finance in many Dutch organisations. An integration lets your portal, shop, planning or work-order app read straight from it and write back safely, without anyone retyping data. AFAS has a clear model for that: GetConnectors to read, UpdateConnectors to write, and tokens you grant per integration. OmniTechs builds on that model, with recorded fields, error handling and a test in the AFAS test environment before anything goes live.
Door Sina Sadegh Esfahani · Practice page by OmniTechs in Groningen; amounts follow the current price contract · Beoordeeld op .
What does a AFAS integration cost?
An integration between AFAS and one other system with a documented API is agreed in advance as a fixed amount; the calculator on the API integration main page shows the starting price for your combination and number of data types. After that the quote is fixed, no hours afterwards.
If one of the systems is poorly documented, documents or emails have to be read first, or it is unclear which system leads, we start with a Solution Sprint of €1,250 excl. VAT: we test the connection for real and you receive a fixed build price. Recurring costs are limited to hosting of the integration layer and monitoring in a Care plan; licences for the systems themselves are paid directly to their vendors.
- Standard integration: fixed price after the calculator and a short intake
- Uncertain combination: Solution Sprint €1,250 excl. VAT, then a fixed quote
- Recurring: hosting of the integration layer and monitoring via Care
- First assessment free, within one working day
What moves to and from AFAS Profit?
Reading goes through GetConnectors defined by an AFAS administrator; writing through UpdateConnectors with fixed fields. Both define what an integration may do.
| Data | Direction | Watch out for |
|---|---|---|
| Contacts and contact persons | AFAS → portal or CRM, and back | Which side leads per field; address change in the portal or in Profit? |
| Projects, job costing and hours | Work order or time tracking → AFAS | Project code and cost type must exist; hours per employee |
| Sales orders and invoices | Shop or portal → AFAS | Item code and VAT; shipping costs on the right ledger |
| Employees and absence | AFAS HR → planning or roster | Only the fields needed; privacy by design |
| Documents and files | Portal → AFAS dossier | File size and dossier type |
AFAS Connect, partner connector or custom?
For many systems a partner connector exists in the AFAS partner network, and integration platforms offer standard connectors on subscription. Choose those when your data flow is standard. Custom work pays off when you have your own portal, shop or app that must talk to Profit, when you want to validate or enrich data before it lands in Profit, or when you want to control exactly which fields leave the system.
How an AFAS integration works technically
In AFAS Profit the administrator creates an App Connector and grants a token per integration; that token defines which GetConnectors may be read and which UpdateConnectors written. Reading and writing is possible through REST with JSON or SOAP with XML; we use REST where possible. Large data sets are fetched in parts and filtered on changed records. Every integration is tested first in your organisation's AFAS test environment, with real structure but without consequences for your administration.
What you prepare
An AFAS administrator who can create the App Connector and the required Get- and UpdateConnectors, access to the test environment, and a decision per data type on which system leads. With the free mapping tool on the main page you line up the fields of your portal or app next to the AFAS fields.
How it runs
Day 1: free assessment of the requested data flows and the available connectors. Week 1: field mapping and agreements on leading systems and error handling. Weeks 2 to 4: build, test in the test environment, go-live per data flow. Then monitoring through a Care plan or handover to your own administrators.
What to expect
- First assessment within one working day, free
- Field mapping as a document you can check yourself, with the free mapping tool on the main page
- Tests with real data in a test administration before the integration goes live
- Error messages someone on your team understands, with an owner and a retry
- Code, mapping and documentation are yours; maintenance via Care or in-house
Frequently asked questions
What are GetConnectors and UpdateConnectors?
GetConnectors are read views on Profit data defined by the AFAS administrator; UpdateConnectors are fixed write interfaces for contacts, orders, hours, dossiers and more. An integration uses only the connectors granted to its token.
How secure is an AFAS integration?
Access runs through a token that may use only the granted connectors; we store tokens encrypted outside the code and agree a rotation schedule. Data travels encrypted and we log what was read and written without personal data in the logs.
Can you connect AFAS to HubSpot, Salesforce or a work-order app?
Yes, as long as the other system has an API. Contacts and projects from Profit to the CRM or app, and hours, orders or statuses back: that is the usual shape.
How long does an AFAS integration take?
Allow two to four weeks per data flow, including the test in the AFAS test environment. Speed often depends on how quickly the connectors are ready in Profit.
Can you take over or repair an existing AFAS integration?
Yes. After a free review of code, tokens and connectors you hear what repair or takeover costs.
Which system must read from or write to AFAS Profit?
Send the name of your portal, shop or app and the data that must move. Within one working day you hear which connectors are needed and what the integration costs.