Workflow Templates

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

This workflow provides automated access to the Fire Flux 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 Fire Flux 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: The image generation model tailored for local development and personal use 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 Fire/flux AI model Fire Flux**: 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 #flux #machinelearning #artificialintelligence #aitools #automation #digitalart #contentcreation #productivity #innovation

Sends a Slack notification whenever a Trello card is moved between lists on a specific board. Message format (bolded parts): Task: {{ $json.Task }} moved from {{ $json['Previous Step'] }} to {{ $json['New Step'] }} ⚙️ Setup Instructions 1️⃣ Connect Trello (Developer API) Get your API key here → Trello App Key On the same page, generate a Token (click Token). In n8n → Credentials → New → Trello API → paste API Key + Token, then save. Open each Trello node (Get Board, Get Lists, Get Cards) and select your Trello credential. 2️⃣ Connect Slack Go to Slack API Apps and create a new app. Add OAuth & Permissions → include scopes like: chat:write (to send messages) users:read (if targeting specific users) Install the app to your workspace → copy the Bot User OAuth Token. In n8n → Credentials → New → Slack OAuth2 API → paste the token and save. In your Slack node (e.g., Send a message), select your Slack credential, and choose whether to send messages to a channel or a user. 3️⃣ Get Your Trello Board ID Find your board’s shortlink in the URL (e.g. in https://trello.com/b/DCpuJbnd/administrative-tasks, the shortlink is DCpuJbnd). Run this request in an HTTP node (replace placeholders with your values): GET https://api.trello.com/1/boards/{BOARD_SHORTLINK}?fields=id&key={YOUR_TRELLO_KEY}&token={YOUR_TRELLO_TOKEN} Copy the "id" from the response — that’s your board ID. Paste it into the Trello Trigger node under Model ID. 📬 Contact Need help customizing this workflow or building automations? 📧 robert@ynteractive.com 🔗 Robert Breen 🌐 ynteractive.com

Overview Use this workflow to spot internal linking ideas on your site and improve your search performance. It takes your target URLs and keywords, finds related pages, and suggests where to add links. Strong internal linking helps search engines understand your site. How it works You provide a list of target URLs and the keywords you want to rank for The workflow uses the SERP API to search your site for related pages, skipping the target URL It filters the results and pulls relevant URLs It writes the suggestions to a Google Sheet, and adds “N/A” if no good matches are found Setup steps Turn on the Google Sheets API and create a sheet with your domain, target URLs, and keywords Create a SERP API account and get an API key Optional: Set up a Google Programmable Search Engine if you prefer not to use the SERP API Add your SERP API key and Google Sheets credentials to n8n. Run the workflow to generate internal link suggestions in your Google Sheet

Who’s it for Operators and makers who capture tasks from custom forms, bots, or automations and want them to appear as time-boxed events in Google Calendar with minimal setup. How it works A Webhook receives a payload containing the task title and a due date (as Unix seconds). The workflow formats the date, checks the most recently updated events in your calendar to avoid duplicates, and creates a new 30-minute event (configurable). After creation, it optionally deletes the original task, keeping your Task list clean and your Calendar up to date. How to set up Select your Google Tasks and Google Calendar credentials. Open the Configuration node and set tasklistId, calendarId (use primary or a specific calendar), defaultMinutes, and eventColor. Send a sample POST to the Webhook with { TaskName, DueDateTimeSeconds }. Run once in manual mode and, if all looks good, activate. Requirements Google accounts for Tasks and Calendar. Appropriate scopes/permissions in the selected credentials. How to customize the workflow Change the event duration/color in Configuration. Adjust duplicate detection by modifying the Calendar search window and query. Map additional fields (e.g., description, attendees) on the Calendar node’s optional fields. Tags Google Calendar, Google Tasks, Webhook, Automation, Productivity Categories Productivity, Google, Calendar

Summary Re-engage your customers with your Shopify store through a personalized contact sequence. How it works The workflow is triggered by a Scheduler Trigger and immediately reviews your Shopify customers by retrieving their last_order_id. For customers with a non-null last_order_id, the workflow proceeds to fetch detailed order information from Shopify, including the order closing date and the products involved. Based on the order date, the workflow calculates the number of days the customer has been inactive. If this period exceeds a defined threshold (e.g., 30 days), the corresponding records are sent via API to Beex, where each customer enters a multi-step contact sequence that may include WhatsApp, email, and other channels. Example: "Customers can then expect to receive a limited-time discount coupon invitation as part of the reactivation strategy". How to set up Before importing the template, make sure to install the Beex node using the following package name: n8n-nodes-beex Configure your Shopify credentials according to your store’s settings. You will need to provide: Your store subdomain Your Access Token Your App Secret Key For Beex users with platform access (if you need a trial, please contact frank@beexcc.com), go to the main dashboard and navigate to: Platform Settings → API KEY & Callback There, you can retrieve your API key and insert it into the corresponding Beex node within n8n. Requirements You need accounts for: Beex (omnichannel contact platform) Shopify (E-commerce platform builder) You need in Beex (Node): Portfolio ID Sequence ID The above determines the sequence of contact that customers are subjected to. How to customize You can also change the threshold to define from what extent you consider that a client is inactive. You can configure a particular sequence in Beex to contact your inactive customers to insert them into the node.

Who is this template for? Growth teams and SDR targeting small companies. In small companies, it is common for the founder to monitor the contact@ email, so generic emails can give you good results. What problem does this workflow solve? Get from a list of domain names to a list of email addresses. This workflow allows you to choose which email pattern you are looking for. So you can use it to find function emails like hr@ or accounting@. This is a great way to get in touch with your ICP. What this workflow does Think workflow will: Generate email candidates based on the domain name and root you are providing Check if those email addresses are valid using EmailListVerify Requirement This template uses: Google Sheet to handle input and output data EmailListVerify to discover email (from $0.05 per email) Setup (10 minutes) 1: Make a copy of the GoogleSheet template 2: In "[Input] pattern" sheet, write the root email you want to check, like contact or accounting 3: In "[Input] domain", put the domain for which you want to find email addresses. Write the domain without http or www in front. 4: Add your EmailListVerify API key to setting to the 3rd step 5: Update Google Sheet node to point to your copy of the template 6: Trigger the workflow

This n8n template posts a quick weekly snapshot to Slack so your team sees last week’s funnel movement at a glance. It counts how many contacts entered the Lead stage in the past week—and optionally reports closed-won deals from the same period. Perfect for GTM standups and Monday pipeline reviews. How it works A weekly schedule (e.g., Mondays 07:00) kicks things off. HubSpot → Get all contacts** pulls contacts with hs_v2_date_entered_lead. A filter keeps only those whose lead date is within the last 7 days. Summarize** counts the resulting leads. Slack* posts: “Last week we generated *X** leads.” (Optional branch) Deals: HubSpot → Get all deals with hs_is_closed_won and hs_closed_won_date. Filter to closed-won last week. Summarize to report count and (if mapped) total amount. How to use Connect HubSpot on the contacts and (optional) deals nodes. Connect Slack and pick the destination channel. In Schedule the report, set your preferred day/time. (Optional) For the Deals branch, include the amount property on “Get all deals” and set Summarize → sum over amount. Activate the workflow. Requirements HubSpot** (OAuth2) Slack** (OAuth2) Notes & customization Time windows:** Adjust the filter to different periods (e.g., last 14 or 30 days). More stages:** Duplicate the contacts branch for MQL/SQL or custom lifecycle events. Richer Slack message:** Add emojis, trend vs. prior week, or a tiny leaderboard by owner. Segments:** Split by country/industry using HubSpot lists or additional filters.

Chat with a Slack channel using AI. This workflow fetches the channel’s message history and lets you ask natural-language questions (“what were the decisions?”, “who’s blocked?”, “summarize yesterday”). The assistant only answers from the channel’s actual messages—no guessing. ⚙️ Setup Instructions 1️⃣ Set Up OpenAI Connection Go to OpenAI Platform Navigate to OpenAI Billing Add funds to your billing account Copy your API key into the OpenAI credentials in n8n 2️⃣ Connect Slack API Create an app → <https://api.slack.com/apps> OAuth & Permissions → add scopes you need to read channel history (typical: channels:history, groups:history, im:history, mpim:history, plus channels:read, groups:read, users:read. Add chat:write if you want the bot to reply in Slack.) Install the app to your workspace → copy the Bot User OAuth Token In n8n → Credentials → New → Slack OAuth2 API → paste token and save In the Slack History node, select your Slack credential and the Channel ID to read 🗣️ Example Questions You Can Ask “Give me a 5-bullet summary of the last 24 hours.” “What action items were assigned, and to whom?” “List open questions that haven’t been answered yet.” “Who was mentioned most this week?” “Summarize decisions from the last sprint planning.” “Show messages with the word ‘blocker’ from the past 2 days.” “What files/links were shared today?” 📬 Contact Need help customizing this or adding auto-replies back into Slack? 📧 robert@ynteractive.com 🔗 Robert Breen 🌐 ynteractive.com

This workflow instantly sends successful Stripe Checkout payments to RD Station Marketing by creating an Order & Payment Event for every confirmed transaction. It’s ideal for businesses that want to automate lead tracking, unify customer data, and trigger marketing automation flows at the moment of sale. Who’s it for This template is designed for online sellers, course creators, SaaS businesses, and marketers who use Stripe Checkout for payments and RD Station Marketing for lead management and automation. If you want real-time revenue data inside RD Station without manual work, this workflow is for you. How it works Stripe triggers the workflow whenever a Checkout Session is completed. The workflow checks the payment status and retrieves the list of purchased items. A new Order & Payment Event is sent to RD Station Marketing using the community node. You can extend the workflow to include customer details captured during checkout. How to set up Edit the Stripe Trigger and getItems nodes with your Stripe API keys. Add your RD Station Marketing credentials in the send2RDMKT node. In production, copy the workflow’s webhook URL and add it to your Stripe Webhook settings. Test the workflow with a real or test payment. Requirements A Stripe account and valid API keys An RD Station Marketing account Installation of the community node: RD Station Marketing for n8n Disclaimer: This workflow requires a self-hosted n8n instance because it uses a community node. How to customize the workflow You can extend the payload sent to RD Station Marketing to include additional fields such as customer name, email, coupon codes, or metadata collected in Stripe Checkout. Feel free to add routers, conditionals, or enrichment nodes depending on your marketing logic.

CI Artifact Completeness Gate (GitHub Push → Sentry Release Files → Artifact Validation → GitHub Commit Status Update) This workflow acts as a CI/CD quality gate for mobile app crash-symbolication artifacts. Whenever a new commit is pushed to GitHub, the workflow automatically checks the corresponding Sentry release and confirms whether required build artifacts (dSYM or ProGuard + mapping.txt) exist. If artifacts are complete, it updates the GitHub commit status to success, allowing the PR to be merged. If incomplete, the workflow fails silently (no commit status update), effectively blocking merges. ⚡ Quick Implementation Steps Configure GitHub Trigger for your repo. Add Sentry API credentials. Add GitHub API credentials. Update Sentry project URLs with your org_slug and proj_slug. Ensure your build pipeline uploads artifacts to Sentry before the workflow runs. Activate workflow. What It Does This workflow ensures your mobile crash-symbolication artifacts are fully present in Sentry for every release. When a new GitHub push occurs, the workflow: Reads the commit SHA and repo info from the GitHub Push event. Fetches the list of all releases from Sentry. Locates the correct release and fetches its uploaded artifact files. Runs custom validation logic: Success if: a .dSYM file exists *OR**\ both proguard.txt AND mapping.txt are present\ Failure if: neither dSYM nor both mapping artifacts exist. If validated successfully, the commit receives a success status on GitHub → PR can be merged. This provides a strong CI gate ensuring symbolication completeness and preventing un-debuggable releases. Who's It For Mobile development teams using Sentry for crash reporting. Engineering teams enforcing strict release-quality gates. DevOps teams wanting automated artifact validation. CI/CD pipeline engineers integrating Sentry symbolication checks. Teams who frequently upload dSYM or ProGuard mapping files. Requirements to Use This Workflow n8n instance (cloud or self-hosted) GitHub repository access (API credentials) Sentry project with: org_slug project_slug Auth Token with release access Build process that uploads artifacts to Sentry releases The release version must match the format expected by the workflow How It Works & How To Set Up Step 1: GitHub Push Trigger The GithubPushTrigger node listens for push events and extracts: Commit SHA Repository full name Branch Metadata No configuration required except selecting your GitHub credentials. Step 2: Configure Sentry Release Fetching Open Check Sentry Artifacts Releases and update: https://sentry.io/api/0/projects/<org_slug>/<proj_slug>/releases/ Make sure the Sentry credential is correctly selected. Step 3: Fetch Files for the Specific Release The next HTTP Request (Check Sentry Artifacts Files) uses a dynamic URL: https://sentry.io/api/0/projects/<org_slug>/<proj_slug>/releases/{{ $json.version }}/files/ Ensure your build pipeline sets version consistently with what Sentry receives. Step 4: Artifact Validation Logic The Verify Artifacts node runs JS logic to check: ✔ Condition 1 --- Valid dSYM Any file ending with .dSYM ✔ Condition 2 --- Valid Android Mapping proguard.txt\ mapping.txt ✖ Failure --- If neither set exists The Code node returns: { "status": "failure", "description": "Missing artifacts..." } This stops the workflow and prevents GitHub commit-status update. Step 5: Extract Commit Info & Prepare Update The Artifacts Validation and Get Repository Data node compiles: repo full name commit SHA validation status If validation failed → workflow ends here. Step 6: Update GitHub Commit Status The Update Status node hits: POST https://api.github.com/repos/<repoFullName>/statuses/<commitSHA> And sends: { "state": "success", "description": "Artifacts successfully verified." } This appears as a green check on your commit/PR. Step 7: Activate the Workflow Turn on the workflow to start enforcing symbolication completeness for all releases. How To Customize Nodes Change Sentry Project Edit URLs in both Sentry HTTP Request nodes: org_slug proj_slug Add Additional Artifact Rules Modify JS inside Verify Artifacts, e.g., require: native symbols extra asset files other platform artifacts Customize Commit Status Message Edit the request body in Update Status. Support Multiple Platforms / Multiple Releases Branch logic in: Code nodes Conditional checks Add-Ons (Optional Enhancements) Add Slack/Teams notifications when artifacts are missing. Auto-retry release checks after build completes. Merge-blocking PR checks for GitHub. Multi-platform artifact validation (iOS + Android + Unity). Upload artifacts directly from n8n. Store validation logs in Airtable or Google Sheets. Add GitHub Checks API rich reporting. Use Case Examples Block merges until symbolication artifacts are uploaded. Enforce strict Sentry release completeness for every build. Ensure Android mapping files always match the correct release version. Automatically verify multiple release types (debug, staging, production). Improve crash debugging by preventing un-symbolicated builds from shipping. Troubleshooting Guide | Issue | Possible Cause | Solution | |----------------------------|-----------------------------------------------|--------------------------------------------------------------------------| | Commit status never updates| Validation failed silently | Check logs from Verify Artifacts | | "version undefined" in URL | Sentry release list not matched | Ensure your build uploads a valid version | | 401 from Sentry API | Invalid/broken Sentry token | Regenerate token and update credentials | | Always failing validation | Artifact names differ (e.g., .dsym.zip) | Update RegEx patterns in Code node | | GitHub status API returns 404 | Missing repo permissions | Update GitHub credentials (repo status scope) | | Files array empty | Build system not uploading artifacts | Verify build → Sentry upload step | Need Help? If you need help customizing the artifact rules, integrating multiple platforms or automating Sentry/GitHub workflows, reach out to our n8n automation developers at WeblineIndia. We can assist with: Mobile CI/CD pipelines Sentry automation Multi-artifact validation GitHub PR quality-gates Advanced Code-node scripting And so much more. Happy automating! 🚀

🔄 Purpose of the Workflow: The Update-N8N workflow is designed to automatically trigger a (Portainer) webhook to update an N8N container, but only if a new version of N8N is available. ⚙️ Detailed Workflow Steps: 🕒 Scheduled Trigger The workflow runs every 16 hours at minute 8 using a schedule trigger node. 🌐 Fetch Latest N8N Version It sends an HTTP GET request to https://registry.npmjs.org/n8n/latest to retrieve the latest published N8N version from the npm registry. 📈 Get Currently Running Local Version Another HTTP GET request is sent to https://127.0.0.1/metrics (likely the Prometheus metrics endpoint of the local N8N instance) to extract the currently installed N8N version. 🧠 Version Comparison The workflow compares the local version (parsed from metrics) with the latest available version. 📬 Trigger Portainer Webhook If the versions do not match (i.e., an update is available), a POST request is sent to a webhook URL, which might be a Portainer webhook that redeploys or updates the N8N container/stack. ✅ Key Benefits: No manual checks or updates needed. Triggers only when a new version is available. Integrates seamlessly with Portainer via webhook. Secure configuration, e.g., disallowing unauthorized TLS certs for external requests.