Documenso Webhooks EventsSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-08Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: documenso-webhooks-events description: 'Implement Documenso webhook configuration and event handling. Use when setting up webhook endpoints, handling document events, or implementing real-time notifications for document signing. Trigger with phrases like "documenso webhook", "documenso events", "document completed webhook", "signing notification". ' allowed-tools: Read, Write, Edit, Bash(curl:*), Bash(ngrok:*) version: 1.14.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - documenso - webhooks compatibility: Designed for Claude Code --- # Documenso Webhooks & Events ## Output - A verified signed, idempotent webhook/event path with redacted observability and recovery ownership. - A receipt that records correlation ID, environment, event type, lifecycle result, and safe retry decision. ## Examples Validate the callback signature before parsing the event, deduplicate with an opaque event ID, acknowledge within the documented timeout, and log only state/result metadata. Test in development using a synthetic document; retry transient errors with bounded backoff and quarantine terminal failures without replaying signing actions blindly. ## Overview Configure and handle Documenso webhooks for real-time document lifecycle notifications. Webhooks require a Teams plan or higher. The webhook secret is sent via the `X-Documenso-Secret` header (not HMAC-signed -- it is a shared secret comparison). ## Prerequisites - Documenso team account (webhooks require teams) - HTTPS endpoint for webhook reception - Completed `documenso-install-auth` setup ## Supported Events | Event | Trigger | Use Case | |-------|---------|----------| | `document.created` | New document created | Audit logging | | `document.sent` | Document sent for signing | Start SLA timers | | `document.opened` | Recipient opens the document | Track engagement | | `document.signed` | One recipient completes signing | Progress tracking | | `document.completed` | All recipients have signed | Trigger downstream workflows | | `document.rejected` | Recipient rejects | Alert sender, escalate | | `document.cancelled` | Sender cancels document | Cleanup, notify recipients | ## Instructions ### Step 1: Create Webhook via Dashboard 1. Log into Documenso, navigate to **Team Settings > Webhooks**. 2. Click **Create Webhook**. 3. Enter your **HTTPS endpoint URL**. 4. Select the events you want to receive. 5. (Optional) Enter a **webhook secret** -- this value will be sent as-is in the `X-Documenso-Secret` header on every request. 6. Save. ### Step 2: Webhook Handler (Express) ```typescript // src/webhooks/documenso.ts import express from "express"; const router = express.Router(); const WEBHOOK_SECRET = process.env.DOCUMENSO_WEBHOOK_SECRET!; // Middleware: verify the shared secret function verifySecret(req: express.Request, res: express.Response, next: express.NextFunction) { const secret = req.headers["x-documenso-secret"]; if (!secret || secret !== WEBHOOK_SECRET) { console.warn("Webhook rejected: invalid secret"); return res.status(401).json({ error: "Invalid webhook secret" }); } next(); } router.post("/webhooks/documenso", express.json(), verifySecret, async (req, res) => { const { event, payload } = req.body; console.log(`Received ${event} for document ${payload.id}`); // Acknowledge immediately -- process async res.status(200).json({ received: true }); // Route to handler try { await handleEvent(event, payload); } catch (err) { console.error(`Failed to process ${event}:`, err); } }); async function handleEvent(event: string, payload: any) { switch (event) { case "document.completed": // All recipients signed -- download final PDF, update CRM await onDocumentCompleted(payload); break; case "document.signed": // One recipient signed -- track progress await onRecipientSigned(payload); break; case "document.rejected": // Recipient rejected -- alert sender await onDocumentRejected(payload); break; case "document.opened": // Track engagement for SLA console.log(`Document ${payload.id} opened by recipient`); break; default: console.log(`Unhandled event: ${event}`); } } async function onDocumentCompleted(payload: any) { const { id, title, recipients } = payload; console.log(`Document "${title}" (${id}) completed by all ${recipients?.length} recipients`); // Download signed PDF, store in S3, update database, notify team } async function onRecipientSigned(payload: any) { console.log(`Recipient signed document ${payload.id}`); // Update progress tracker, send notification } async function onDocumentRejected(payload: any) { console.log(`Document ${payload.id} REJECTED`); // Alert sender, create follow-up task } export default router; ``` ### Step 3: Verification in Python ```python # webhooks/documenso.py from flask import Flask, request, jsonify import hmac app = Flask(__name__) WEBHOOK_SECRET = os.environ["DOCUMENSO_WEBHOOK_SECRET"] @app.route("/webhooks/documenso", methods=["POST"]) def handle_webhook(): # Verify shared secret (constant-time comparison) secret = request.headers.get("X-Documenso-Secret", "") if not hmac.compare_digest(secret, WEBHOOK_SECRET): return jsonify({"error": "Unauthorized"}), 401 data = request.json event = data["event"] payload = data["payload"] print(f"Event: {event}, Document: {payload['id']}") if event == "document.completed": # Trigger post-signing workflow pass elif event == "document.rejected": # Alert and escalate pass return jsonify({"received": True}), 200 ``` ### Step 4: Local Development with ngrok ```bash # Start your webhook server npm run dev # listening on port 3000 # Expose via ngrok ngrok http 3000 # Copy the HTTPS URL (e.g., https://abc123.ngrok.io) # Add as webhook URL in Documenso dash
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__documenso-webhooks-events.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Documenso Webhooks Events skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Documenso Webhooks Events safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Documenso Webhooks Events access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Documenso Webhooks Events work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.