by Robin Geuens
Overview Use this workflow to create SEO-friendly outlines based on articles that do well in Google. Enter a keyword, and the workflow scrapes the top results, scrapes the content, analyzes it with AI, and builds a MECE (mutually exclusive, collectively exhaustive) outline. It’s useful for content creators and SEO specialists who want relevant, well-structured content. How it works Accepts a keyword submitted through a form Uses the SerpAPI to get top Google results for a chosen country Collects the top five URLs. We use five because we expect some to fail at the scraping stage Scrapes each URL separately Uses the first three articles to fit the AI model’s context window Extracts the main text from the page body Converts HTML to Markdown to get rid of tags and attributes. Combines the cleaned text into a single list for AI processing Analyzes the content with an AI language model to find common topics and headings Generates an SEO-focused outline based on the most frequent topics Setup steps Sign up for a SerpAPI account (free tier available) Create an OpenAI account and get an API key Set up your credentials within N8N Run the workflow and enter your keyword in the form. The workflow will generate an SEO-friendly outline for your content Improvement ideas Add another LLM to turn the outline into an article Use the Google docs API to add the outline to a Google doc Enright the outline with data from Perplexity or Tavily
by jason
A workflow to automatically create groups of three based on a Mattermost channel and send out invitations to each group member.
by jason
Receive a new book recommendation each Friday from Open Library. You can select the subject from thousands of options and have a new recommendation delivered to you automatically.
by Will Stenzel
This workflow recieves webhook data from a form submission and creates a new user (with name and email) if necessary. It also add the current semester of the program to the relation for the user.
by Gareth Roll
This workflow uses OpenAI to generate tweets to be stored in Airtable for review. A JS snippet handles the topics to be tweeted about in the form of hashtags.
by Valor
This workflow gets latest RSS from different RSS Sources and categorizes them with conditional. *Reference https://n8n.io/workflows/1507 https://n8n.io/workflows/617 https://n8n.io/workflows/199*
by Ghazi Triki
Fetches Zammad tickets at daily basis at 08:30 then sends them to #customer support>ticket on zulip for daily standups.
by Luka Zivkovic
Description A production-ready authentication workflow implementing secure user registration, login, token verification, and refresh token mechanisms. Perfect for adding authentication to any application without needing a separate auth service. Get started with n8n now! What it does This template provides a complete authentication backend using n8n workflows and Data Tables: User Registration**: Creates accounts with secure password hashing (SHA-512 + unique salts) Login System**: Generates access tokens (15 min) and refresh tokens (7 days) using JWT Token Verification**: Validates access tokens for protected endpoints Token Refresh**: Issues new access tokens without requiring re-login Security Features**: HMAC-SHA256 signatures, hashed refresh tokens in database, protection against rainbow table attacks Why use this template No external services**: Everything runs in n8n - no Auth0, Firebase, or third-party dependencies Production-ready security**: Industry-standard JWT implementation with proper token lifecycle management Easy integration**: Simple REST API endpoints that work with any frontend framework Fully customizable**: Adjust token lifespans, add custom user fields, implement your own business logic Well-documented**: Extensive inline notes explain every security decision and implementation detail How to set up Prerequisites n8n instance (cloud or self-hosted) n8n Data Tables feature enabled Setup Steps Create Data Tables: users table: id, email, username, password_hash, refresh_token refresh_tokens table: id, user_id, token_hash, expires_at Generate Secret Keys: Run this command to generate a random secret: node -e "console.log(require('crypto').randomBytes(32).toString('hex'))" Generate two different secrets for ACCESS_SECRET and REFRESH_SECRET Configure Secrets: Update the three "SET ACCESS AND REFRESH SECRET" nodes with your generated keys Or migrate to n8n Variables for better security (instructions in workflow notes) Connect Data Tables: Open each Data Table node Select your created tables from the dropdown Activate Workflow: Save and activate the workflow Note your webhook URLs API Endpoints Register: POST /webhook/register-user Request body: { "email": "user@example.com", "username": "username", "password": "password123" } Login: POST /webhook/login Request body: { "email": "user@example.com", "password": "password123" } Returns: { "accessToken": "...", "refreshToken": "...", "user": {...} } Verify Token: POST /webhook/verify-token Request body: { "access_token": "your_access_token" } Refresh: POST /webhook/refresh Request body: { "refresh_token": "your_refresh_token" } Frontend Integration Example (Vue.js/React) Login flow: const response = await fetch('https://your-n8n.app/webhook/login', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ email, password }) }); const { accessToken, refreshToken } = await response.json(); localStorage.setItem('accessToken', accessToken); Make authenticated requests: const data = await fetch('https://your-api.com/protected', { headers: { 'Authorization': Bearer ${accessToken} } }); Key Features Secure Password Storage**: Never stores plain text passwords; uses SHA-512 with unique salts Two-Token System**: Short-lived access tokens (security) + long-lived refresh tokens (convenience) Database Token Revocation**: Refresh tokens can be revoked for logout-all-devices functionality Duplicate Prevention**: Checks username and email availability before account creation Error Handling**: Generic error messages prevent information leakage Extensive Documentation**: 30+ sticky notes explain every security decision Use Cases SaaS applications needing user authentication Mobile app backends Internal tools requiring access control MVP/prototype authentication without third-party costs Learning JWT and auth system architecture Customization Token Lifespan**: Modify expiration times in "Create JWT Payload" nodes User Fields**: Add custom fields to registration and user profile Password Rules**: Update validation in "Validate Registration Request" node Token Rotation**: Implement refresh token rotation for enhanced security (notes included) Security Notes :warning: Important: Change the default secret keys before production use Use HTTPS for all webhook endpoints Store secrets in n8n Variables (not hardcoded) Regularly rotate secret keys in production Consider rate limiting for login endpoints Support & Documentation The workflow includes comprehensive documentation: Complete authentication flow overview Security explanations for every decision Troubleshooting guide Setup instructions FAQ section with common issues Perfect for developers who want full control over their authentication system without the complexity of managing separate auth infrastructure. Get Started with n8n now! Tags: authentication, jwt, login, security, user-management, tokens, password-hashing, api, backend
by Lorena
This workflow illustrates how to convert data from JSON to binary format and import JSON data or files into Google Sheets or local spreadsheets.
by Rahul Joshi
Description: Transform your Jira project management workflow with this intelligent n8n automation template that continuously tracks, scores, and reports the health of Jira Epics. The automation runs every 6 hours, fetches all active Epics, analyzes linked issues for performance, quality, and stability metrics, and automatically flags at-risk Epics. It updates Jira fields, sends alerts to Slack, logs trends in Google Sheets, and syncs visibility with Monday.com—ensuring teams stay proactive, not reactive. Ideal for agile teams, project managers, and product owners looking to monitor delivery health, detect risks early, and maintain transparent reporting across tools. ✅ What This Template Does (Step-by-Step) ⏱ Trigger Every 6 Hours: Automatically executes every six hours to keep health data updated in near real-time. 📥 Fetch All Epics from Jira: Retrieves all Epics, their keys, and fields via the Jira API to establish a full analysis scope. 🔀 Split Epics for Processing: Converts the batch of Epics into individual items, enabling sequential metric analysis. 🔗 Fetch Linked Issues: Collects all issues linked to each Epic, capturing their types, statuses, cycle times, and labels for deeper health analysis. 📈 Calculate Health Score: Computes a weighted score (0–1 scale) based on: • 40% Average Cycle Time • 30% Bug Ratio • 20% Churn (Reopened issues) • 10% Blocker Ratio Scores above 0.6 indicate at-risk Epics. ⚖️ Decision Gate: At-Risk or Healthy: If the health score exceeds 0.6, the workflow automatically initiates corrective actions. 🔧 Update Jira Epic: Updates Jira with the computed health score and adds an “At Risk” label for visibility in dashboards and filters. 🚨 Send Slack Alerts: Notifies the #project-alerts channel with Epic details, health score, and direct Jira links for immediate attention. 📋 Update Monday.com Pulse: Syncs health metrics and risk status back to your Monday board, maintaining cross-platform transparency. 📊 Log to Google Sheets: Appends health score logs with timestamps and Epic keys for trend analysis, audits, and dashboard creation. 🧠 Key Features ✔️ Automated Jira Epic health scoring (cycle time, churn, bugs, blockers) ✔️ Real-time risk flagging with Slack alerts ✔️ Integrated cross-tool visibility (Jira + Monday + Sheets) ✔️ Continuous trend tracking for performance improvement ✔️ Secure API-based automation 💼 Use Cases 💡 Track project delivery health and spot risks early 📈 Build executive dashboards showing team velocity and quality 🤝 Align product and engineering with shared visibility 🧾 Maintain a compliance audit trail of Epic health trends 📦 Required Integrations • Jira Software Cloud API – for Epic and issue data • Slack API – for real-time team alerts • Monday.com API – for visual board updates • Google Sheets API – for historical tracking and analytics 🎯 Why Use This Template? ✅ Prevents project delays by flagging risks early ✅ Provides automated, data-driven Epic health insights ✅ Connects your reporting ecosystem across platforms ✅ Perfect for Agile and DevOps teams driving continuous improvement
by Yaron Been
CDO Agent with Data Analytics Team Description Complete AI-powered data analytics department with a Chief Data Officer (CDO) agent orchestrating specialized data team members for comprehensive data science, business intelligence, and analytics operations. Overview This n8n workflow creates a comprehensive data analytics department using AI agents. The CDO agent analyzes data requests and delegates tasks to specialized agents for data science, business intelligence, data engineering, machine learning, data visualization, and data governance. Features Strategic CDO agent using OpenAI O3 for complex data strategy and decision-making Six specialized data analytics agents powered by GPT-4.1-mini for efficient execution Complete data analytics lifecycle coverage from collection to insights Automated data pipeline management and ETL processes Advanced machine learning model development and deployment Interactive data visualization and business intelligence reporting Comprehensive data governance and compliance frameworks Team Structure CDO Agent**: Data strategy leadership and team delegation (O3 model) Data Scientist Agent**: Statistical analysis, predictive modeling, machine learning algorithms Business Intelligence Analyst Agent**: Business metrics, KPI tracking, performance dashboards Data Engineer Agent**: Data pipelines, ETL processes, data warehousing, infrastructure Machine Learning Engineer Agent**: ML model deployment, MLOps, model monitoring Data Visualization Specialist Agent**: Interactive dashboards, data storytelling, visual analytics Data Governance Specialist Agent**: Data quality, compliance, privacy, governance policies How to Use Import the workflow into your n8n instance Configure OpenAI API credentials for all chat models Deploy the webhook for chat interactions Send data analytics requests via chat (e.g., "Analyze customer churn patterns and create predictive models") The CDO will analyze and delegate to appropriate specialists Receive comprehensive data insights and deliverables Use Cases Predictive Analytics**: Customer behavior analysis, sales forecasting, risk assessment Business Intelligence**: KPI tracking, performance analysis, strategic business insights Data Engineering**: Pipeline automation, data warehousing, real-time data processing Machine Learning**: Model development, deployment, monitoring, and optimization Data Visualization**: Interactive dashboards, executive reporting, data storytelling Data Governance**: Quality assurance, compliance frameworks, data privacy protection Requirements n8n instance with LangChain nodes OpenAI API access (O3 for CDO, GPT-4.1-mini for specialists) Webhook capability for chat interactions Optional: Integration with data platforms and analytics tools Cost Optimization O3 model used only for strategic CDO decisions and complex data strategy GPT-4.1-mini provides 90% cost reduction for specialist data tasks Parallel processing enables simultaneous agent execution Template libraries reduce redundant analytics development work Integration Options Connect to data platforms (Snowflake, BigQuery, Redshift, Databricks) Integrate with BI tools (Tableau, Power BI, Looker, Grafana) Link to ML platforms (AWS SageMaker, Azure ML, Google AI Platform) Export to business applications and reporting systems Disclaimer: This workflow is provided as a building block for your automation needs. Please review and customize the agents, prompts, and connections according to your specific data analytics requirements and organizational structure. Contact & Resources Website**: nofluff.online YouTube**: @YaronBeen LinkedIn**: Yaron Been Tags #DataAnalytics #DataScience #BusinessIntelligence #MachineLearning #DataEngineering #DataVisualization #DataGovernance #PredictiveAnalytics #BigData #DataDriven #DataStrategy #AnalyticsAutomation #DataPipelines #MLOps #DataQuality #BusinessMetrics #KPITracking #DataInsights #AdvancedAnalytics #n8n #OpenAI #MultiAgentSystem #DataTeam #AnalyticsWorkflow #DataOperations
by Rahul Joshi
Description Keep your CRM and task system perfectly in sync — automatically. This workflow monitors a Google Sheet for lead reply updates, instantly updates the corresponding contact in GoHighLevel (GHL), and creates a ClickUp follow-up task when a response is detected. It ensures your sales team never misses a warm lead and every reply is logged, tracked, and acted upon. ⚡ What This Template Does Watches a Google Sheet for reply status changes (“Yes” in the Replied column). 📄 Filters only rows where a lead has replied. 🔍 Updates the corresponding contact record in GoHighLevel (GHL). 🔗 Automatically creates a follow-up task in ClickUp with lead details. 🗂️ Merges updates from both GHL and ClickUp into a single result. 🔄 Logs sync status and timestamps in a tracking sheet (Sheet2) for auditing. 📋 Key Benefits Instant sync: Update GHL and ClickUp the moment a lead replies. ⚙️ Zero manual work: Automated updates and follow-up task creation. 🚫 Full traceability: Audit trail stored in a second Google Sheet. ✅ Increased sales responsiveness: Teams act immediately on new replies. 💬 Multi-app harmony: Connects Google Sheets, GHL, and ClickUp seamlessly. 🌐 Features Google Sheets trigger runs every minute to check for changes. ⏱️ Conditional logic (If node) processes only “Replied = Yes” leads. ✅ GHL contact update node for CRM synchronization. 💼 ClickUp task creation node with customizable priority and naming. 📝 Merge node to unify both paths before final sheet update. 🔀 Timestamp and action tracking for audit clarity. 📊 Visual sticky notes explaining each stage. 🧩 Requirements n8n instance (cloud or self-hosted). 🧰 Google Sheet with headers: Name, GHL_ID, Replied, Email. 📑 Connected credentials for: Google Sheets API (Trigger + Update access) GoHighLevel OAuth2 API ClickUp API Separate “log” sheet (Sheet2) for sync tracking. 📄 Target Audience Sales teams using GoHighLevel for CRM and ClickUp for task management. 🎯 Agencies managing multiple client pipelines. 🤝 Business development reps who track lead replies manually. 📞 Founders automating lead follow-up and CRM hygiene. 🚀 Step-by-Step Setup Instructions (Concise) Prepare a Google Sheet with columns: Name, GHL_ID, Email, Replied. 📋 Add a second sheet (“Sheet2”) for tracking updates. 📊 Connect credentials for Google Sheets, GoHighLevel, and ClickUp in n8n. 🔐 Import and open this workflow. Update GHL contact field mappings if your CRM structure differs. ⚙️ Adjust ClickUp team, space, and list IDs to match your setup. 📂 Execute manually once for testing, then enable it to run every minute. ▶️ Security Best Practices Share your Google Sheet only with the n8n Google account (Editor). 🔒 Keep API credentials securely stored in n8n’s credential manager. 🛡️ Log timestamps for traceability and rollback. ⏳ Periodically archive older sync logs to keep the sheet lightweight. 🧹