Arthur Braghetto
Engineer, Coder, Maker, Curious...
Templates by Arthur Braghetto
Control your n8n instance remotely with Telegram bot commands
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Your n8n Command Center in a Telegram Chat Remotely manage and operate your n8n instance from Telegram with powerful admin commands. This workflow connects your n8n instance with a Telegram Bot, giving you remote control over key admin operations through simple chat commands. 📱 You can List your workflows (workflows) Execute a workflow (execute [name]) Activate/deactivate workflows (activate [name], deactivate [name]) List past executions (executions [name]) Permanently delete archived workflows (cleanup) Create backups of all your workflows and credentials (backup) Get help (help) Get notified when a workflow fails and when n8n instance starts. This is especially useful for self-hosted instances when you want quick access to your automation environment from your mobile device. 📌 Notes backup only works on self-hosted setups. execute, activate, deactivate, and executions require the workflow name as argument. Workflows must contain the appropriate trigger nodes to be executed or activated. Commands and arguments are not case sensitive, there is no need to prefix with slash and spaces in the argument name are supported. ⚙️ Setup Create your credentials for Telegram API and n8n API. Edit all Telegram and n8n nodes. Select your credentials on them. On telegram nodes provide your chatid. Detailed step-by-step instructions are available in the workflow notes. In each workflow that fails and you want to receive a warning, configure this workflow as Error Workflow in its settings.
By Arthur BraghettoExtract Clean Web Content with Anti-Bot Fallback for AI Agents & Workflows
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Clean Web Content Extraction with Anti-Bot Fallback Extract clean and structured text from any webpage with optional fallback to an anti-bot scraping service. Ideal for AI tools and content workflows. 🧠 How it Works This sub-workflow enables reliable and clean scraping of any public webpage by simply passing a url parameter. It is designed to be embedded into other workflows or used as a tool for AI agents. It supports two output modes: fulltext: true — returns { title, text } with full page content fulltext: false — returns { title, url, content } with a short excerpt 💡 If the site is protected by anti-bot systems (like Cloudflare), it will automatically fallback to Scrape.do, a scraping API with a generous free plan. 🧩 This template requires the n8n-nodes-webpage-content-extractor community node, so it only works in self-hosted n8n environments. 🚀 Use Cases As a reusable sub-workflow, via Execute Sub-workflow node. As a tool for an AI Agent, compatible with Call n8n Workflow Tool. Perfect for chatbots, summarization workflows, or RSS/feed enrichment. Empowers your AI Agent with the ability to browse and extract readable content from websites automatically. 🔖 Parameters url (string): the webpage URL to scrape fulltext (boolean): set true for full page content, false for summarized output ⚙️ Setup Install the community node n8n-nodes-webpage-content-extractor in your self-hosted n8n instance. Create a free account at Scrape.do and obtain your API Token. In the workflow, locate the Scrape.do HTTP Request node and configure the credentials using your API Token. Detailed step-by-step instructions are available in the workflow notes. The Scrape.do API is only used as a fallback when conventional scraping fails, helping you preserve your API credits.
By Arthur BraghettoTransfer workflows with credentials & sub-workflow management between n8n instances
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Export Workflows Between n8n Instances Copy workflows between n8n instances — with optional credential export and automatic sub-workflow adjustments. 🧠 How it Works This workflow copies a selected workflow from a SOURCE n8n server to a TARGET server and guides you through safe checks: Name conflict check: If a workflow with the same name exists on the target the export is stopped. Sub-workflows: Detects calls to sub-workflows. If all sub-workflows exist on the target (same names), references are auto-updated and the export continues. If any are missing, the form shows what’s missing and lets you cancel or proceed anyway. Credentials: Detects nodes using credentials and lets you export those credentials along with the workflow. The workflow can only apply credential corrections for the credentials that you choose to export with it. At the end, the form lists which credentials were successfully exported. 💡 For in-depth behavior and edge cases, see the Notes inside the workflow (Setup, How It Works, and Credential Issues). 🚀 How to Use Run this workflow on your SOURCE server. Follow the step-by-step form: pick the workflow to export, choose whether to include credentials, and review sub-workflow checks. Done. ⚙️ Setup Create an n8n API key on both servers (SOURCE and TARGET). On the SOURCE server, create two n8n API credentials in n8n: one for SOURCE and one for TARGET (using the respective base URL and key). Configure the nodes in this workflow with these two credentials. Detailed step-by-step instructions are available in the workflow notes. ✅ Once configured, you’ll be ready to migrate workflows between servers in just a few clicks.
By Arthur Braghetto