How do I connect my tuning tools?

Workspace → Connections is where you store the master credentials for your tuning tool. Once a connection is saved, verified and enabled, an encrypted ECU (engine control unit) read that a dealer uploads to your workspace is decrypted automatically, and the file you deliver can be re-encrypted for that dealer's slave tool before it leaves. Connections is also where the evc.de reseller account and the accounting integration live.

Which tools can I connect?

One tuning tool is supported on the Connections page today: Autotuner. It appears as a card whether or not you have saved anything, so an empty Connections page is normal rather than broken. Other vendors are not on the page — if you work with a tool that is not listed, keep handling its files by hand; nothing about ordering or delivery depends on a connection existing.

How do I connect Autotuner?

Two fields on the Autotuner card, both taken from your own master tool:

1. Master Tool ID — the identifier of your master tool.
2. Master API key — the key that master tool issues.

Press Save & verify. The credentials are checked immediately: the badge on the card turns to Verified when they work, and you get "Saved, but the keys did not verify" when they do not. Keys are encrypted at rest and never shown back to you, so the fields go blank after saving and the button becomes Replace keys.

Saving is not the last step. Verifying a connection does not switch it on — a verified connection sits idle until you press Enable. That is deliberate: nothing starts touching customer files until you say so.

What do the badges on the card mean?

• Not configured — no credentials saved yet.
• Not verified — credentials are stored but have never been checked successfully.
• Verified — the keys work, but automation is off. Press Enable.
• Enabled — the keys work and automation is running. This is the working state.
• Invalid keys — the last check failed. The reason is shown on the card, and enabling is switched off automatically so bad keys can never leave decryption armed. Fix the keys with Replace keys, or press Test connection if you believe the failure was temporary.
• Not available yet — the integration itself isn't switched on for this environment, whatever your keys say. Your credentials are still saved, but nothing is verified against them and enabling stays off. Open a support ticket naming the vendor if you see this in production.

Test connection re-checks the stored keys at any time and updates the badge.

What does an enabled connection actually do?

An enabled Autotuner connection changes two moments in the order.

On upload. Every ECU file uploaded to the platform is probed for tool encryption — that probe is keyless and runs whether or not you have a connection. When the file is an encrypted container for a vendor you have enabled, and the order belongs to your workspace, the file is decrypted with your master credentials and the clear read is stored alongside the original. The original upload is never overwritten, and the order page then serves you the decrypted copy to work from.

On delivery. When the read carried a slave reference, the delivery dialog on the order page offers a checkbox: Re-encrypt with Autotuner before delivery, so the dealer receives a slave file. Tick it and the finished file is encrypted for that slave before the dealer is notified — the dealer's "file ready" notification only fires once the slave file is ready. Leave it unchecked to deliver the file exactly as you produced it.

Two limits are worth knowing. Orders routed to the platform pool are never auto-decrypted — only orders that belong to your own workspace are. And an encrypted upload with no enabled connection never blocks the order: it stays encrypted, you are notified, and you handle it the way you did before.

What else is on the Connections page?

• WinOLS (evc.de) — your reseller account, so buyers can top up their WinOLS credits from your portal. This card only appears on plans that include WinOLS reselling. See winols-credit-reselling.
• Accounting — connect Exact Online so the invoices you issue are pushed into your bookkeeping. Choose your region (Netherlands, Belgium or Germany), optionally tick Also import my existing invoices, and press Connect Exact Online; you are sent to Exact to authorise and returned here. Afterwards set your Administration (division) number. The card then shows region, administration and VAT (value added tax) mapping — Enable stays unavailable until VAT reads auto-mapped, because pushing invoices with unmapped VAT codes would corrupt your books.
• Ad leads — send leads from Meta, LinkedIn, Google Ads or a no-code tool like Zapier straight into your portal inbox. See the next section.

How do I send leads from Meta, LinkedIn or Google Ads here?

The Ad leads card turns a lead from an ad platform's own lead-generation form into a conversation in your portal inbox — answered by the AI agent exactly like a website enquiry, with an alert email the moment it arrives.

Press Activate. This mints one API key and reveals two ready-made webhook URLs — the key is the only credential in this whole feature, and it authenticates every source, not just the two URLs shown beside it.

Which URL (or the key on its own) you use depends only on what the sending tool can configure:

Meta and LinkedIn do not have their own direct webhook you can paste a URL into — connect the ad account to a Zapier or Make zap first (their New Lead / New Lead Gen Form Response triggers), then have that zap POST to the Meta, LinkedIn, manual, Zapier/Make URL above. Google Ads is the exception: its lead-form asset has a Webhook integration screen built in, so paste the Google Ads lead form URL there directly, and the API key into its separate Webhook key field — send Google's own test lead from that screen before turning the form live; test leads are accepted but never stored, so testing never litters your inbox.

Pause stops accepting leads without disturbing anything already configured — resuming later needs no reconfiguration in Zapier, Make or Google Ads. Rotate replaces the key everywhere it is used: every tool still holding the old one stops working until you paste the new key in, so only rotate if you believe the old key leaked.

"No leads received yet" under the key is normal right after activating — it updates the first time a real lead (or a platform's own test lead, for Google Ads) reaches the endpoint.

If a connection still will not work

Autotuner won't verify. Check the credentials in your own tool's portal first — the Master Tool ID and API key are issued there, and a key that was regenerated on the tool side stops working here without any warning. If the keys are definitely current and the badge still says Invalid keys, open a support ticket with the vendor (Autotuner), the exact error text shown on the card, and the time you last pressed Test connection.

A lead isn't landing in your inbox. Confirm the card still reads Active, not Paused. Then check the sending tool's own side: in Zapier or Make, open the zap's run history for an error on the webhook step; on Google Ads' Webhook integration screen, use Send test lead and confirm it succeeds there before assuming the portal side is at fault. If the tool reports success but nothing appears here, open a support ticket with the lead source, roughly when it was sent, and (for Google Ads) whether it was a real or test lead.