ZPZapier
Every receipt,
a trigger.
Webhooks fire on receipt.completed. Point Zapier at the URL, pick what to do with each receipt, and let it run. No code, no parsing, no scraping the dashboard.
Why this integration
The parts that make
Zapier feel native.
Webhook fires on completion
receipt.completed event posted to your Zap webhook the moment extraction finishes. Includes the full structured payload, not a placeholder.
HMAC-signed by default
Every delivery includes an X-Receipts-Signature header. Zapier verifies it via a built-in step, so spoofed payloads bounce.
Reliable delivery
Retried with exponential backoff. Failures land in the dashboard's delivery log with status codes and response bodies for debugging.
How it connects
- 01Receipt arrivesDashboard or API
- 02AI extractionVision model reads it
- 03Webhook firesPOST to your Zap URL
- 04Your Zap runsSheets, Notion, Slack, anything
zapier.jsonJSON
// Zap receives this payload
{
"event": "receipt.completed",
"receipt": {
"id": "rcpt_2yK3pQ",
"merchant": { "name": "Brew & Butter" },
"total": 27.13,
"currency": "USD",
"items": [/* … */]
}
}FAQ
About the
Zapier integration.
Do I need to write code?
No. Zapier handles the webhook receive step natively. Pick the receipt fields you want and point them at any downstream Zap action.
Can I trigger different Zaps for different receipts?
Yes. Use Zapier filters on receipt fields like merchant name, category, or total amount to route receipts to different actions.
What if my Zap fails?
We retry with exponential backoff. Persistent failures show up in the dashboard's delivery log so you can see what went wrong and replay manually.
Is there a Zapier app instead of just webhooks?
A native Zapier app is on the roadmap. For now, the webhook integration is fast to set up and works with any Zapier plan.
Other integrations