Workflow Templates

📌 Who’s it for This subworkflow is designed for developers, AI engineers, or automation builders who generate dynamic HTML content in their workflows (e.g. reports, dashboards, emails) and want a simple way to host and share it via a clean URL, without spinning up infrastructure or uploading to a CMS. It’s especially useful when combined with AI agents that generate HTML content as part of a larger automated pipeline. ⚙️ What it does This subworkflow: Accepts raw HTML content as input. Creates a new GitHub Gist with that content. Returns the shareable Gist URL, which can then be sent via Slack, Telegram, email, etc. The result is a lightweight, fast, and free way to publish AI-generated HTML (such as reports, articles, or formatted data outputs) to the web. 🛠️ How to set it up Add this subworkflow to any parent workflow where HTML is generated. Pass in a string of valid HTML via the html input parameter. Configure the GitHub credentials in the HTTP node using an access token with gist scope. ✅ Requirements GitHub account and personal access token with gist permissions 🔧 How to customize Change the filename (report.html) if your use case needs a different format or extension. Add metadata to the Gist (e.g., description, tags).

📝Content Management

1 nodes1 views

Update Twitter Banner Using HTTP Request

by System Admin

No description available

4 nodes1 views

AI Hairstyle Preview Generator with OpenAI and LINE Group Sharing

by kote2

Overview This workflow takes an image + instruction text from an n8n Form, edits only the hairstyle while keeping the face unchanged, uploads the result to Cloudinary, and pushes the image to a designated LINE group. It’s designed for salons or creative teams that need quick, consistent “hair-only” edits and one-click sharing to a staff group. Key Features Accepts image and free-form instructions via n8n Forms Enforces identity preservation: face is not altered; only the hairstyle is modified Uses OpenAI Image Edit to generate the edited image Uploads the output to Cloudinary and returns a public URL Sends the final image to a LINE group via the Push API (no replyToken required) Optional safety: store the groupId once (via webhook) in n8n Data Store and reuse it, avoiding mis-sending to individuals Requirements OpenAI API key (Image Edit capable model) Cloudinary account with an unsigned upload_preset LINE Official Account (Messaging API enabled) and the bot added to the target group (to capture groupId once) n8n with Forms enabled and Data Store available Notes Replace placeholders like CLOUDINARY_CLOUD_NAME, CLOUDINARY_UPLOAD_PRESET, LINE_CHANNEL_TOKEN, and LINE_GROUP_ID with your values.

1 nodes2 views

Send Postcards to Contacts Automatically using CentralStationCRM and EchtPost

by CentralStationCRM

Workflow Overview This workflow benefits anyone, who: wants to automate sending Postcards to tagged CentralStationCRM contacts Tools in this Workflow CentralStationCRM - the simple and intuitive CRM Software for small teams. EchtPost - send postcards online Workflow Screenshot Workflow Description This workflow consists of: a webhook trigger a set node an if node an HTTP request The Webhook Trigger The webhook triggers when a person is updated in CentralStationCRM. The persons data is sent to n8n, including the company name and the address. The Set node This node filters the webhook data for just the data the EchtPost node needs. It also transforms the country field to the associated country code (i.e. "Deutschland" -> "DE") The if node This node checks if there is an "EchtPost" tag in the persons data. -> if false: do nothing -> if true: go to HTTP request The HTTP Request This node sends the persons name, address and country code alongside with the id of the EchtPost template (inserted manually in the node) to EchtPost. It also needs an E-Mail-Adress for a confirmation mail. The data starts a "Mail in 3 days" process with the EchtPost service, which mails a postcard with that template to the person. Preconditions For this workflow, you need: a CentralStationCRM account with API access an EchtPost account with API access an EchtPost template, with a message, and the templates ID

1 nodes6 views

🐋DeepSeek V3 Chat & R1 Reasoning Quick Start

by System Admin

Tagged with: , , , ,

Create, update, and get a profile in Humantic AI

by System Admin

No description available

5 nodes1 views

Integrating AI with Open-Meteo API for Enhanced Weather Forecasting

by System Admin

No description available

🤖AI & Machine Learning

12 nodes1 views

Extract High-Engagement YouTube Keyword Trends for Content Strategy

by Sulieman Said

📊 YouTube Trends Workflow in n8n 🎯 Goal of the Workflow This workflow fetches the most popular YouTube videos in Germany and transforms them into a clean list of trending hashtags/keywords. It’s not just raw data – it highlights qualitative insights about which topics and keywords drive real engagement. Useful for: Content creators & marketers** → quick inspiration for viral topics SEO/hashtag research** → discover high-performing keywords Social media teams** → automated trend reporting ⚙️ How It Works – Step by Step 1. Trigger Node:** Manual Trigger Entry point of the workflow. → Can later be replaced with a Cron or Webhook trigger to run automatically. 2. API Call – YouTube Node:** HTTP Request Calls the YouTube Data API v3 with: chart=mostPopular regionCode=DE maxResults=50 Returns a list of trending videos in Germany, including title, channel, views, likes, comments, and tags. 3. Split Items Node:** Split Out Splits the API response (items[]) into individual items, so each video is processed separately. 4. Context & KPIs Node:** Set Extracts key fields: title, channel, publishedAt views, likes, comments Calculates: engagementRate = (likes + comments) / (views + 1) Why? Looking at views alone is misleading. Engagement rate reveals which videos truly resonate with the audience. 5. Ranking & Limit Node:** Item Lists Sorts videos by highest engagement rate (descending). Limits results to the Top 20 videos. Why? This reduces noise and focuses only on the most relevant trends. 6. Collect Tags Node:** Aggregate Collects all snippet.tags from the top videos. Merges them into a single keyword list. 7. Keyword Summary Node:** Summarize Concatenates all collected tags into one string. Result: A compact hashtag/keyword list → ready to use for: Content ideas SEO/hashtag strategies Social media planning 📈 Why This Workflow Is Useful Automated trend analysis**: no need to manually browse YouTube. Quality focus**: uses engagement rate, not just views. Reusable**: results can be: stored in Google Sheets or Airtable, sent to Slack/Telegram, or used in a dashboard. 🚀 Possible Extensions Cron Trigger** → run daily for automated reports. Notifier** → send results directly to Slack, Discord, or Telegram. Storage** → save trends in a database for historical analysis. AI Node** → use GPT to summarize trends into “3 key insights of the day.” ✅ Conclusion With a few smartly combined nodes, this workflow: fetches external API data (YouTube), cleans and enriches it, calculates qualitative KPIs, and delivers actionable trend insights. Perfect as a community showcase or a practical tool for creators and marketers.