Integrations
Connect, test and monitor freight exchange, telematics, accounting, email, routing, geocoding, sanctions list and e-invoicing.
Para:Administrador2 min de lectura
Catalogue and controls
The catalogue is grouped by type (freight exchange, telematics, accounting, email, customs, routing & geocoding, e-invoicing) and shows the status available, beta or planned. Planned providers cannot be set up yet.
- Active/inactive switch, configure, documentation.
- Test connection → shows OK with the response time, or the failure reason.
- Last sync and last error for monitoring.
- Remove deletes the stored credentials.
Credentials
Credentials are stored encrypted and only shown masked (••••••••). Fields left empty or masked keep the stored value. Some fields fall back to a server setting when empty (the form tells you which one).
Providers at a glance
| Provider | Type, status | Key fields / note |
|---|---|---|
| TIMOCOM | Freight exchange, available | API key, API secret, company ID; without access a demo adapter is used |
| Trans.eu | Freight exchange, planned | Client ID, client secret |
| Webfleet | Telematics, available | Account, username, password, API key; match vehicles via telematics provider/ID |
| Samsara | Telematics, beta | API token, base URL (EU by default) |
| Demo telematics | Telematics, available | Simulates vehicle movements along tours |
| BMD NTCS | Accounting, available | Company number, receivables account (20000), revenue account (4000); file-based export |
| DATEV | Accounting, available | Consultant number, client number, receivables account (10000), revenue account (8400) |
| IMAP/SMTP mailbox | Email, available | See the mailbox setup article |
| OSRM | Routing, available | Base URL; the public demo server is not meant for production |
| Nominatim | Geocoding, available | Base URL, contact email (required by the terms of use); 1 request/s |
| EU sanctions list | Customs, available | List URL (required), match threshold (0.85) |
| HERE, ATLAS, Peppol | Planned | Peppol: the e-invoice XML is already generated; sending will follow |
Telematics and geocoding
- Telematics positions are synchronised every 2 minutes (if enabled on the server). Each vehicle needs a telematics ID.
- Geocoding results are cached for 30 days. If coordinates are missing, use geocoding on the partner.
Artículos relacionados
- Setting up the mailbox (IMAP/SMTP)How emails reach the AI inbox and how replies, quotes and invoices go out – including server variables and multi-tenant operation.
- Carrier compliance and sanctions screeningKeep track of carrier licence and insurance expiry, screen against the EU sanctions list and assess hits.
- Webhooks and API keysNotify third-party systems about events via webhooks and connect them with least-privilege API keys.
- Accounting export (BMD/DATEV)Export invoices, debtors and creditors as CSV for BMD NTCS or DATEV – including account mapping and import tips.