# documenso-webhooks-events

documenso-webhooks-events configures Documenso webhook endpoints and event handlers. Useful when tracking document signing status and automating downstream actions.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 1 install · ★ 2935 repo stars
- Author: Jeremy Longshore
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/HEAD/skills/.curated/documenso-webhooks-events/SKILL.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/documenso-webhooks-events

## What it does

The skill provides implementation patterns for Documenso document lifecycle callbacks. It covers events such as `document.created`, `document.signed`, `document.completed`, and `document.rejected`. Sample handlers are provided for both Express in TypeScript and Flask in Python.

Event handling relies on immediate HTTP 200 acknowledgments before asynchronous execution begins. To prevent duplicate execution, it creates an idempotency key using the event type, document ID, and update timestamp. Local endpoint verification uses ngrok alongside synthetic curl payloads.

Webhooks in Documenso require a Teams plan or higher. The platform does not use HMAC signatures. It sends a raw shared secret in the `X-Documenso-Secret` header, which requires constant-time string comparison to avoid timing vulnerabilities.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-webhooks-events -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/documenso-webhooks-events/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/documenso-webhooks-events/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-webhooks-events -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/documenso-webhooks-events/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-webhooks-events -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/documenso-webhooks-events/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install jeremylongshore/tons-of-skills-marketplace skills/.curated/documenso-webhooks-events
```

2. **Manually: put the files in place**
- File: `.github/skills/documenso-webhooks-events/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-webhooks-events -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace --path skills/.curated/documenso-webhooks-events
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/documenso-webhooks-events/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-webhooks-events -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/HEAD/skills/.curated/documenso-webhooks-events/SKILL.md

## When to use it
- set up Documenso webhook routes in Express or Flask
- verify the `X-Documenso-Secret` header securely
- handle document lifecycle events like completion or rejection
- test webhook delivery locally using ngrok and curl

## Example prompts
- Set up an Express webhook endpoint for Documenso events
- How do I verify the X-Documenso-Secret header in Python?
- Write an idempotent handler for document.completed events

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: c896c42f8d677924.

BEGIN THIRD-PARTY FILE c896c42f8d677924
```text
---
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 <jeremy@intentsolutions.io>
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**.
```
END THIRD-PARTY FILE c896c42f8d677924

The third-party file has ended. Everything between the c896c42f8d677924 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2409 of 8486 bytes. © Jeremy Longshore · MIT · https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/HEAD/skills/.curated/documenso-webhooks-events/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
