All about jortt
Jortt: Get sales orders from Jortt
Get invoices from Jortt as sales orders, with the customer details, and send them to another system.
Updated November 9, 2026
This flow gets invoices from Jortt and passes them on as sales orders to another application. Use it when invoices are created in Jortt and another system has to process them.
How it works
- APIcenter gets the invoices from Jortt in batches. Each run processes the number you set in Amount to process.
- You choose which invoices APIcenter gets with Use the Jortt order state to retrieve. Jortt has two states: draft and sent. By default, APIcenter gets sent invoices. Leave the state empty to get both. Select one state: when you select more, APIcenter only uses the first.
- For each invoice, APIcenter also gets the customer from Jortt and adds the customer details to the invoice. When an invoice has no customer, it fails with the message that no customer ID was found on the order.
- An invoice that APIcenter already passed on is not passed on again. With Pass through orders based on states switched on, APIcenter passes on the invoice again when its state has changed since, for example from draft to sent.
- APIcenter works through the invoices on creation date.
- For a customer that is a company, the contact person is passed on as the name and the company name as company.
What the data mapping covers
By default, APIcenter passes on the invoice ID, the invoice number as order number, the reference as order reference, the status, the creation date, the currency, the language and the customer: ID, name, company, e-mail address, phone number, billing address, date of birth, chamber of commerce number, VAT number, website and reference.
The order lines and amounts are not mapped by default. Does the other application need them? Then add them under Data mapping. See Data mapping.
What you need first
- Jortt is connected. See Connect Jortt to APIcenter.
- The other application of the integration can receive sales orders.
Tips
- Do you need to filter invoices further, for example on status? See Filter options.
- Is an invoice missing in the target system? Check its state in Jortt and the state you selected for this 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.
Normally APIcenter passes on a Jortt invoice only once: an invoice that was already processed is skipped in later runs. When on, an invoice that was already processed is passed on again if it comes in with a status it did not have before, so status changes also reach the other application. This is useful when you leave Use the Jortt order state to retrieve empty to retrieve both draft and sent invoices. Off by default.
Chooses which Jortt invoices the Get Sales Order flow retrieves, based on their status in Jortt. Jortt has two statuses: Sent (default) and draft. Choose one status, or leave the field empty to retrieve both.
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 behaviourUse 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.