Block 1 - Check Java
- Type / Role
- n8n-nodes-base.executeCommand - executeCommand
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
PDF Digital Signature API with PAdES Compliance Sign PDF documents with legally compliant digital signatures using X.509 certificates. Supports multiple PAdES signature levels (B, T, LT, LTA) with ...
n8n-nodes-base.executecommand, n8n-nodes-base.if, n8n-nodes-base.httprequest, n8n-nodes-base.readwritefile, n8n-nodes-base.set, n8n-nodes-base.readbinaryfile, n8n-nodes-base.respondtowebhook, n8n-nodes-base.switch
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Vigh Sandor.
Original n8n.io sourceSign PDF documents with legally-compliant digital signatures using X.509 certificates. Supports multiple PAdES signature levels (B, T, LT, LTA) with optional visible stamps.
This workflow creates a professional PDF signing service that:
Perfect for contracts, invoices, legal documents, and any PDF requiring digital authentication.
Choose the signature level based on your needs:
BASELINE-B (Basic, 2-3 seconds)
BASELINE-T (Timestamp, 3-5 seconds) - Recommended
BASELINE-LT (Long-Term, 5-10 seconds)
BASELINE-LTA (Archival, 8-12 seconds)
Invisible (default):
Visible:
isVisible=true and logoFile to requestModify the signLevel parameter in your request:
B - BasicT - Timestamp (default)LT - Long-termLTA - ArchivalUpload a logo and add customization parameters to the signing command nodes:
--hint "Digitally Signed" # Custom text
--page 2 # Sign on page 2
--label-signee "Signed by" # Custom label
--label-timestamp "Date" # Custom timestamp label
--no-hint # Hide hint row
--signature-reason "Contract Approval" # Reason text
Modify these nodes to change temporary file locations:
Write Files : PDF - PDF storage pathWrite Files : PFX - Certificate storage pathWrite Files : LOGO - Logo storage pathFor production use, add authentication before the webhook:
The workflow automatically installs:
Uses OpenSSL to extract:
All files use timestamped names to prevent conflicts.
Implements ETSI EN 319 142 PAdES standards:
Q: Where do I get certificates? A: For testing, use free certificates from Codegic. For production, purchase from DigiCert, GlobalSign, or Sectigo.
Q: What PDF sizes are supported? A: Up to 50MB by default. Adjust n8n configuration for larger files.
Q: Can I sign multiple PDFs at once? A: Call the API once per PDF, or modify the workflow to accept multiple files.
Q: Will signatures work in Adobe Reader? A: Yes, if using certificates from trusted CAs. Self-signed certificates will show warnings.
Q: How do I verify signed PDFs? A: Open in Adobe Acrobat Reader and check the signature panel, or use the EU DSS validation tool webapp.
Q: Can I use this commercially? A: Yes, the workflow is free for personal and commercial use.
License: Free for personal and commercial use
Dependencies: OpenJDK 11, OpenSSL, curl, open-pdf-sign v0.3.0 (Apache 2.0)
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 65 workflow blocks. Download the JSON for the full node graph.
| Workflow | Sign PDF documents with X.509 certificates using PAdES standards |
|---|---|
| Complexity | advanced |
| Nodes | 65 |
| Categories | Document Extraction |
| Author | Vigh Sandor |
| Published | 07 Nov 2025 |
Use the JSON export at /data/workflows/10606/10606.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
PDF Digital Signature API with PAdES Compliance Sign PDF documents with legally compliant digital signatures using X.509 certificates. Supports multiple PAdES signature levels (B, T, LT, LTA) with ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction use case.