The e-invoice automation is a webhook-triggered, single-send automation that delivers an invoice PDF over WhatsApp as a document-header template message, immediately on receiving the webhook.
Note: Multiple E-Invoice automations per business are allowed
E-invoice automation setup
Create the automation → Automations → Notifications → New Automation → E-Invoice Webhook.
Copy the webhook URL and paste it into your invoicing/ERP/tax system as its outbound webhook target.
Send one real payload so the schema is captured.
Map the phone number field from the captured payload tree, plus a country-code source if numbers arrive in local format.
Pick the template.
Map the PDF document header from the Webhook response.
Map the custom fields from the template to the correct data from the webhook response. And click Save.
Configure response handling for open-text replies and delayed responses.
Write a specific reply for each quick reply button you added in the template and choose an action (assign to team, close or trigger API call)
Save and Publish.
Worth knowing: the mandatory-header guard checks only that a mapping exists and reads from the payload — it does not verify PDF-ness. The PDF requirement is enforced by the UI at setup and by the MIME whitelist at runtime, and that whitelist also permits images and MP4. So a caller bypassing the UI could legitimately ship a PNG invoice.
The e-invoice automation use cases
The core one: any system that generates a customer-facing PDF and can call a webhook, delivering it to WhatsApp instead of (or alongside) email.
Tax e-invoicing compliance — ZATCA (Saudi), Egypt's ETA, and similar regimes require issuing a compliant invoice to the buyer. Once your e-invoicing provider stamps and returns the PDF, this pushes it to WhatsApp, where open rates far exceed email.
ERP / accounting invoice delivery — invoice issued in your ERP → webhook → customer's WhatsApp within seconds.
POS and retail receipts — digital receipt instead of a printed one at checkout.
Payment confirmations and receipts — payment gateway settles → receipt PDF delivered.
Credit notes, refund documents, statements of account — the same mechanism, different document; filter branches let one automation handle several document types with different templates.
Subscription / recurring billing — each billing cycle's invoice pushed automatically.
Reporting
Same statistics screen as the plain Webhook type. The CSV export gives five Yes/No columns per contact: Started, Completed, Clicked, Open-text reply, No Reply, plus the timestamps.
To download an e-invoice automation report, follow these steps:
From Automations > Notification Automations, choose the e-invoice automation
Click Export Delivery Report, choose the time filter and click Export
Gotchas to plan around
The PDF link must survive until the webhook is processed. Short-lived signed URLs that expire in seconds will fail the download.
Authenticated PDF URLs won't work — we fetch them with no credentials.
Reply branches are quick-reply buttons on the template, so plan the template's buttons before wiring per-button actions.