Most-used N8Ntrigger workflows
- Control Your N8n Instance Remotely with Telegram Bot Commands (67 nodes)
- N8n Subworkflow Dependency Graph & Auto-tagging — n8n N8Ntrigger workflow (40 nodes)
- N8n Subworkflow Dependency Graph & Auto-tagging (http Request) (40 nodes)
- Multi-functional Discord Bot: Llama Ai, Image Generation & Knowledge Base — n8n N8Ntrigger workflow (36 nodes)
- My Workflow 69 (17 nodes)
- Notify on Server Restarts with Discord, Telegram, and Slack Alerts — n8n N8Ntrigger workflow (17 nodes)
- Automatic Workflow Backups to Gitlab with Gpt-4.1 Documentation Generation (15 nodes)
- Safely Update N8n with Version Checks and Telegram Notifications — n8n N8Ntrigger workflow (15 nodes)
- Gist:mxmzb (8 nodes)
- Splitout Executecommand — n8n N8Ntrigger workflow (7 nodes)
This workflow contains community nodes that are only compatible with the self-hosted version of n8n.
n8n Subworkflow Dependency Graph & Auto-Tagging. Uses httpRequest, n8n, scheduleTrigger, n8nTrigger. Scheduled trigger; 40 nodes.
As n8n instances scale, teams often lose track of sub-workflows—who uses them, where they are referenced, and whether they can be safely updated. This leads to inefficiencies like unnecessary copies o
Multi-functional Discord Bot with Llama AI, Image Generation, and Knowledge Base Integration 🤖🎨🧠
My workflow 69. Uses n8nTrigger, postgres, httpRequest. Event-driven trigger; 17 nodes.
This workflow triggers when the n8n instance starts, checks recent executions via the n8n API for unfinished runs, summarizes which workflows are affected, and posts a restart and incident summary to
This n8n template automatically backs up your workflows to a GitLab repository whenever they're updated or activated, and generates README documentation using AI. This workflow can be aslo added as a
This workflow is for system administrators or self-hosted n8n users who want to automatically check and update their n8n instance to the latest version — with Telegram notifications for every step. Th
Gist:Mxmzb. Uses n8n, dataTable, n8nTrigger. Event-driven trigger; 8 nodes.
Splitout Executecommand. Uses manualTrigger, splitOut, executeCommand, scheduleTrigger. Event-driven trigger; 7 nodes.
This workflow helps you set and maintain n8n credential overwrites by fetching credential schemas via the n8n REST API and registering overwrite values on every n8n startup using the credential overwr
Mattermost N8N. Uses n8nTrigger, mattermost. Event-driven trigger; 2 nodes.
12 of 12 workflows in this view · Browse all →
FAQ
How many n8n N8Ntrigger workflows are in the catalog?
12 n8n workflows in AutomationFlows currently use the N8Ntrigger integration — triggers, actions, or both.
How do I connect N8Ntrigger in n8n?
After importing the workflow JSON, n8n will prompt for N8Ntrigger credentials on the relevant nodes. AutomationFlows strips credential IDs before publishing — you'll add your own.
Can I combine these with other integrations?
Yes — most N8Ntrigger workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.