HumationHuman + Automation
Back to Catalog

Generate PDF documents from HTML with PDF Generator API, Gmail and Supabase

Marián DanašMarián Današ
113 views
2/3/2026
documentationautomationreadmegeneratormarkdown
Official Page

Who’s this for 💼

This template is designed for teams and developers who need to generate PDF documents automatically from HTML templates. It’s suitable for use cases such as invoices, confirmations, reports, certificates, or any custom document that needs to be created dynamically based on incoming data.

What this workflow does ⚙️

This workflow automates the full lifecycle of document generation, from request validation to delivery and storage. It is triggered by a POST webhook that receives structured JSON data describing the requested document and client information.

Before generating the document, the workflow validates the client’s email address using Hunter Email Verification to prevent invalid or mistyped emails. If the email is valid, the workflow loads the appropriate HTML template from a Postgres database, fills it with the incoming data, and converts it into a PDF using PDF Generator API.

Once the PDF is generated, it is sent to the client via Gmail, uploaded to Supabase Storage, and the transaction is recorded in the database for tracking and auditing purposes.

How it works 🛠️

  1. Receives a document generation request via a POST webhook.
  2. Validates the client’s email address using Hunter.
  3. Generates a PDF document from an HTML template using PDF Generator API.
  4. Sends the PDF via Gmail and uploads it to Supabase Storage.
  5. Stores a document generation record in the database.

How to set up 🖇️

Before activating the workflow, make sure all required services and connections are prepared and available in your n8n environment.

  • Create a POST webhook endpoint that accepts structured JSON input.
  • Add Hunter API credentials for email verification.
  • Add PDF Generator API credentials for HTML to PDF conversion.
  • Prepare a Postgres database with tables for HTML templates and document generation records.
  • Set up Gmail or SMTP credentials for email delivery.
  • Configure Supabase Storage for storing generated PDF files.

Requirements ✅

  • PDF Generator API account
  • Hunter account
  • Postgres database
  • Gmail or SMTP-compatible email provider
  • Supabase project with Storage enabled

How to customize the workflow 🤖

This workflow can be adapted to different document generation scenarios by extending or modifying its existing steps:

  • Add extra validation steps before document generation if required.
  • Extend delivery options by sending the generated PDF to additional services or webhooks.
  • Enhance security by adding document encryption or access control.
  • Add support for additional document types by storing more HTML templates in the database.
  • Modify the database schema or queries to store additional metadata related to generated documents.
  • Adjust the data mapping logic in the Code node to match your input structure.

Generate PDF Documents from HTML with PDF Generator API, Gmail, and Supabase

This n8n workflow automates the process of generating PDF documents from HTML content, storing them in Supabase, and sending them via email. It's designed to streamline document creation and distribution, making it ideal for invoicing, report generation, or any scenario requiring dynamic PDF creation and delivery.

What it does

This workflow is triggered manually and performs the following steps:

  1. Starts Manually: The workflow is initiated manually, allowing for on-demand PDF generation.
  2. Generates HTML Content: A "Code" node is used to dynamically generate HTML content that will be converted into a PDF.
  3. Generates PDF: An "HTTP Request" node calls the PDF Generator API to convert the generated HTML into a PDF document.
  4. Checks for PDF Generation Success: An "If" node checks if the PDF generation was successful by evaluating the HTTP status code from the PDF Generator API response.
  5. Handles Successful PDF Generation:
    • Stores PDF in Supabase: If the PDF generation is successful, a "Postgres" node inserts the generated PDF (as a base64 encoded string) into a Supabase database.
    • Sends Email with PDF: A "Gmail" node sends an email with the generated PDF attached.
  6. Handles Failed PDF Generation:
    • Sends Error Email: If the PDF generation fails, a "Gmail" node sends an email notification about the failure.
  7. Responds to Webhook: A "Respond to Webhook" node sends a response back to the initiating webhook (though in this manually triggered workflow, it acts as a final output).
  8. Provides Information (Sticky Note): A "Sticky Note" node provides additional context or instructions within the workflow.
  9. Performs Hunter.io Action (Unconnected): A "Hunter" node is present in the workflow but is not connected to any other nodes, indicating it's either a placeholder or an unused component.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • PDF Generator API Account: An API key for the PDF Generator API.
  • Supabase Database: Access to a Supabase database with a table configured to store PDF data (e.g., a BYTEA or TEXT column for base64 encoded PDFs).
  • Gmail Account: A Gmail account configured as a credential in n8n for sending emails.
  • Postgres Credential: A Postgres credential configured in n8n to connect to your Supabase database.
  • HTTP Request Credential: An HTTP Request credential (or direct API key in the node) for the PDF Generator API.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • PDF Generator API: In the "HTTP Request" node for PDF generation, configure your API key for the PDF Generator API.
    • Supabase (Postgres): Update the "Postgres" node with your Supabase database credentials. Ensure the table name and column names match your Supabase setup.
    • Gmail: Configure your Gmail credential in the "Gmail" nodes for sending emails.
  3. Customize HTML Content: Modify the "Code" node to generate the HTML content you wish to convert into a PDF.
  4. Adjust Email Details: Customize the "Gmail" nodes with the desired recipient email addresses, subject lines, and body content for both success and failure notifications.
  5. Activate the workflow: Once configured, activate the workflow.
  6. Execute the workflow: Run the workflow manually to generate and send your PDF documents.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31