Flowgrammer

Adobe Sign Webhook Verification Pack

Original Acrobat Sign webhook pack with CLIENTID echo vectors, five-second ACK tests, and eighteen fictional cases.

Download the webhook verification pack (ZIP)

Download this pack when Acrobat Sign agreements already go out and you need to prove CLIENTID echo and retrieval timing before SignatureEvidence accepts a row. The pack implements the Adobe Acrobat Sign Automation adapter and the published E-Signature Automation control plane. It includes fiction CLIENTID echo vectors, five-second ACK notes, eighteen cases, and a forbidden-downstream sheet.

Read the paired guide first: Adobe Acrobat Sign Automation. Keep the shared Signing Workflow Requirements Workbook nearby for the field list. If you already verify DocuSign Connect, keep the published DocuSign E-Signature Automation page for that HMAC. If you already acknowledge Dropbox Sign callbacks, keep the published Dropbox Sign E-Signature Automation page for that event_hash. Those checks are not interchangeable.

Download the webhook verification pack (ZIP)

The ZIP includes CLIENTID echo vectors, timeout notes, JSON event files, setup notes, a retrieval matrix, and SX01 through SX12 plus SX-ADB-01 through SX-ADB-06. Samples stay fictional on 9 September 2026. No live Adobe tenant is included, and this is not an Adobe Exchange listing.

What you get

  • CLIENTID echo tests for intent GET and notify POST
  • Header echo and JSON xAdobeSignClientId body echo
  • Five-second ACK with queued-work notes
  • The 45-second callback timeout as a separate setting
  • RESOURCE versus ACCOUNT webhook scope
  • AGREEMENT_WORKFLOW_COMPLETED versus 10 MB truncation
  • An idempotency table for retried webhookNotificationId values
  • Forbidden-downstream rules for payment, bank-detail change, accounting, auto-renew, and auto-terminate
  • Eighteen fictional Cedar and Quay cases on DOC-CQ-SIGN-014

Keep these jobs separate

A completed agreement is not Document Approval DecisionEvidence. This pack covers the Acrobat Sign webhook adapter. Recipient signing and an Adobe APPROVER role may implement a vendor-hosted gate. Broader Acrobat Sign workflow products may exist. Those surfaces do not automatically become Flowgrammer Document Approval DecisionEvidence. Use the published Document Approval Workflow when an org decision is required. 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/clientid-echo-tests.csv and csv/timeout-queue-matrix.csv.
  3. Confirm CE01 and CE02 pass and CE03 fails when the Application ID is unknown.
  4. Confirm the five-second ACK queues work and a 6.2 second sync handler fails.
  5. Walk SX01 through SX12, then SX-ADB-01 through SX-ADB-06.
  6. Keep the paired Adobe Acrobat Sign Automation guide nearby.

If webhook enablement, Application IDs, 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