Actions260
- Admin Job Management Actions
- Admin License Management Actions
- Admin Server Certificate Actions
- Admin Settings Actions
- AI Tools Actions
- Analysis Actions
- Audit Actions
- Authentication Actions
- Convert Actions
- Convert Ghostscript Inputs To Pdf
- Url To Pdf
- Convert Json To Pdf
- Convert Svg To Pdf
- Process Pdf To XML
- Pdf To Excel
- Process Pdf To Word
- Convert Pdf To Vector
- Process Pdf To RT For TXT
- Convert Pdf To Json
- Export Partial Pdf
- Extract Pdf Metadata
- Clear Cache
- Process Pdf To Presentation
- Pdf To Pdf A
- Process Pdf To Markdown
- Convert To Image
- Process Pdf To HTML
- Convert Pdf To Epub
- Pdf To Csv
- Convert Pdf To Cbz
- Convert Pdf To Cbr
- Markdown To Pdf
- Convert To Pdf
- Html To Pdf
- Process File To PDF
- Convert Eml To Pdf
- Convert Ebook To Pdf
- Convert Cbz To Pdf
- Convert Cbr To Pdf
- Extract Single Page
- Extract Page Fonts
- Database Actions
- File Storage Actions
- Filter Actions
- Forms Actions
- General Actions
- Info Actions
- Invite Actions
- Job Management Actions
- Misc Actions
- Metadata
- Unlock PDF Forms
- Extract Header
- Scanner Effect
- Replace And Invert Color
- Repair Pdf
- Rename Attachment
- Remove Blank Pages
- Process Pdf With OCR
- List Attachments
- Flatten
- Extract Images
- Extract Image Scans
- Extract Attachments
- Delete Attachment
- Decompress Pdf
- Optimize Pdf
- Auto Split Pdf
- Extract Header 1
- Add Stamp
- Add Page Numbers
- Overlay Image
- Add Comments
- Add Attachments
- Pipeline Actions
- Proprietary UI Data Actions
- Saved Signatures Actions
- Security Actions
- Signature Assets Actions
- Signing Sessions Actions
- Team Actions
- UI Data Actions
- User Actions
- Workflow Participant Actions
Workflow Participant → Submit Signature
AI-generatedSummary
Submits a participant's signature to a Stirling PDF signing workflow, sending certificate details, optional visible-signature settings and a participant token to the Stirling PDF API.
Inputs
- participantToken — Token identifying the workflow participant submitting the signature.
- certType — Certificate type string sent in the request body (e.g. the kind of certificate used). Valid values are not documented in the node.
- password — Password for the certificate/keystore.
- p12FileBinaryProperty — Name of the input binary property holding the P12 certificate file (default 'data').
- jksFileBinaryProperty — Name of the input binary property holding the JKS keystore file (default 'data').
- showSignature — Whether to render a visible signature on the PDF (default false).
- pageNumber — Page number on which to place the visible signature (default 0).
- location — Signing location text stored in the signature.
- reason — Reason for signing, stored in the signature.
- showLogo — Whether to show a logo in the visible signature (default false).
- wetSignaturesData — String data for handwritten ('wet') signatures to apply.
- requestOptions — Node settings for batching (items per batch, interval), ignoring SSL issues, proxy and request timeout (default 10000 ms).
Output shape
The response from the Stirling PDF API for the signature submission, returned as the node's output item(s).
The source pack contains only a class stub, so the exact response shape isn't visible. Behavior is inferred from the declared routing, which sends the fields as body parameters. The P12 and JKS binary fields have no routing in the properties, so how they are attached is not confirmed.
Examples
Example 1: Sign a document as a workflow participant using a P12 certificate
Set Participant Token, Cert Type, Password, and P12 binary field name 'data'; add Reason and Location.
Example 2: Add a visible signature on the first page
Enable Show Signature and Show Logo, set Page Number, and provide the participant token and certificate.