What usually breaks at the document step
- ✕
Your Zap reaches the 'create document' step and suddenly needs five apps glued together.
- ✕
You build a Lambda that wraps docxtemplater and pray it never OOMs.
- ✕
You pay for a Make operation per row and watch the quota evaporate on busy days.
- ✕
Every new client means reinventing the document-generation tail of the automation.
How it works
- 1
Create a job
Pick a template, define merge tags, save. Every job gets its own webhook URL.
- 2
POST from anywhere
Zapier, Make, n8n, your backend, a CRM action — POST a JSON payload to the URL.
- 3
Document appears
SheetMergy merges, stores, optionally emails, and returns a link — all in one request.
The webhook step that actually works
Just HTTPS + JSON
No SDK to install. Works from every automation platform and every programming language.
Signed payloads
Optional HMAC signature header so you can verify requests really came from your automation.
Sync or async
Get the document back in the response, or poll a run status endpoint. Your choice per request.
Chain with delivery
Let SheetMergy email the document to the recipient in the payload — no extra steps in your automation.
Idempotency keys
Safe retries. Same idempotency key + payload = same output, no double-charging.
One webhook per job
Isolate workflows per client or per team without sharing credentials.
Webhook questions
- Can Zapier call a SheetMergy webhook?
- Yes — use Zapier's native 'Webhooks by Zapier' POST action. Same for Make, n8n, Pipedream, or your own backend.
- Does it reply with the generated document?
- In sync mode, the response includes the signed URL and metadata. In async mode, poll the run ID or register a callback.
- Rate limits?
- Dashboard shows your per-key rate limits. Bursts are allowed; sustained high throughput needs a higher tier.
- What's the cost per invocation?
- 1 credit per document, 1 per email. No per-request fee.