DocuSign Maestro Trigger
AI-generatedSummary
Starts a workflow when DocuSign Maestro sends a POST webhook, optionally verifying its HMAC-SHA256 signature and filtering by event type, then emits the request body as the item.
Inputs
- events — Multi-select of Maestro events to accept: Instance Started (workflow-instance-started), Instance Completed (workflow-instance-completed), Instance Failed (workflow-instance-failed). Defaults to Instance Completed. Payloads whose
eventfield is not in the selection are ignored (no workflow run). If the selection is empty or the payload has noeventfield, the payload passes through. - verifySignature — Default true. When on, the node reads webhookSecret from the DocuSign Maestro API credential and checks the
x-docusign-signature-1header against a base64 HMAC-SHA256 of the JSON-stringified body. A missing secret, missing header or mismatch causes an error and the request is rejected.
Output shape
One item per accepted webhook call, with json set to the full parsed request body from DocuSign Maestro.
The webhook responds immediately (responseMode onReceived). Filtered-out events produce no execution. Signature is computed over JSON.stringify of the parsed body, not the raw bytes, so re-serialization differences could cause valid requests to fail verification. The node requires the docuSignMaestroApi credential. Registration is a no-op: you must configure the n8n webhook URL (path 'webhook', POST) in DocuSign Maestro yourself.
Examples
Example 1: Notify Slack when a Maestro workflow instance fails
Events: Instance Failed only; Verify Signature on, with Webhook Secret set in the credential; connect to a Slack node.
Example 2: Track the full lifecycle of Maestro instances in a database
Events: Started, Completed and Failed all selected; Verify Signature on; connect to a database insert node.