<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog: epilot integration in practice</title><description>Articles on epilot webhooks, the API, Quarkus mappers, operations and code ownership. For IT leads at grid operators and municipal utilities.</description><link>https://epilot-berater.de/en/blog/</link><language>en</language><atom:link href="https://epilot-berater.de/en/rss.xml" rel="self" type="application/rss+xml"/><item><title>An epilot integration project at a grid operator</title><link>https://epilot-berater.de/en/blog/epilot-integration-project-grid-operators/</link><guid isPermaLink="true">https://epilot-berater.de/en/blog/epilot-integration-project-grid-operators/</guid><description>How an epilot integration project at a grid operator runs, from the intro call to quote, interfaces and operation, plus answers for procurement and legal teams.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Connecting ERP, billing and third-party systems to epilot</title><link>https://epilot-berater.de/en/blog/connecting-systems-to-epilot/</link><guid isPermaLink="true">https://epilot-berater.de/en/blog/connecting-systems-to-epilot/</guid><description>epilot integration explained: when the Integration Toolkit, Batch API, webhooks or public APIs fit, and when dedicated middleware connects your other systems.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate></item><item><title>epilot API: providing data from other systems via REST</title><link>https://epilot-berater.de/en/blog/rest-api-data-for-epilot/</link><guid isPermaLink="true">https://epilot-berater.de/en/blog/rest-api-data-for-epilot/</guid><description>How the epilot API and a dedicated REST API bring data from CRMs and databases into epilot: pull vs push, OpenAPI contracts, rate limits, caching and GDPR.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Mappers between epilot and third-party systems with Quarkus</title><link>https://epilot-berater.de/en/blog/epilot-mapper-quarkus/</link><guid isPermaLink="true">https://epilot-berater.de/en/blog/epilot-mapper-quarkus/</guid><description>A Quarkus mapper for epilot: how it receives webhooks, converts data for third-party systems, calls them via REST and handles failures in operation.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Processing epilot webhooks securely</title><link>https://epilot-berater.de/en/blog/epilot-webhooks-processing-securely/</link><guid isPermaLink="true">https://epilot-berater.de/en/blog/epilot-webhooks-processing-securely/</guid><description>How to process an epilot webhook securely: verify the signature, check the timestamp, respond fast, handle retries and replays, and make processing idempotent.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Running epilot integrations: monitoring, errors, maintenance</title><link>https://epilot-berater.de/en/blog/epilot-integration-operations/</link><guid isPermaLink="true">https://epilot-berater.de/en/blog/epilot-integration-operations/</guid><description>epilot integration maintenance after go-live: monitoring mappers, handling errors with replay, rate limits, updates, and who looks after interfaces long term.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate></item><item><title>When is low-code in epilot no longer enough?</title><link>https://epilot-berater.de/en/blog/epilot-low-code-limits/</link><guid isPermaLink="true">https://epilot-berater.de/en/blog/epilot-low-code-limits/</guid><description>epilot low-code goes a long way. How grid operators and utilities spot when third-party systems, data transformations or events need classic development.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Who owns the integration code?</title><link>https://epilot-berater.de/en/blog/integration-code-ownership/</link><guid isPermaLink="true">https://epilot-berater.de/en/blog/integration-code-ownership/</guid><description>The code of an epilot interface belongs to the client. What grid operators should know about repositories, handover, maintenance contracts and independence.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate></item></channel></rss>