Connect Pipedrive to Lexware Office
For Pipedrive and Lexware Office, formerly called lexoffice, there is a ready-made app from PD Experts. It creates a quote, order confirmation and invoice from a deal and reports the payment status back. For many sales teams, that is enough. A custom integration pays off with your own rules for document chains, products and contacts, or when no event may get lost.
Which data flows between Pipedrive and Lexware Office
- Deal in a specific stage becomes a quote in Lexware Office on stage change
- Won deal becomes an order confirmation or invoice referencing the quote on status change
- Products on the deal become document line items with quantity, discount and tax rate with every document
- Organization and person become a Lexware contact with address, VAT ID and contact person with the first document
- Document number and link are shown in the deal immediately
- Payment status from Lexware becomes a field on the deal and starts follow-up tasks on every change
What already exists for Pipedrive and Lexware Office
The Lexware integration from PD Experts is listed in the Pipedrive marketplace and on Lexware's partner page. According to the partner page, it creates quotes, order confirmations and e-invoices from a deal. Master data such as company, address, VAT ID and contact person move to Lexware Office with the first document, and the deal's products become line items. Payment status and a link to the document come back. According to the page, the requirements are a Pipedrive plan of Essential or higher, a Lexware Office account with access to the Public API and administrator rights in both systems.
Automation services such as MindCloud and SyncSpider also offer workflows between the two systems. If your process follows the standard “deal won, write invoice”, use the app from PD Experts.
Where the standard stops
Webhooks can fail
Pipedrive counts a delivery as failed after ten seconds without a response and then retries three times. If errors pile up, Pipedrive blocks the webhook for 30 minutes. According to the documentation, events in that period are lost. After three days without success, the webhook is deleted.
Daily budget for API calls
Pipedrive grants each company a daily budget of API tokens, depending on plan and seats. Expensive calls such as search use more. A sync that rereads everything every hour can use up the budget.
Document chains with special cases
Partial invoices, several invoices for one deal or credit notes after a partial return do not follow the simple flow. Rules are needed for which document follows which.
Organization or person as recipient
In Pipedrive, a deal can be linked to an organization, a person or both. Lexware Office needs one unambiguous invoice recipient.
Deals in foreign currency
Pipedrive keeps deals in any currency. According to the documentation, the Lexware API always returns payment information in euros. For deals in francs or dollars, the return path of the payment status needs a clear rule.
How we build the integration
Pipedrive side: We register version 2 webhooks for changes to deals. Each notification contains the new state and the previous values of the changed fields. This lets us recognize a real stage change and not react to every edit. Delivery is protected with Basic Auth. Because notifications are lost during a block, a lean reconciliation of recently changed deals runs in addition. It uses the cheaper endpoints of API version 2.
Lexware side: We create quote, order confirmation and invoice through the Public API. Follow-up documents reference their predecessor, so the document chain stays visible in Lexware Office. Before creating contacts, we search by name, number or email. We learn about payment changes through an event subscription and write them into a field on the deal. There, Pipedrive automations can trigger tasks or reminders.
Operation: Both sides have request limits, and a queue keeps within them. Errors appear in the log and as a note on the deal. More about monitoring under Operation and monitoring.
Process and price range
In the free 30-minute integration check, we go through pipeline, document types and products. Within 3 working days, you receive a fixed-price offer. For the connection from Pipedrive to Lexware Office, the entry price is €1,900 net, usually implemented in 2 to 4 weeks. How we work is described under Process and pricing.
Frequently asked questions
What can the app from PD Experts do?
According to the provider, it creates quotes, order confirmations and e-invoices from deals, takes over master data and products and returns the payment status to Pipedrive. For standard processes, it is a good choice.
Which Pipedrive plan do I need?
For the partner app, the provider names Essential or higher. For a custom integration, the API budget of your plan matters most.
What happens if a webhook fails?
Our additional reconciliation finds deals whose notification is missing and creates the document afterwards. The stored link between deal and document prevents duplicate documents.
Can a quote later become the invoice?
Yes. The invoice references the quote or the order confirmation, the line items are carried over and adjusted if needed.
Can several invoices be created for one deal?
Yes, for example a down payment invoice and a final invoice. We define in advance which stage or field triggers which invoice, and store all document numbers on the deal.
Sources
- Lexware Partner: Pipedrive by PD Experts, retrieved on 20 Oct 2026
- Pipedrive Marketplace: Lexware Schnittstelle von PD Experts, retrieved on 20 Oct 2026
- MindCloud: Pipedrive and Lexware Office, retrieved on 20 Oct 2026
- SyncSpider: Pipedrive and lexoffice, retrieved on 20 Oct 2026
- Pipedrive Developers: Guide for Webhooks v2, retrieved on 20 Oct 2026
- Pipedrive Developers: Rate limiting, retrieved on 20 Oct 2026
- Lexware API Documentation (Contacts, Quotations, Invoices, Event Subscriptions), retrieved on 20 Oct 2026
Related
Lexware Office (lexoffice)
lexoffice is now Lexware Office: Public API, webhooks, e-invoicing and limits at a glance.
HubSpot → Lexware Office
Won HubSpot deals become invoices in Lexware Office (formerly lexoffice): what apps can do, where the return path is missing and what custom code looks like.
Shopware → Lexware Office
Shopware invoices as vouchers in Lexware Office (formerly lexoffice): which plugins exist, where backfills and sales channels fall short, how we build it.
CRM connection
From won deal to invoice without a second entry, payment status back to the CRM.
