Flowgrammer

DocuSign Connect Webhook Test Pack

Original Connect HMAC test pack with raw-body vectors, rotating keys, and sixteen fictional cases.

Download the Connect webhook test pack (ZIP)

Download this pack when DocuSign envelopes already go out and you need to prove Connect HMAC on the exact raw body before SignatureEvidence accepts a row. The pack implements the DocuSign E-Signature Automation adapter and the published E-Signature Automation control plane. It includes fiction HMAC vectors, rotating Signature-N headers, sixteen cases, and a forbidden-downstream sheet.

Read the paired guide first: DocuSign E-Signature Automation. Keep the shared Signing Workflow Requirements Workbook nearby for the field list.

Download the Connect webhook test pack (ZIP)

The ZIP includes HMAC vectors, exact raw-body fixtures, JSON event files, setup notes, a routing checklist, and SX01 through SX12 plus SX-DS-01 through SX-DS-04. Samples stay fictional on 9 September 2026. No live DocuSign tenant is included, and this is not a Marketplace listing.

What you get

  • HMAC-SHA256 to Base64 vectors for X-Docusign-Signature-N
  • Multi-key rotation, missing signature, truncated body, CRLF, and re-serialized JSON failures
  • Fast ACK with queued-work notes
  • An idempotency table for replayed events
  • Routing-order checklist for change_routing_order and free-form signing risk
  • Forbidden-downstream rules for payment, bank-detail change, accounting, auto-renew, and auto-terminate
  • Sixteen fictional Cedar & Quay cases on DOC-CQ-SIGN-014

Keep these jobs separate

A completed envelope is not Document Approval DecisionEvidence. This pack covers the eSignature Connect adapter. Recipient signing order and Approve/Decline actions may implement a vendor-hosted gate. Broader DocuSign CLM and workflow products also support approval processes. Those vendor surfaces do not automatically become Flowgrammer Document Approval DecisionEvidence. Use the published Document Approval Workflow when an org decision is required. If the file lives in Dropbox and the job is internal approval, use the published Dropbox document approval workflow. This pack does not run IDP or OCR. Use invoice processing automation or the contract tracker when money or renewal is the actual job.

If you still need the shared signing model, start with E-Signature Automation. If you still need to choose a first workflow, start with Document Processing Automation.

How to start

  1. Read README.md, then markdown/setup.md.
  2. Walk csv/hmac-vectors.csv against fixtures/.
  3. Confirm the LF body passes. The test harness derives a CRLF body from that LF fixture; the derived body must fail against the LF digest.
  4. Confirm Signature-2 can pass after Signature-1 fails.
  5. Walk SX01 through SX12, then SX-DS-01 through SX-DS-04.
  6. Keep the paired DocuSign E-Signature Automation guide nearby.

If Connect enablement, HMAC keys, or the event log are still unclear, start with an AI Success Audit. If they are named, book a fit call to scope an AI Automation Systems build.

Book an AI Success Audit call