Integrations
A signed payload to anywhere.
When a document is signed, completed, or declined, we POST a signed JSON to your endpoint. Hook it into Zapier, Make.com, Slack, or your own service.
Webhooks done right.
Eight event types. HMAC-SHA256 signed payloads. Per-endpoint retry logs. Recipe cards in the dashboard for the three most common targets — Zapier, Make.com, Slack — so you're not reading docs.
8
Event types
HMAC-SHA256
On every payload
1-click
Retry failed deliveries
Recipes
Zapier, Make.com, Slack — paste-and-go.
Each integration gets its own recipe card in the dashboard with the exact paste pattern. Zapier: paste into a "Webhooks by Zapier" trigger. Make.com: into a Custom webhook trigger. Slack: incoming webhook URL. No docs-reading required.
- Zapier recipe card with exact instructions
- Make.com recipe with the right trigger module
- Slack incoming webhook for #signed-doc channels
- "See docs" link on every recipe
Integrations
Connect FusionDocs to other apps — paste a URL.
Zapier
Paste this URL into a "Webhooks by Zapier" trigger to start a Zap whenever something happens.
See Zapier docs
Make.com
Add a "Custom webhook" trigger module to your scenario and paste in the URL.
See Make.com docs
Slack
Use a Slack incoming webhook URL to post notifications into a channel.
See Slack docs
Eight events
You pick which fire, per endpoint.
Sent, signed, declined, voided, completed, approval-requested, approved, rejected. Each endpoint subscribes to whichever events it cares about. No noise — the channel that wants signed events doesn't also get sent events.
- document.sent / signed / declined / voided / completed
- document.approval_requested / approved / rejected
- HMAC-SHA256 signature on every payload
- Per-endpoint event subscription
document.signed
12ms · 3s ago
document.completed
8ms · 18s ago
document.signed
14ms · 1m ago
document.sent
120ms · 4m ago
document.sent
11ms · 6m ago
Delivery log
See every attempt. Retry the failed ones.
Each endpoint shows recent deliveries with HTTP status, response time, response body. If the receiving end was down, retry from the dashboard with one click. If you rotated the signing secret, replay deliveries to test the new value.
- Recent deliveries with HTTP status + timing
- One-click retry on a failed delivery
- Signing secret rotation with re-issue
- Test ping to verify the endpoint is up
document.signed
12ms · 3s ago
document.completed
8ms · 18s ago
document.signed
14ms · 1m ago
document.sent
120ms · 4m ago
document.sent
11ms · 6m ago
Wire FusionDocs to your stack in five minutes.
Free. No card. No demo call. We get out of your way.