All about jortt
Jortt: Get customers from Jortt
Get customers from Jortt, companies and private persons with address, e-mail address and VAT number, and send them to another system.
Updated November 9, 2026
This flow gets customers from Jortt and sends them to another application, for example a CRM system or a webshop. Use it when Jortt is the leading system for your customer data.
How it works
- APIcenter gets the customers from Jortt in batches. Each run processes the number of customers you set in Amount to process and continues where the previous run stopped. When APIcenter reaches the end of the customer list, it starts again at the beginning.
- A customer that is a company is passed on with the company name as company and the contact person as name. For a private person, the name is passed on as the name of the customer.
- The date of birth is passed on as a date.
- The e-mail address identifies the customer in the activity of this flow.
- By default, APIcenter passes on the name, company, e-mail address, phone number, address, date of birth, chamber of commerce number, VAT number, website, reference and the Jortt customer ID. You can add more fields under Data mapping, such as the invoice language, the payment term, extra information and the e-mail addresses in cc.
What you need first
- Jortt is connected. See Connect Jortt 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. See Data mapping.
- Is a customer missing in the target system? Check whether the customer has an e-mail address in Jortt and look in the activity of the flow.
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.
Enable URL Encoding of data in the endpoints of the source application
General flow settingEncodes values in request URLs when this flow retrieves data from Jortt. These requests only contain page numbers, invoice statuses and Jortt customer ids, so you rarely need this. Only works when Enable URL encoding of data in endpoints is on as well. Off by default.
Enable URL Encoding of data in the endpoints of the target application
General flow settingEnable URL encoding of data in endpoints
General flow settingUse administration mapping table
General flow settingThis setting has no effect for Jortt. The data that APIcenter exchanges with Jortt has no administration field, so there is nothing to map. Leave it off (default).
What to do with a value that cannot be mapped using the mapping table
General flow settingDecides what happens when the administration mapping table has no row for a value from the incoming data.
- Use default (default): APIcenter uses Default administration id, if that default is switched on; otherwise the field stays empty.
- Use value: the original value is passed on unchanged.
- Ignore value: the field stays empty.
This has no effect for Jortt, because the data that APIcenter exchanges with Jortt has no administration field.
Notifications Email address
NotificationsNotifications Slack webhook
NotificationsNotifications frequency
NotificationsReceive Notifications
NotificationsAmount to process
Run behaviourThe maximum number of customers or invoices APIcenter retrieves from Jortt per run. The default is 10. A higher number clears a backlog faster but makes each run take longer. In the Get Payment flow this number does not limit how many payments are retrieved in a run.
Last execution time
Run behaviourMaximum number of pages to retrieve
Run behaviourThe maximum number of pages APIcenter reads when it repeats a request to get a list in several pages. The Jortt flows read one page of customers or invoices per run (see Offset), so this setting has no practical effect for Jortt. The default is 20; you do not need to change it.
Offset
Run behaviourAPIcenter keeps track of where the flow stopped in the list of customers or invoices in Jortt, and uses this number to continue in the next run. APIcenter updates it automatically after each run, so you normally do not change it. The default is 0, which starts at the beginning of the list. Only change it when APIcenter support asks you to.
Run at specific times
Run behaviourThis setting has no effect for Jortt. APIcenter retrieves customers and paid invoices from Jortt page by page (see Offset and Amount to process) and does not filter on a date. Changing the date does not make the flow retrieve older or newer records, so leave it at its default.
Use page size
Run behaviourThe number of records per page when APIcenter requests a list in several pages. The requests that the Jortt flows send for customers and invoices do not contain a page size, so this setting has no practical effect for Jortt. The default is 50; you do not need to change it.