Connect JTL-Wawi
Connect JTL-Wawi to SimpliServ via the REST API: establish the connection, approve the app registration, sync settings, live updates via a Wawi workflow.
→ Open the JTL connector in SimpliServ
With the JTL-Wawi connector you connect your local JTL-Wawi instance to SimpliServ via its REST API. Customers, items, orders, invoices and stock are synced – depending on the setting – in one or both directions. JTL remains the leading system for master data, prices, taxes and stock; SimpliServ adds service, tasks and a customer portal.
You'll find the connector under Administration → Organisation → Connectors. Open the JTL-Wawi tile there. Access to the connectors page requires the View settings permission (admin.settings.view).
Prerequisites
- A running JTL-Wawi installation with its REST API enabled.
- The Wawi host must be reachable from the SimpliServ cloud (open the API port or provide it via VPN). The default port is
5883. - A Wawi user with rights to approve applications under Admin → Applications.
Enable the REST API in JTL-Wawi
Turn on the REST API
In JTL-Wawi, open the file JTL-Wawi.exe.config (admin) and enable the REST API on a port the SimpliServ cloud can reach. The default is 5883.
Check reachability
Make sure the base URL responds from outside, e.g. http://wawi.example.local:5883/api/eazybusiness.
Establish the connection
Open the connector
Go to Administration → Organisation → Connectors and open the JTL-Wawi tile. Switch to the Configuration tab.
Enter the base URL
Under Base URL, enter the address of your Wawi REST API (e.g. http://wawi.example.local:5883/api/eazybusiness). The Authorization scheme usually stays on Wawi (older versions partly use Bearer). Click Save connection.
Test the connection
Click Test connection. SimpliServ checks whether the host responds and shows – once detected – the Wawi version in the connection block ("JTL Wawi instance") in the Configuration tab.
Approve the app registration
JTL-Wawi only issues an API key once a Wawi user has approved the external app.
Start the registration
Click Start registration. SimpliServ sends a registration request to your Wawi.
Approve in JTL-Wawi
Open JTL-Wawi → Admin → Applications and approve the pending request.
The key is taken over
The page checks the status automatically every few seconds (or via Check status now). Once the app is approved, the API key is saved and the status switches to Connected.
If the request is rejected in Wawi, SimpliServ shows Registration rejected. You can then send a new attempt via Restart registration.
Set the sync settings
Under Sync settings you set per area whether and in which direction it syncs. You choose the direction per row: Inbound (only pull from JTL), Outbound (only push to JTL) or Both.
Available areas:
- Customers – customer master records and addresses
- Suppliers – supplier master records (imported as supplier customers)
- Items – item master data, prices, identifiers and weights
- Orders – order headers, billing and shipping addresses and line items
- Invoices – invoice headers and line items from JTL
- Payments – payment transactions for JTL invoices and orders
- Stock – stock and reservations per warehouse
- Serial numbers – item serial numbers per warehouse
- Reference data – customer groups, payment & shipping methods, manufacturers, warehouses, categories, tax classes
For Customers, Items and Orders there's additionally the option Sync new entries automatically: if active, every newly created record is automatically marked as sync-enabled and transferred to JTL. Existing records keep their individual setting. Click Save settings after changes.
Trigger a sync
In the Synchronization section you start syncs on demand. Bulk syncs run in the background.
- Incremental sync – syncs only changed records. Also runs automatically on a schedule (every few minutes).
- Full sync – reloads all entities. Can take a long time and must be confirmed.
- Refresh reference data – updates customer groups, methods, tax classes, warehouses and categories.
You see the progress in the Overview tab under Sync status: per entity the total count and the timestamp of the last sync.
Live updates via a Wawi workflow
So that changes in Wawi reach SimpliServ immediately (instead of only at the next scheduled sync), you set up workflows in Wawi that call a webhook URL. You find the area in the Installation tab of the JTL tile.
Show the webhook URL
Click Show webhook URL. The URL contains your tenant identifier and is shown only once for security reasons – copy it immediately. Via Regenerate you can rotate it later (the old URL becomes invalid immediately).
Create workflows
Open JTL-Wawi → Administration → Workflows and create a workflow per suggested row – matching the object (customer, item, order) and trigger (e.g. "Was created", "Was changed", "Was deleted", "Stock was changed"). SimpliServ shows a ready-made URL to copy for each workflow.
Set up a web-request action
Add a web request action with method POST per workflow and enter the copied URL. Leave the header and body empty.
Insert variables via the picker
Insert the {{ … }} variables in the URL via the Wawi variable picker – never type them manually. A wrong path is rejected. Then Save and activate.
Wawi 2.0.3 can't accept order line items via the REST API. SimpliServ therefore writes them into a dedicated Wawi field; an additional workflow creates them as real line items on push. The exact guide (a dedicated text field SimpliServ Positionen under Admin → Custom fields → Sales order plus an "Execute" action on the "Was created" and "Was changed" triggers) is shown by the connector in the Order line items section.
Sync individual records
Even without a global auto-sync you can connect individual customers or items specifically. On the detail view of a contact or product you find the JTL Wawi card with the Auto-sync to JTL toggle. There you also see the status (Synced, Syncing, Sync failed, Disabled or No connection), the JTL ID and the last sync.
Disconnect the connection
In the connection block of the JTL tile (the Configuration tab) you disconnect via Disconnect. This removes the stored API key and the sync cursors. You should then disable the Wawi workflows in Wawi.
Related topics
How is this guide?
Connect WooCommerce
Connect a WooCommerce store to SimpliServ via the REST API: create API keys, choose sync settings, import products and set up webhooks.
Connect VeloConnect
Connect suppliers for purchasing via the VeloConnect standard: store dealer credentials, test the connection, fetch prices and availability, search the catalog and submit orders.