Templates / Generate and email Stripe invoice PDFs with PDFBolt and Gmail

Generate and email Stripe invoice PDFs with PDFBolt and Gmail

Unknown

by PDFBolt ✓ · 7 views · created 2026-07-13 · Invoice Processing

Unknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.

Community nodes

These come from third-party npm packages. In n8n 3.0 unverified community packages are off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).

Nodes used (4)

StripeGmail

What it does

Quick overview This workflow triggers on successful Stripe invoice payments, formats the invoice data for a PDFBolt template, generates a PDF invoice, and emails it to the customer through Gmail. How it works 1. Triggers when Stripe emits an invoice.paymentsucceeded event for a paid invoice. 2. Extracts the Stripe invoice object, formats amounts, and maps customer and line-item fields into templateData for PDFBolt. 3. Generates a PDF from a published PDFBolt template using the Direct endpoint and returns the file as binary data. 4. Sends the generated PDF as an attachment in a Gmail email to the customer’s email address from the Stripe invoice. Setup 1. Connect your Stripe account and ensure the trigger can receive invoice.paymentsucceeded events. 2. Add your PDFBolt API key from https://app.pdfbolt.com/api-keys, publish an invoice template in PDFBolt, and paste its Template ID into the PDFBolt node. 3. Connect your Gmail account and adjust the email subject or body text if you want different wording or branding. Requirements - Stripe account connected in n8n - PDFBolt account and API key - Published PDFBolt invoice template - Gmail account connected in n8n Customization - Use your own PDFBolt Template ID - Match templateData fields to your invoice template variables - Customize the Gmail subject and message - Adjust filename or PDF options in the PDFBolt node Additional info PDFBolt returns the generated PDF as binary field data. Gmail uses that field as the attachment, so keep the field name unchanged unless you update the Gmail node too.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.