Supabase insertion & upsertion & retrieval
This is a demo workflow to showcase how to use Supabase to embed a document, retrieve information from the vector store via chat and update the database. Setup steps: set your credentials for Supabase set your credentials for an AI model of your choice set credentials for any service you want to use to upload documents please follow the guidelines in the workflow itself (Sticky Notes) Feedback & Questions If you have any questions or feedback about this workflow - Feel free to get in touch at ria@n8n.io
Bytedance Seedream 3: text-to-image transformation template
This workflow provides automated access to the Bytedance Seedream 3 AI model through the Replicate API. It saves you time by eliminating the need to manually interact with AI models and provides a seamless integration for image generation tasks within your n8n automation workflows. Overview This workflow automatically handles the complete image generation process using the Bytedance Seedream 3 model. It manages API authentication, parameter configuration, request processing, and result retrieval with built-in error handling and retry logic for reliable automation. Model Description: Advanced AI model by bytedance for automated processing tasks. Key Capabilities High-quality image generation from text prompts Advanced AI-powered visual content creation Customizable image parameters and styles Tools Used n8n: The automation platform that orchestrates the workflow Replicate API: Access to the Bytedance/seedream-3 AI model Bytedance Seedream 3: The core AI model for image generation Built-in Error Handling: Automatic retry logic and comprehensive error management How to Install Import the Workflow: Download the .json file and import it into your n8n instance Configure Replicate API: Add your Replicate API token to the 'Set API Token' node Customize Parameters: Adjust the model parameters in the 'Set Image Parameters' node Test the Workflow: Run the workflow with your desired inputs Integrate: Connect this workflow to your existing automation pipelines Use Cases Content Creation: Generate unique images for blogs, social media, and marketing materials Design Prototyping: Create visual concepts and mockups for design projects Art & Creativity: Produce artistic images for personal or commercial use Marketing Materials: Generate eye-catching visuals for campaigns and advertisements Connect with Me Website: https://www.nofluff.online YouTube: https://www.youtube.com/@YaronBeen/videos LinkedIn: https://www.linkedin.com/in/yaronbeen/ Get Replicate API: https://replicate.com (Sign up to access powerful AI models) n8n automation ai replicate aiautomation workflow nocode imagegeneration aiart texttoimage visualcontent aiimages generativeart machinelearning artificialintelligence aitools automation digitalart contentcreation productivity innovation
Launch AWS EC2 instances from Google Sheets using Terraform
This automated n8n workflow enables launching AWS EC2 instances directly from a Google Sheets document. Users can specify instance details (e.g., region, instance type, key pair) in a Google Sheet, triggering the workflow to create EC2 instances via the AWS API. The workflow updates the sheet with instance information and sends confirmation emails. Fundamental Aspects Google Sheets Trigger: Initiates the workflow when a new row is added or updated in the Google Sheet. Extract Instance Details: Parses region, instance type, key pair name, and instance name from the sheet. Validate Inputs: Checks for required fields and valid AWS configurations. Launch EC2 Instance: Uses the AWS EC2 API to launch the specified instance. Update Google Sheet: Adds instance ID and status to the sheet. Send Confirmation Email: Notifies the user via email with instance details. Setup Instructions Import the Workflow into n8n: Download the workflow JSON and import it via the n8n interface. Configure API Credentials: Set up Google Sheets API credentials with appropriate permissions. Configure AWS IAM credentials with EC2 launch permissions. Configure SMTP credentials for email notifications. Prepare Google Sheet: Create a sheet with columns for region, instance type, key pair name, instance name, instance ID, and status. Run the Workflow: Activate the Google Sheets trigger and test by adding a row with instance details. Verify Responses: Check the Google Sheet for updated instance IDs and emails for confirmation. Adjust Parameters: Fine-tune AWS region settings or email templates as needed. Technical Dependencies Google Sheets API: For reading and writing data. AWS EC2 API: For launching and managing instances. SMTP Service: For sending confirmation emails. n8n: For workflow automation and integration. Customization Possibilities Add Instance Types: Support additional EC2 instance types. Enhance Validation: Add checks for AWS limits or quotas. Support Tags: Include custom tags for launched instances. Add Logging: Integrate with a logging service for workflow tracking. Customize Emails: Adjust email content or add attachments.
Create, update and get a post via Discourse
This workflow allows you to create, update and get a post using the Discourse node. Discourse node: This node creates a new post under a category. Based on your use-case, you can select a different category. Discourse1 node: This node updates the content of the post. Discourse2 node: This node fetches the node that we created using the Discourse node. Based on your use-case, you can add or remove nodes to connect Discourse to different services.
Create complete 20-song YouTube playlists with Suno API, Claude & Telegram bot
Transform your music creation process with this comprehensive automated system that generates complete playlists from simple text descriptions! π What You Get This professional-grade N8N workflow system automatically creates 20 unique songs per playlist (40 total tracks with 2 versions each) using cutting-edge AI technology. Simply describe your desired playlist through Telegram, and watch as the system generates song ideas, writes lyrics, produces audio, and organizes everything in Google Drive. β‘ Key Features π€ Telegram Bot Interface - User-friendly chat interface for playlist creation πΌ AI Song Generation - 20 unique song titles and descriptions per playlist π Automated Lyrics Writing - Professional-quality lyrics for each song π΅ Audio Production - High-quality music tracks via Suno AI π Organized Storage - Automatic Google Drive folder management π Complete Automation - End-to-end workflow with minimal manual intervention π οΈ APIs & Services Used Telegram Bot API - User interaction interface Claude AI (Anthropic) - Song ideation and lyrics generation Suno AI - Professional music track generation Google Sheets - Database management Google Drive - Automated file storage and organization Google Apps Script - Seamless file upload integration π¦ What's Included β 7 Complete N8N Workflows - Ready-to-import automation system β Comprehensive Setup Guide - Step-by-step installation instructions β Google Sheets Database Template - Pre-configured data structure β Google Apps Script Code - Custom Drive upload functionality β AI Prompt Templates - Optimized system messages for all agents β Troubleshooting Guide - Solutions for common issues β Customization Instructions - Modify outputs to match your style π‘ Perfect For Music producers and content creators Playlist curators and music enthusiasts Digital agencies offering music services Developers interested in AI automation Anyone looking to streamline music creation workflows π― System Requirements Active N8N instance (cloud or self-hosted) API access to: Telegram, Claude AI, Suno AI, Google Services Basic understanding of N8N workflows (setup guide included) π° Cost Considerations Suno AI: ~240 credits per playlist (20 songs Γ 2 versions) Claude AI: Variable based on usage Other APIs: Minimal costs for most use cases β±οΈ Expected Processing Time Complete playlist generation: 30-45 minutes per playlist (fully automated) --- π Bonus: Complete documentation includes AI agent customization guide, allowing you to fine-tune song styles, lyrics generation, and bot behavior to match your specific needs. Get instant access to this powerful automation system and start generating professional playlists today! --- If you need a csutom workflow please reach out via email joseph@uppfy.com
Ai lead scoring & enrichment from Mailchimp to HubSpot and Pipedrive with GPT-4o
How it works This workflow captures new subscribers from a Mailchimp list and extracts their key details. It then enriches the subscriber data using AI, predicting professional attributes and assigning a lead score. Based on the score, high-value leads are identified, and all leads are synced into HubSpot and Pipedrive. For top-priority leads, the workflow automatically creates new deals in Pipedrive for sales follow-up. Step-by-step Step-by-step Capture subscriber data Mailchimp Subscriber Trigger β Detects new signups in a Mailchimp list. Extract Subscriber Data β Normalizes payload into clean fields like name, email, and timestamp. Enrich with AI Lead Enrichment AI β Uses AI to infer company, role, industry, intent, LinkedIn, and lead score. Parse & Merge Enrichment β Merges AI output with subscriber info and sets defaults if parsing fails. Qualify leads High-Value Lead Check β Filters leads with a score β₯70 to flag them as priority. Create High-Value Deal β Opens a new deal in Pipedrive for high-value leads. Sync to CRMs HubSpot Contact Sync β Updates enriched lead data in HubSpot CRM. Pipedrive Person Create β Adds lead as a person in Pipedrive. Why use this? Automatically enrich raw Mailchimp subscribers with valuable professional insights. Score and qualify leads instantly for prioritization. Keep HubSpot and Pipedrive updated with enriched lead records. Automate deal creation for high-value opportunities, saving sales team effort. Build a seamless pipeline from marketing signups to CRM-ready opportunities.
Automated LinkedIn lead enrichment pipeline using Apollo.io & Google Sheets
LinkedIn to Apollo.io Lead Enrichment System with Google Sheets Automatically capture company and store details from LinkedIn posts, enrich them with domain names and key decision-maker (KDM) data from Apollo.io, and store everything neatly in Google Sheets. This workflow turns LinkedIn post data into a complete, structured lead database β fully automated from detection to enrichment. --- π§Ύ Summary This workflow reads LinkedIn post data (in JSON format) received via a webhook, extracts company and location information using an AI agent, and progressively enriches the data in three stages: Find Company Domain using Apollo.io Fetch Key Decision Makers (KDMs) using the company domain Find Corporate Emails for those KDMs All results are automatically updated in Google Sheets, ensuring your lead list remains fresh, structured, and actionable. --- βοΈ Prerequisites Before running the workflow, make sure you have: An Apollo.io API Key with company and people search access A connected Google Sheets account (OAuth2) A Webhook URL or LinkedIn scraper that feeds JSON-formatted post data (Optional) An OpenAI / AI Agent node to extract company names and store locations from post text --- π§© Example Input (Webhook JSON) Each LinkedIn post is received as a JSON object containing key clues: json { "index": 1, "text": "Excited to announce the opening of our new KFC store at Sky City Mall, Borivali East ππ\n\nLooking forward to welcoming you all to experience the Finger Lickinβ Good taste at our newest location!\n\nKFCIndia NewStoreOpening Borivali SkyCityMall Sapphirefoods", "CompanyName": "MockCompany", "NewStoreLocation": "optional", "PersonPosted": "https://linkedin.com/in/mockperson", "PostImage": null, "PostLink": "https://www.linkedin.com/search/results/all/?keywords=%23kfcindia&origin=HASHTAGFROM_FEED", "extracted_at": "2025-09-08T12:05:40.044101" } π§ Workflow Overview This workflow runs in three main stages, moving from LinkedIn data β company domain β people β emails. --- Stage 1: Company Name to Company Domain π Goal: Convert each company name into its website domain using Apollo.io. Nodes & Flow Schedule Trigger β Runs automatically (e.g., once a week) to check your Google Sheet for companies missing a domain. IF Node (Check for Missing Domain) β Filters only companies without a website. Loop Over Items β Iterates through each company record. HTTP Request β Find Domain β Calls the Apollo.io Company API to find the companyβs domain (e.g., kfc.com). Update Row in Google Sheets β Writes the found domain back into the corresponding company row. Wait Node β Delay Between API Calls β Adds a small pause to avoid hitting rate limits. --- Stage 2: Domain to Top 10 KDMs π₯ Goal: Fetch key decision-makers (KDMs) from each company using Apollo.io. Nodes & Flow Schedule Trigger β Runs on a weekly cadence to check for companies with a domain but no KDMs. Get Rows from Google Sheets β Pulls company records ready for enrichment. IF Node (Check for Missing KDMs) β Ensures only companies without people data are processed. Loop Over Items β Processes one company at a time. HTTP Request β Find KDMs β Searches Apollo.io People API for top roles such as Founder, CEO, Head of Retail, etc. Update Row in Google Sheets β Saves the top 10 names and their LinkedIn profiles into your sheet. Wait Node β Adds a delay to manage rate limits safely. --- Stage 3: KDM Profile to Email Enricher π§ Goal: Find and store verified corporate email addresses for each KDM. Nodes & Flow Schedule Trigger β Weekly automation trigger. Get Rows from Google Sheets β Pulls KDMs that have LinkedIn profiles but no email yet. IF Node (Check for Missing Emails) β Ensures only valid records are processed. Code Node β Prepare Data β Organizes LinkedIn profile and domain information. HTTP Request β Find Email β Queries Apollo.ioβs email enrichment endpoint using the LinkedIn URL and domain. Code Node β Format Response β Cleans and formats the email result. Wait Node β Adds delay to avoid request bursts. Update Row in Google Sheets β Writes the verified email address back to the corresponding KDM entry and marks it as βUpdated β email search.β π --- π§° Setup Instructions Connect APIs & Credentials Add your Apollo.io API Key under HTTP Request credentials. Connect your Google Sheets account (OAuth2). Customize Sheet Structure Add columns for: CompanyName, Domain, KDMs, LinkedInProfile, Email, Status Set Schedule Frequency Each Schedule Trigger can be configured separately (e.g., Stage 1 every Monday, Stage 2 every Wednesday). Optional: AI Extraction Node Use an AI model (like OpenAI or Gemini) to extract company name and location from LinkedIn post text before enrichment. --- π§° Custom Node Names (Recommended for Clarity) | Node Type | Recommended Name | Description | |------------|------------------|-------------| | HTTP Request (Company) | Find Company Domain (Apollo.io) | Searches for the companyβs official domain | | HTTP Request (People) | Find Key Decision Makers (Apollo.io) | Retrieves top company contacts | | HTTP Request (Emails) | Find Corporate Emails (Apollo.io) | Gets verified email addresses for each contact | | Wait Node | API Delay (Rate Limit Buffer) | Adds delay to avoid hitting API rate limits | | Code Node | Prepare KDM Data | Organizes input data for API calls | --- βοΈ Customization Tips Multiple Campaigns: Duplicate the workflow for different industries or store categories, updating parameters as needed. Batch Size: Adjust API request limits (e.g., 100 per batch) based on your Apollo.io plan. Filtering: Add IF conditions to skip records already marked as βCompleted.β Dashboards: Build visual analytics directly in Google Sheets or connect to Looker Studio. Enrichment: Combine with CRM systems (like HubSpot or Close) using company domain or lead email as the linking key. --- π Security and Publishing Notes π Never hardcode API keys in workflow exports. Use n8n credentials or environment variables instead. π« Replace sensitive values (like API keys or Sheet IDs) with placeholders before sharing. π Keep your Google Sheet private unless intentionally shared. --- π§© Troubleshooting No Data in Sheets: Check API response for data[] and verify Split Out configuration. Duplicate Rows: Ensure the βMatching Columnβ in Google Sheets is correctly set (e.g., CompanyName or LinkedInProfile). Rate Limits: Add Wait Nodes or reduce batch size. Mapping Errors: Confirm Google Sheet headers exactly match node field mappings. Timezone Adjustments: Apollo.io timestamps are in UTC β convert to local time if needed. --- π― Example Use Case Every week, this workflow scans new LinkedIn store-opening posts. It extracts company names (like KFC India), finds their domains and top executives through Apollo.io, retrieves their emails, and logs everything in a Google Sheet β ready for your sales team to reach out. --- Tags: LinkedIn Apollo Automation LeadGeneration GoogleSheets MarketingOps DataEnrichment