Merge Onboarding PDFs via PDFops + Google Drive Webhook (n8n)

Instantly fill and merge two onboarding PDFs, then deliver the final packet to Google Drive

This n8n workflow receives a webhook request with two fillable PDF URLs and field data, uses PDFops to fill both forms, merges them into a single onboarding packet, uploads the result to Google Drive, and returns a clear JSON success/error response.

What this workflow does

• Receives a POST webhook with formAUrl, formBUrl, fieldsA, fieldsB, and optional packetName.
• Validates inputs: ensures both form URLs are HTTPS and that fieldsA / fieldsB are JSON objects. Otherwise, it returns a 400 error.
• Downloads the blank PDFs from the provided URLs.
• Fills each PDF with the corresponding field values using the PDFops tools.
• Combines and merges the two filled documents into one packet, confirming both filled files exist before continuing.
• Names the output using packetName (or a default filename) and then uploads the merged PDF to Google Drive.
• Returns JSON: a success response on completion, or a 400 error if any step fails.

Use cases

• Auto-generate onboarding packets from two separate forms (e.g., “Employee Info” + “IT Access”) after a customer signs up.
• SaaS operations: produce consistent PDF onboarding documentation per user and store it in the correct Google Drive folder.
• Automation engineers: expose an n8n webhook endpoint that another system can call with URLs + field JSON.

Technical details

• Webhook trigger (POST endpoint accepting formAUrl, formBUrl, fieldsA, fieldsB, packetName).
• PDFops community node: n8n-nodes-pdfops (PDFops integration).
• Google Drive credential + upload step (Drive and folder configurable).
• Includes if/merge logic to validate, combine, and ensure filled outputs exist.