Integrations
What Druma connects to
Each card says how far it has been tested. Only LocTracker runs on a live fleet today; a card waiting for access cannot be switched on until the provider grants it.
Transporeon
- Does
- Built to read Transporeon transport orders into the Intake queue and send status updates and proof of delivery back.
- Tested so far
- Tested on recorded examples
- You bring
- Your Transporeon access.
Client API
- Does
- Imports orders from a client's own system through a versioned REST API and sends status events back by webhook.
- Tested so far
- Druma's own feature, tested on Druma's test system
- You bring
- An API key from Settings and a developer on the client's side.
Email orders
- Does
- Reads order emails sent to your order inbox and drafts each order, with a confidence level per field, for a planner to confirm.
- Tested so far
- Druma's own feature, tested on Druma's test system
- You bring
- A forwarding rule in your mail system.
- Note
- Orders can also be confirmed automatically, under rules you set and Druma's own checks such as an exact client match.
Outlook add-in
- Does
- Reads an order email inside Outlook and turns it into a draft order.
- Tested so far
- Druma's own feature, tested on Druma's test system
- You bring
- Microsoft 365 and permission to install the add-in.
- Note
- You install it from a file Druma provides, not from Microsoft's add-in store.
Browser extension
- Does
- Reads a load on a Bursa de Transport page and sends it to Druma as a draft order.
- Tested so far
- Druma's own feature, tested on Druma's test system
- You bring
- A Chrome-based browser.
- Note
- You download it from Druma, not from the Chrome Web Store.
Timocom
- Does
- Will read Timocom loads near a truck's offload point, and send your offers on them, once access opens.
- Tested so far
- Waiting for Timocom to grant access
- You bring
- When access opens: your Timocom contract, and the API client ID and secret your Timocom account manager issues.
Trans.eu
- Does
- Will read Trans.eu freight near a truck's offload point, and send offers from each planner's own login, once access opens.
- Tested so far
- Waiting for Trans.eu to grant access
- You bring
- When access opens: an API client ID and secret from your Trans.eu account manager, and a Trans.eu login per planner.
ANAF e-Factura
- Does
- Built to create each invoice as e-Factura XML, upload it to ANAF and show ANAF's answer, linking a credit note to its invoice.
- Tested so far
- Checked with ANAF's own validator
- You bring
- Your ANAF authorisation for e-Factura.
- Note
- ANAF's public validator accepted all eight of Druma's sample invoices in October 2026; nothing has been filed through ANAF yet.
Peppol
- Does
- Sends a Belgian company's invoices over Peppol through Recommand and shows whether each one was delivered.
- Tested so far
- Tested against Recommand's test environment
- You bring
- Your KBO number and BE VAT number, entered on the Peppol card in Settings; Druma then registers you on Peppol, and you complete Recommand's identity check from the verification link shown there.
- Note
- Druma has not yet sent an invoice to Peppol production. It only sends; receiving needs a separate solution.
KSeF
- Does
- Sends a Polish VAT entity's invoices to KSeF and keeps the KSeF number on each invoice.
- Tested so far
- Tested against KSeF's test environment
- You bring
- A KSeF token or certificate for the Polish entity.
- Note
- Druma has not yet sent an invoice to KSeF production. Druma switches it on per company.
SAGA
- Does
- Built to export invoices and payments in SAGA's import format (.dbf files).
- Tested so far
- Tested on sample files
- You bring
- Your SAGA installation to import the file.
WinMENTOR
- Does
- Built to export invoices as the pipe-separated text file of WinMENTOR's text-file import.
- Tested so far
- Tested on sample files
- You bring
- Your WinMENTOR installation to import the file.
JPK_V7M
- Does
- Exports the JPK_V7M(3) Polish VAT records file for a Polish billing entity.
- Tested so far
- Checked against the official file schema
- You bring
- A Polish billing entity with its VAT number.
ANAF e-Transport
- Does
- Built to read the UIT your client declared, check it with ANAF, watch its expiry and report the vehicle change to ANAF.
- Tested so far
- Built to the ANAF documentation
- You bring
- The UIT from your client and your ANAF e-Transport access.
- Note
- Your client declares the load; Druma never files the declaration. Positions for ANAF come from your telematics provider or the ANAF app.
eCMR
- Does
- Issues the eCMR, collects sender, driver and consignee signatures on screen, and seals the PDF (PAdES).
- Tested so far
- Druma's own feature, tested on Druma's test system
- You bring
- Nothing to install. Unlimited eCMRs are included on every truck plan.
- Note
- The production seal certificate is set up before eCMR is switched on for you during onboarding.
Webfleet, Geotab, Samsara, Scania, Volvo and Frotcom are built to each provider's documentation and have not yet read a customer's account; VDO and Webeye wait on the providers' partner approval. Once a connector reads your account, its positions show on the planning board and the client tracking page. LocTracker shows driver hours on the truck's board card and the live map today. Webfleet is built to supply them too, and Scania and Volvo the driver's working state.
Webfleet
- Does
- Built to read each driver's remaining driving time and each truck's position through WEBFLEET.connect.
- Tested so far
- Built to the Webfleet documentation
- You bring
- A Webfleet account with WEBFLEET.connect access. The API key comes from Webfleet support.
Geotab
- Does
- Built to read truck positions from a MyGeotab service account, without tachograph data.
- Tested so far
- Built to the Geotab documentation
- You bring
- A MyGeotab service account with view-only rights.
Samsara
- Does
- Built to read GPS positions from a Samsara account, without tachograph data.
- Tested so far
- Built to the Samsara documentation
- You bring
- A Samsara API token that can read vehicle statistics.
Scania rFMS
- Does
- Built to read each Scania truck's position and the driver's working state over rFMS.
- Tested so far
- Built to the Scania documentation
- You bring
- Your Scania fleet account with rFMS access.
Volvo rFMS
- Does
- Built to read each Volvo truck's position and the driver's working state over rFMS.
- Tested so far
- Built to the Volvo Trucks documentation
- You bring
- Your Volvo Trucks account with rFMS access.
Frotcom
- Does
- Built to read each vehicle's position from your Frotcom account.
- Tested so far
- Built to the Frotcom documentation
- You bring
- Your Frotcom login, with API access enabled by Frotcom support or your reseller.
Continental VDO
- Does
- Will read truck positions from your VDO fleet account once access opens.
- Tested so far
- Waiting for Continental to grant access
- You bring
- When access opens: the Client ID and secret Continental issues under a partner agreement.
Webeye / Eurowag
- Does
- Will read truck positions from your Webeye account once access opens.
- Tested so far
- Waiting for Eurowag to grant access
- You bring
- When access opens: a username and secret you generate in Eurowag's selfcare portal, with Druma approved as a connected system.
LocTracker
- Does
- Reads positions, fuel level, driver hours and the CMR and delivery photos drivers take on the LocTracker tablet, and sends nothing back.
- Tested so far
- Runs in production on a live fleet
- You bring
- A read-only API user from LocTracker.
Mapon
- Does
- Built to read the set point and actual temperature of each reefer unit into the order.
- Tested so far
- Built to the Mapon documentation
- You bring
- Your Mapon account with API access.
Thermo King TracKing
- Does
- Will read the temperature of Thermo King units into the order once access opens.
- Tested so far
- Waiting for Thermo King to grant access
- You bring
- When access opens: your Thermo King TracKing account, with Druma admitted as a TracKing partner.
Carrier Lynx Fleet
- Does
- Will read the temperature of Carrier Transicold units through Lynx Fleet once access opens.
- Tested so far
- Waiting for Carrier to grant access
- You bring
- When access opens: your Carrier Lynx Fleet account, with Druma holding Carrier's Lynx Fleet API toolkit.
Orbcomm
- Does
- Built to read reefer temperatures from the Orbcomm platform into the order.
- Tested so far
- Built to the Orbcomm documentation
- You bring
- API credentials for your Orbcomm platform account.
- Note
- The reefer data paths still have to be confirmed with a customer's Orbcomm account token.
Fuel-card statements
- Does
- Built to import CSV or Excel statements from DKV, UTA, AS24, Shell, TotalEnergies, BP, Circle K, Eurowag, WEG, MOL and E100, split tolls from diesel and match each line to a plate.
- Tested so far
- Tested on sample files
- You bring
- The statement file from your card provider.
- Note
- These layouts have not yet been checked against a real export.
Bank statements and payment emails
- Does
- Built to read payment emails from BRD, BCR, Raiffeisen, UniCredit and ING and to import CAMT.053, MT940 and CODA statements, matching each payment to an open invoice.
- Tested so far
- Tested on sample files
- You bring
- A statement file, or a forwarding rule for the bank's emails. Your bank login is never needed.
- Note
- These email layouts have not yet been checked against a real email, and a payment that does not match waits for review.
CHEP and Paki statements
- Does
- Built to import CHEP and Paki statements and compare each line with your pallet movements.
- Tested so far
- Tested on sample files
- You bring
- The statement file from the pallet provider.
- Note
- You can open a dispute from any line that does not match.
WhatsApp Business
- Does
- Built to send and read driver messages, including proof-of-delivery and CMR photos, through your WhatsApp Business account.
- Tested so far
- Built to the Meta documentation
- You bring
- Your own Meta WhatsApp Business account.
Slack, Teams and Telegram
- Does
- Built to send Druma notifications to a Slack or Microsoft Teams channel, or to a Telegram chat through a bot.
- Tested so far
- Built to the Slack, Teams and Telegram documentation
- You bring
- A webhook address for Slack or Teams. For Telegram, a bot token and the chat ID.
MCP server
- Does
- Reads your Druma data into your own AI assistant, such as Claude, over MCP, with the rights of the person who connects it.
- Tested so far
- Druma's own feature, tested on Druma's test system
- You bring
- Your own AI subscription.
- Note
- Tested end to end with Claude; other MCP clients, such as ChatGPT, connect the same way. It stays off until your company switches it on.
Druma AI with your own key
- Does
- Sends Druma AI's requests to your AI provider on your company's own key, and that provider bills you directly.
- Tested so far
- Druma's own feature, tested on Druma's test system
- You bring
- An API key from your AI provider.
- Note
- Whoever saves the key confirms that Druma data will be sent to that provider.
Druma itself relies on several outside services, for example PTV for routing, tolls and arrival times, and HERE for addresses. Full sub-processor list
Connectors built on request
A company admin can request a connector in Settings, and Druma answers there whether it will build it. If you have a paid subscription and other Druma customers can use the connector too, there is no development fee. The other system needs an API or a documented file exchange, and outside fees are paid at cost.
Your own developer can link a system to Druma's public API and webhooks straight away, with an API key a company admin creates in Settings. No request is needed.
Example: asking for a fuel-card connector
A fleet manager wants each fuel-card transaction in Druma next to the trip it belongs to, without waiting for the monthly statement. Druma can import the statement files but has no live link to any card provider, so this would be a new connector.
The company admin opens Settings > Integrations, clicks "Request an integration", picks the Fuel card category, names the provider and writes how the company would use the link. The request shows as Received, then as Planned, Planned for later (accepted, but not in the current work) or Not planned.
If the request is planned, the company admin opens an API account with the card provider so the connector can be built and tested against it. Once it is finished, you enter your provider credentials on its card. Some providers, such as Continental VDO, Eurowag, Thermo King and Carrier, also need Druma to hold their partner access or tools.
The same form has categories for telematics and GPS, freight exchanges, TMS and transport platforms, accounting, and Other. There is no connector yet for ERP systems such as SAP; one can be requested under Other.
The terms
- Druma decides how an integration built on request is built and owns it, and may offer it to other customers without sharing your data with them. During a trial there is no obligation to build one.
- An integration for your company alone, or one that needs software written only for you, is not covered by your subscription. It is offered only under a separate written agreement.
- If an integration you asked for costs Druma money, such as a provider's API, licence or data fees, certificates or other external charges, you pay for it, invoiced separately at the cost actually incurred. If the expected amount is more than EUR 250, or another amount set in your Order Form, you are told the amount in writing first.
- You obtain the logins, licences and permissions the other system requires, keep them valid, and arrange the access Druma needs to build and test the integration. Druma is not responsible for changes in, or interruptions of, the other system.
- There is no delivery date until Druma confirms one in writing.
The binding wording is in Annex 2 of your Order Form.
Request it in Settings > Integrations