Actions55
- PDF Asset Actions
- PDF Engine Actions
- Signing Process Actions
- Template Actions
- Template Asset Actions
- Template Category Actions
- Template Tag Actions
- Webhook Actions
Signing Process → Create
AI-generatedSummary
Create a SmartDocs signing process from a stored PDF asset. Set its subject, dispatch mode, expiry, signer definitions, and optional signing fields or extra settings; the node sends these to SmartDocs and returns the API response as JSON.
Inputs
- Source PDF Asset ID (required) — ID of the stored PDF asset to use for the signing process.
- Subject (required) — Subject for the signing process.
- Dispatch Mode (required) — Choose Email, Kiosk, or Current User.
- Expires At (required) — Expiry date and time for the signing process.
- Signers — JSON array of signer definitions. Each signer must include signOrder; optional fields include name, email, phoneE164, roleLabel, linkedUserId, and locale.
- Fields — JSON array of signing field definitions, with assignedSignerSignOrder, type, label, page, position and dimensions (x, y, w, h), and required status.
- Additional Fields — Optional settings: Auth Policy (AES OTP or SES Link Only), Message, and Metadata as JSON.
Output shape
A single JSON response record for each input item.
The request is sent to SmartDocs as a POST to /signing-processes. Signers and Fields default to empty arrays; supplied JSON values are parsed before sending. Metadata is parsed and included only when provided.