Automated post-purchase emails for Gumroad with Notion CRM and Gemini AI
Mirai MailFlow β Gumroad Personalized Autoreply
This n8n template automates post-purchase communication for Gumroad creators by sending AI-powered personalized thank-you emails and logging customer data into Notion. It helps creators engage buyers instantly while keeping a clean customer CRM β fully hands-free.
Use cases
- Automatically send personalized thank-you emails after every Gumroad purchase
- Maintain a lightweight customer CRM in Notion
- Reduce manual email follow-ups for digital product sales
- Improve buyer experience and post-purchase engagement
- Build a foundation for creator support, upsells, or onboarding flows
Good to know This workflow connects to a few external services, so credentials must be configured before running the template. It works on both n8n Cloud and self-hosted instances, and setup typically takes 5 minutes.
Requirements
- n8n Cloud or self-hosted instance
- Gmail account (OAuth connected) to receive and send emails
- Notion account with a customer database
- Google Gemini API key for AI-generated email content
Customising this workflow
- Replace Gmail with Slack, Telegram, or WhatsApp for message delivery
- Swap Google Gemini with OpenAI or Claude for different writing styles
- Add follow-up emails, upsells, or discount links
- Extend the Notion database into a full creator CRM
- Use it as a base for Gumroad analytics, support automation, or AI creator tools
n8n Workflow: Automated Post-Purchase Emails for Gumroad with Notion CRM and Gemini AI
This n8n workflow automates the process of sending personalized post-purchase emails to Gumroad customers, managing them in a Notion CRM, and leveraging Gemini AI for email content generation.
What it does
This workflow is triggered manually and is designed to:
- Start Manually: The workflow is initiated manually.
- Trigger by Gmail: It listens for new emails in Gmail that match specific criteria (e.g., Gumroad purchase notifications).
- Filter Emails: It uses an "If" node to filter incoming emails, likely checking for keywords or sender addresses to confirm they are Gumroad purchase emails.
- Extract Data with Code: A "Code" node processes the email content to extract relevant information about the purchase and customer.
- Generate Email Content with AI: An "AI Agent" node, utilizing the "Google Gemini Chat Model," generates a personalized post-purchase email based on the extracted data.
- Update Notion CRM: It creates or updates an entry in a Notion database with the customer and purchase details, including the generated email content.
- Send Personalized Email: Finally, it sends the AI-generated personalized email to the customer via Gmail.
- Handle Errors: If any critical step fails, the "Stop and Error" node will halt the workflow and report an error.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Gmail Account: Connected to n8n with appropriate credentials to read incoming Gumroad purchase emails and send outgoing emails.
- Notion Account: Connected to n8n with access to a CRM database where customer and purchase information will be stored.
- Google Gemini API Key: For the "Google Gemini Chat Model" to generate email content.
- Gumroad Purchase Notifications: Ensure your Gumroad account is configured to send purchase notifications to the monitored Gmail address.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Gmail: Set up your Gmail OAuth2 credentials for both the
Gmail TriggerandGmailnodes. Ensure the credentials have permissions to read emails and send emails. - Notion: Set up your Notion API credentials. Ensure the integration has access to the specific Notion database you intend to use as your CRM.
- Google Gemini: Configure your Google Gemini API key within the
Google Gemini Chat Modelnode.
- Gmail: Set up your Gmail OAuth2 credentials for both the
- Customize Nodes:
- Gmail Trigger: Adjust the "Query" field to specifically target your Gumroad purchase notification emails (e.g.,
from:noreply@gumroad.com subject:"New sale"). - If Node: Refine the conditions in the
Ifnode to accurately filter for valid Gumroad purchase emails if the Gmail trigger alone isn't sufficient. - Code Node: Modify the JavaScript code to correctly parse the specific structure of your Gumroad purchase notification emails and extract details like customer name, product name, and purchase amount.
- AI Agent / Google Gemini Chat Model: Customize the prompt in the
AI Agentnode to guide Gemini in generating the desired tone and content for your post-purchase emails. - Notion Node: Map the extracted data to the correct properties in your Notion CRM database.
- Gmail Node: Configure the "To," "Subject," and "Body" fields using expressions to dynamically insert customer and product details, along with the AI-generated email content.
- Gmail Trigger: Adjust the "Query" field to specifically target your Gumroad purchase notification emails (e.g.,
- Activate the Workflow: Once configured, activate the workflow. It will now run automatically based on the Gmail trigger.
- Test Thoroughly: Perform test purchases on Gumroad (or simulate emails) to ensure the workflow processes correctly, sends the right emails, and updates Notion as expected.
Related Templates
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
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch π LinkedIn β Wessel Bulte
Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review
This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.