HumationHuman + Automation
Back to Catalog

Automate product launch sequence with Notion, Mailchimp, Buffer, Google Calendar & Telegram

Shelly-Ann DavyShelly-Ann Davy
46 views
2/3/2026
TrelloWordPressAutomationContent ManagementSynchronisation
Official Page

Automate Product Launch Sequence with Notion, Mailchimp, Buffer, Google Calendar & Telegram 🚀

Launch your digital products, courses, or content with confidence — using a fully automated sequence that handles email, social media, internal tracking, and team alerts.

No more missed steps. No last-minute panic. Just smooth, professional launches — on autopilot.

This workflow is perfect for:

  • 🧑‍🏫 Creators launching a course or eBook
  • 💼 Solopreneurs introducing a new offer
  • 📣 Marketers running a 5-day launch
  • 👩‍👧 Homemakers sharing a printables bundle

It automatically:

  1. 📅 Pulls launch content from your Notion database
  2. 💌 Sends email campaigns via Mailchimp
  3. 📱 Schedules social posts using Buffer
  4. 📆 Logs events in Google Calendar
  5. 📢 Sends internal alerts via Telegram

Setup Instructions

1. Notion Database Requirements

Your Notion database must have the following columns:

| Property | Type | Example | |--------|------|--------| | Name | Title | "Day 1: Welcome Email" | | Content Type | Select | Email, Social Post, Webinar | | Platform | Multi-select | Mailchimp, Buffer, Telegram | | Scheduled Date | Date | 2025-09-05 9:00 AM | | Email Subject | Text | "You're In! Here’s Your Guide" | | Email Body | Text | "Hi {{name}}, thanks for joining..." | | Social Message | Text | "Our new planner is live! Grab it here →" | | Status | Status | To Do, In Progress, Done |

📌 Tip: Duplicate our free Notion template to get started quickly.

How to Install

  1. Import the JSON into n8n.
  2. Set up credentials:
    • Notion API
    • Mailchimp API
    • Buffer (OAuth)
    • Google Calendar
    • Telegram Bot
  3. Connect to your Notion database.
  4. Run the workflow — it will process all items scheduled for today.

Customization Guidance

  • 🔄 Change the schedule: Replace the Trigger node with a Schedule node (e.g., daily at 8 AM).
  • 📧 Add more email platforms: Swap Mailchimp for ConvertKit or ActiveCampaign.
  • 📲 Use WhatsApp instead of Telegram: Replace Telegram with WhatsAble for team alerts.
  • 🎯 Filter by tag or audience: Add a Function node to route content based on Content Type.
  • 🌐 Add Instagram or LinkedIn: Extend Buffer to post to more platforms.

This workflow grows with your launch strategy.

Nodes Used

  • n8n-nodes-base.notion – Pull launch tasks
  • n8n-nodes-base.mailchimp – Send email campaigns
  • n8n-nodes-base.buffer – Schedule social media
  • n8n-nodes-base.googleCalendar – Log launch events
  • n8n-nodes-base.telegram – Send internal alerts

n8n Product Launch Sequence Automation

This n8n workflow provides a foundational structure for automating a product launch sequence. It demonstrates how to trigger actions, process data, make conditional decisions, and send notifications. While the provided JSON is a basic template, it can be extended with integrations like Notion, Mailchimp, Buffer, and Google Calendar to create a comprehensive launch system.

What it does

This workflow showcases:

  1. Manual or Scheduled Trigger: The workflow can be initiated manually or on a predefined schedule.
  2. Webhook Listener: It can respond to incoming webhooks, acting as an API endpoint for other services.
  3. Data Transformation: It includes a "Set" node to modify or add data fields and a "Code" node for custom JavaScript logic.
  4. Conditional Logic: An "If" node allows for branching the workflow based on specific conditions.
  5. External HTTP Requests: It can make requests to external APIs.
  6. Email Notifications: It can send emails.
  7. Telegram Notifications: It can send messages to a Telegram chat.
  8. Webhook Response: It can send a custom response back to the initiating webhook.

Prerequisites/Requirements

To fully utilize this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Email SMTP Credentials: For the "Send Email" node.
  • Telegram Bot Token and Chat ID: For the "Telegram" node.
  • Basic JavaScript Knowledge: If you plan to customize the "Code" node.
  • Understanding of HTTP Requests and APIs: For the "HTTP Request" and "Webhook" nodes.

Setup/Usage

  1. Import the Workflow:
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button (or paste the JSON directly).
    • Paste the provided JSON content into the import dialog.
    • Click "Import".
  2. Configure Credentials:
    • Locate the "Send Email" and "Telegram" nodes.
    • Click on each node and configure the necessary credentials (e.g., SMTP server details for email, bot token for Telegram).
  3. Configure Webhook:
    • The "Webhook" node will generate a unique URL when activated. This URL can be used by external services to trigger this workflow.
  4. Customize Nodes:
    • Edit Fields (Set): Modify this node to add, remove, or transform data fields as needed for your launch sequence.
    • If: Define the conditions for branching your workflow (e.g., if a product is "ready for launch", proceed to a specific branch).
    • HTTP Request: Configure this node to interact with external services like Notion, Mailchimp, or Buffer APIs.
    • Code: Write custom JavaScript logic for advanced data manipulation or integration.
    • Send Email / Telegram: Customize the message content and recipients for notifications.
  5. Activate the Workflow:
    • Once configured, toggle the workflow to "Active" to enable it.
    • You can trigger it manually using the "Manual Trigger" or set up a schedule using the "Schedule Trigger".

This workflow serves as a robust starting point for building sophisticated product launch automations. Expand upon its core functionalities by integrating specific app nodes relevant to your launch strategy.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942