by Javier Quilez Cabello
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. How it works This workflow automates the registration of event participants in SinergiaCRM from a Google Sheets spreadsheet. A Google Sheets Trigger watches for new rows with pending registrations. The flow checks if the participant already exists in SinergiaCRM by NIF (national ID). If the contact exists, it creates a relationship and registers them for an event. If the contact doesn’t exist, it first creates the contact, then adds the relationship and event registration. Finally, it marks the row as "Processed" in the original spreadsheet to avoid duplicate entries. Set up steps Connect your Google Sheets and SinergiaCRM accounts using OAuth credentials. Replace the sample Google Sheet ID and worksheet name with your own. Ensure the spreadsheet contains the following columns: First name, Last name, NIF, Email, Event ID, Relation type, Registration date, and Relation date. Add the appropriate values in the "To CRM" and "Processed" columns to control processing logic. Review sticky notes inside the workflow for additional guidance and customization tips.
by Stephen Anindo
This template lets you selectively import n8n workflows from a GitHub repository, even when your repository uses deeply nested folder structures. Unlike most import workflows, this template does not load everything automatically. Instead, it: • Traverses all nested folders in your repository • Collects every workflow JSON file found • Dynamically generates a selection form • Allows you to choose exactly which workflows to load • Cleans incompatible fields for n8n API compatibility • Creates workflows directly in your instance This makes it ideal for users who: • Work across multiple n8n instances • Store workflows in structured GitHub directories (e.g. YYYY/MM/) • Want precise control over which workflows are restored • Manage staging, production, or client environments If you maintain workflows in GitHub and need controlled, selective imports, especially across structured folder hierarchies, this template is built for that use case.
by Rahul Joshi
Description: Stay on top of product issues with this n8n automation template that centralizes bug reports from Zendesk into a Google Sheets dashboard. The workflow filters only tickets tagged as “bug,” enriches them with reporter details, and updates a single source of truth for developers, QA teams, and support staff. Perfect for product managers, SaaS companies, and agile teams that need full visibility into bug trends and customer impact without wasting time on manual data entry. What This Template Does (Step-by-Step) ⚡ Manual Trigger or Scheduling Run on-demand after releases or bug triage meetings, or set up a schedule to auto-run daily/weekly. 📥 Fetch All Zendesk Tickets Retrieves tickets from your Zendesk account with full metadata. 🔍 Filter Bug Reports Only Processes only tickets tagged as “bug” to ensure relevance. 👤 Add Reporter Details Enriches bug reports with requester’s name, email, and profile data for impact tracking. 📊 Update Google Sheets Bug Tracker Stores bug details including Ticket No., Description, Status, Reporter Info, and Tags. ✔️ Smart update avoids duplicates by using description as a unique key. 🔁 Continuous Bug Aggregation Ensures all relevant bug reports are tracked and kept up-to-date in one central place. Key Features 🔍 Tag-based bug filtering 📊 Centralized bug dashboard in Google Sheets ⚡ Zendesk + Google Sheets integration with OAuth2 ♻️ Real-time sync with deduplication logic 🔐 Secure API credential handling Use Cases 🐞 Track and prioritize product bugs from customer reports 📊 Give QA and dev teams a shared bug dashboard 📩 Identify high-impact bugs based on affected customers 📈 Monitor bug frequency and trends for release planning Required Integrations Zendesk API (for ticket fetch + user info) Google Sheets (for storing/updating bug tracker) Why Use This Template? ✅ Centralizes bug visibility for all teams ✅ Saves hours of manual spreadsheet updates ✅ Improves prioritization with customer context ✅ Scales easily with more tags or categories ✅ Keeps bug tracking transparent across stakeholders
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by Christian Knoflach
What is it? A clean, extensible REST-style API routing template for n8n webhooks with up to 3 path levels. How does it work? Serves API routes via Webhooks with path variables Normalizes incoming requests into "global" _REQUEST and _CFG nodes Flexible routing with Switch-nodes based on path segments & request method Key features No setup required Supports multiple HTTP methods Global config via code node Separation of concern between config/request and implementation data flow Easy to extend Use cases Prototyping backend APIs via JSON-responses Serving interactive websites via HTML-nodes + TEXT responses
by Ivars Bariss
n8n workflow template: Strapi CMS v5 content API An importable n8n workflow that creates, updates, and lists entries on Strapi v5 through a single webhook. It talks to Strapi’s REST API with HTTP Request nodes and a Strapi Token API credential, so it stays compatible with v5 even though n8n’s built-in Strapi node targets older Strapi versions. What’s in this repo | File | Purpose | |------|---------| | strapi-v5-content-n8n-workflow.json | Workflow export — use for Import from File / Import from URL in n8n or when submitting to the n8n template gallery | Features One webhook, three actions** — action_type routes to create, update, or get_all. Any content type** — pass the plural API ID (content_type_plural) per request; no workflow fork per collection. Strapi v5** — uses documentId on update and REST URLs shaped for the v5 API. List with options* — get_all supports status, page_size, page_number, and populate= in the workflow. Clear failures* — checks Strapi error responses and can mark the execution failed via *Stop and Error**. Extra documentation** — after import, open the large sticky note on the canvas for full payload examples and security notes. Requirements n8n (self-hosted or cloud) Strapi v5 with a valid API token (Settings → API Tokens) and permissions for the collections you automate Quick start In n8n, choose Import workflow → From File and select strapi-v5-content-n8n-workflow.json (or import from this repo’s raw URL). Create a Strapi Token API credential in n8n and attach it to all HTTP Request nodes (Create, Update, Get all). Activate the workflow and copy the webhook’s Production URL (default path segment: strapi-v5-content). Change the path in the Webhook node if it clashes with another active workflow on the same instance. Send POST requests with a JSON body as below. Do not include a trailing slash on strapi_base_url. Webhook security (recommended before production) The template ships with no webhook authentication so you can test quickly. Before exposing the URL publicly, add authentication on the Webhook node (for example Header Auth with X-API-Key and a long random secret) and send that header on every call. The workflow intentionally does not hardcode your Strapi host: callers supply strapi_base_url in the body, so only trusted clients should be allowed. Request body reference All actions expect a JSON object (typically the webhook body). Common fields: | Field | Required | Description | |-------|----------|-------------| | action_type | Yes | "create" \| "update" \| "get_all" | | strapi_base_url | Yes | Strapi origin, no trailing slash (e.g. https://your-project.strapiapp.com) | | content_type_plural | Yes | Plural API ID from Content-Type Builder (e.g. articles) | get_all Optional: status (published / draft), page_size, page_number. create Required: data — object of field names and values matching your Strapi schema. update Required: documentId (Strapi v5), and data with fields to patch. Example shapes: { "action_type": "get_all", "strapi_base_url": "https://your-strapi.example.com", "content_type_plural": "articles", "status": "published", "page_size": 10, "page_number": 1 } { "action_type": "create", "strapi_base_url": "https://your-strapi.example.com", "content_type_plural": "articles", "data": { "title": "Hello", "slug": "hello" } } { "action_type": "update", "strapi_base_url": "https://your-strapi.example.com", "content_type_plural": "articles", "documentId": "<from get_all or Strapi admin>", "data": { "title": "Updated title" } } For full parameter notes, pagination examples, and MCP / AI agent usage, see the sticky note inside the imported workflow. License This project is released under the MIT License (Copyright © 2026 IBSolutions.dev).
by Adrian Kendall
Key Features Implements a simple round-robin distribution mechanism using a Data Table to track the last route used. Supports multiple downstream workflows or resources, balancing workload across them sequentially. Uses Switch and Code nodes for flexible routing logic. Designed for easy customization — replace placeholder “Route” nodes with sub-workflow calls or API triggers. Works with any trigger type, and includes merge logic to preserve input data. Nodes in Use | Node Name | Type | Purpose | |-------------------------------------------------|---------------|--------------------------------------------------------------------------| | When clicking ‘Execute workflow’ | Manual Trigger | Test entry point for manual execution. | | Calculate the next route to use | Data Table | Retrieves the last used route number. | | Code in JavaScript | Code | Increments the route counter (0–3 cycle). | | Update last_used in the datatable | Data Table | Updates the “Last_Used” field to track next route. | | Round Robin Router | Switch | Routes workflow execution to the correct path based on Last_Used value. | | Route 1 / Route 2 / Route 3 | NoOp | Placeholder routes — replace with your own workflows. | | Merge trigger data to pass to subworkflow if needed | Merge | Combines trigger data with routing data for sub-workflows. | | Sticky Notes | Annotations | Explain workflow logic and intended replacements. | How It Works The workflow starts when triggered manually (or by another workflow). The Data Table node fetches the current value of Last_Used, which identifies which route was last used. The Code node increments that value, resetting to 0 after 3, creating a round-robin cycle. The Data Table update node stores the new Last_Used value. The Switch node reads Last_Used and routes execution to the correct downstream branch. Each route can represent a duplicated workflow, resource, or API endpoint. Optionally, the Merge node reattaches trigger data before sending it to sub-workflows. Step-by-Step Trigger the workflow manually or via webhook/cron/etc. Retrieve current route index using the Data Table node. Increment route counter with the JavaScript Code node: If Last_Used = 3, it resets to 0. Otherwise, increments by 1. Update Data Table with the new Last_Used value. Route execution using the Switch node based on that value. Send data to corresponding subworkflow (Route 1, Route 2, Route 3). Replace the NoOp nodes with your target workflow or HTTP call nodes for real routing. Use Cases Distribute load across multiple API endpoints to prevent throttling. Run identical sub-workflows on different worker instances for parallel processing. Simulate load balancing during testing of N8N workflows. Sequentially alternate between external systems or servers handling similar tasks. Act as a proof-of-concept for balancing strategies before scaling up.
by Wayne Simpson
This template is a practical introduction to n8n Webhooks with built-in examples for all major HTTP methods and authentication types. It is designed as a learning resource to help you understand how webhooks work in n8n, how to connect them to a data store, and how to secure them properly. What’s included: Webhook nodes for GET, POST, PUT, PATCH, DELETE, and HEAD Demonstrations of Basic Auth, Header Auth, and JWT Auth Supabase integration for creating, retrieving, updating, and deleting rows Example response handling with Respond to Webhook nodes Sticky notes explaining each method, response type, and security option Use this template to: Learn how to configure and test webhooks in n8n Explore different authentication strategies Connect webhooks to a simple Supabase table Understand best practices for securing webhook endpoints This workflow is intended as an educational starting point. It shows you how to receive requests, map data, and return responses securely. For production use, adapt the structure, apply your own security policies, and extend the logic as needed. Check out the YouTube video here: https://www.youtube.com/watch?v=o6F36xsiuBk
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,