Send PDF payment receipts with Stripe, EmitForge, Gmail, Google Drive and Slack
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 9 nodes and runs on Stripe events (charge.succeeded). Along the way it connects Stripe, Gmail, Google Drive and Slack. It also calls emitforge.com over HTTP.
How it runs
Trigger: On Stripe events (charge.succeeded).
- Set company details (Edit Fields (Set)): sets 4 fields: company_name, company_address, support_email…
- Build the receipt fields (Code): runs custom JavaScript code
- Has a customer email? (If): checks a condition and branches into true / false
- Render the receipt PDF (HTTP Request): calls emitforge.com (POST)
- Download the rendered file (HTTP Request): calls an HTTP API
- Email the receipt to the customer (Gmail): uses Gmail
- Archive the receipt in Drive (Google Drive): uses Google Drive
- Post a one-line summary to Slack (Slack): uses Slack
Services it uses
HTTP calls to: emitforge.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Stripe Trigger
n8n-nodes-base.stripeTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - Gmail
n8n-nodes-base.gmail - Google Drive
n8n-nodes-base.googleDrive - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow listens for successful Stripe charges, generates a branded PDF receipt via EmitForge, then emails it to the customer with Gmail while optionally archiving the PDF to Google Drive and posting a confirmation message to Slack. How it…