HumationHuman + Automation
Back to Catalog

Create a REST API for PDF digital signatures with webhooks

Ferenc ErbFerenc Erb
5596 views
2/3/2026
Google DriveAutomationAttachmentsEmailTelegram
Official Page

Overview

An automation workflow that creates a complete REST API for digitally signing PDF documents using n8n webhooks. This service demonstrates how to implement secure document signing functionality through standardized API endpoints with file upload and download capabilities.

Use Case

This workflow is designed for developers and automation specialists who need to implement digital document signing. It's particularly useful for:

  • Integrating PDF signing capabilities into existing document workflows
  • API-based automation of signature processes
  • Creating proof-of-concept implementations for document verification systems
  • Learning n8n's webhook capabilities and file handling techniques
  • Testing PDF signing in development environments before production implementation

What This Workflow Does

API-Based Document Management

  • Exposes RESTful webhook endpoints for all document operations
  • Handles multipart/form-data uploads for PDF documents
  • Processes JSON payloads for signing configuration
  • Provides download functionality for completed documents

Digital Certificate Handling

  • Uploads existing PFX/PKCS#12 digital certificates
  • Generates new certificates with customizable attributes
  • Securely manages certificate storage and access
  • Associates certificates with signing operations

Cryptographic PDF Signing

  • Applies digital signatures using industry-standard cryptographic methods
  • Embeds signature information within PDF document structure
  • Validates document integrity through cryptographic verification
  • Preserves original document while adding signature elements

Webhook Integration System

  • Routes different API methods to appropriate handlers
  • Validates request payloads and file content
  • Manages authentication through webhook paths
  • Returns structured responses for integration with other systems

Technical Architecture

Components

  1. API Gateway: n8n webhook nodes that receive external requests
  2. Request Router: Switch nodes that direct operations based on method parameters
  3. Document Processor: Function nodes for PDF manipulation and verification
  4. Certificate Manager: Specialized nodes for cryptographic key operations
  5. Storage Interface: File operation nodes for document persistence
  6. Response Formatter: Nodes that structure API responses

Integration Flow

Client Request → Webhook Endpoint → Method Router → 
Processing Engine → Digital Signing → Storage → 
Response Generation → Client Response

Setup Instructions

Prerequisites

  • n8n installation (minimum version 0.214.0)
  • Node.js 14 or higher
  • Required environment variable: 
    NODE_FUNCTION_ALLOW_EXTERNAL: "node-forge,@signpdf/signpdf,@signpdf/signer-p12,@signpdf/placeholder-plain"

Configuration Steps

  1. Import Workflow

    • Import the workflow JSON into your n8n instance
    • Activate the workflow to enable the webhooks

  2. Configure Storage

    • Set the storage path variables in the workflow
    • Ensure proper permissions on the storage directories

  3. Test API Endpoints

    • Use the included test scripts to verify functionality
    • Test PDF upload, certificate generation, and signing

  4. Integration

    • Document the webhook URLs for integration with other systems
    • Configure error handling according to your requirements

Testing Methods

Test the workflow functionality using various HTTP requests and JSON data:

  • Upload PDF documents to the document processing endpoint
  • Upload or generate digital certificates
  • Execute PDF signing operations
  • Download signed documents from the download endpoint

Webhook Endpoints

The workflow exposes two primary webhook endpoints that form a complete API for PDF digital signing operations:

1. Document Processing Endpoint (/webhook/docu-digi-sign)

This endpoint handles all document and certificate operations:

Method: Upload PDF

  • HTTP: POST
  • Content-Type: multipart/form-data
  • Parameters: method, uploadType, fileName, fileData

Method: Upload Certificate

  • HTTP: POST
  • Content-Type: multipart/form-data
  • Parameters: method, uploadType, fileName, fileData

Method: Generate Certificate

  • HTTP: POST
  • Content-Type: application/json
  • Parameters: method, subjectCN, issuerCN, serialNumber, validFrom, validTo, password

Method: Sign PDF

  • HTTP: POST
  • Content-Type: application/json
  • Parameters: method, inputPdf, pfxFile, pfxPassword

2. Document Download Endpoint (/webhook/docu-download)

This endpoint handles the retrieval of processed documents:

Method: Download Signed PDF

  • HTTP: GET
  • Content-Type: application/json
  • Parameters: method, fileType, fileName

Key Workflow Sections

The workflow is organized into logical sections with clear responsibilities:

  • Request Processing: Parses incoming webhook data
  • Method Routing: Directs requests to appropriate handlers
  • Document Management: Handles file operations and storage
  • Cryptographic Operations: Manages signing and certificate functions
  • Response Formatting: Structures and returns results

n8n Workflow: Basic Webhook Listener and File Operations

This n8n workflow demonstrates a fundamental setup for receiving webhook requests, performing conditional logic, manipulating data, and interacting with the local file system. It acts as a starting point for building more complex API endpoints that might involve data processing and file handling.

What it does

This workflow performs the following key steps:

  1. Listens for Webhook Requests: It starts by exposing a webhook URL that triggers the workflow upon receiving an HTTP request.
  2. Performs Conditional Logic: An "If" node evaluates incoming data, allowing the workflow to branch based on specific conditions (e.g., checking a query parameter or body field).
  3. Transforms Data (Optional): A "Set" node is available to modify or add fields to the incoming data, preparing it for subsequent steps.
  4. Executes Custom Code: A "Code" node provides the flexibility to run custom JavaScript logic, enabling advanced data manipulation or integration with external libraries.
  5. Reads/Writes Files from Disk: The "Read/Write Files from Disk" node allows the workflow to interact with the local file system, such as reading existing files or writing new ones.
  6. Converts Data to File: The "Convert to File" node can transform structured data (like JSON) into a file format (e.g., CSV, text) for storage or further processing.
  7. Responds to Webhook: It concludes by sending a response back to the originating webhook request, which can include status codes and custom data.
  8. Provides Notes: A "Sticky Note" is included for documentation within the workflow itself.
  9. Further Conditional Logic: A "Switch" node offers more advanced branching capabilities, allowing multiple paths based on different conditions.

Prerequisites/Requirements

  • n8n Instance: An active n8n instance (self-hosted or cloud) where you can import and run workflows.
  • Basic Understanding of Webhooks: Familiarity with how webhooks work and how to send requests to them.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the content of the JSON file, or upload the file directly.
  2. Activate the Workflow: After importing, ensure the workflow is active by toggling the "Active" switch in the top right corner.
  3. Configure the Webhook:
    • The "Webhook" node will display a unique test and production URL. Copy this URL.
    • Send an HTTP request (e.g., using Postman, curl, or another application) to this URL to trigger the workflow.
  4. Customize Nodes:
    • If Node: Configure the conditions in the "If" node to match your specific logic.
    • Edit Fields (Set) Node: Adjust the fields to be set or modified based on your data transformation needs.
    • Code Node: Write your custom JavaScript code to perform specific operations on the incoming data.
    • Read/Write Files from Disk Node: Specify the file path and operation (read, write, append) as required.
    • Convert to File Node: Define the input data and the desired output file format.
    • Switch Node: Set up multiple cases for different branching scenarios.
    • Respond to Webhook Node: Customize the response body and status code.
  5. Test the Workflow: Use the "Test Workflow" button or send a webhook request to the test URL to ensure it functions as expected.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942