Skip to main content

Control your n8n instance remotely with Telegram bot commands

Workflow preview

Workflow preview
100%
Control your n8n instance remotely with Telegram bot commands preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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 Te...

Best for

  • DevOps automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.telegramtrigger, n8n-nodes-base.set, n8n-nodes-base.switch, n8n-nodes-base.if, n8n-nodes-base.n8n, n8n-nodes-base.telegram, n8n-nodes-base.filter, n8n-nodes-base.code

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Arthur Braghetto.

Original n8n.io source

1.1 Workflow description

Title
Control your n8n instance remotely with Telegram bot commands
Workflow name
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.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Telegram Trigger

Type / Role
n8n-nodes-base.telegramTrigger - telegramTrigger
Config choices
Version 1.2

Block 2 - Cmd Parse

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 3 - Cmd Switch

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.2

Block 4 - Execute Arg

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 5 - Activate Workflow

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 6 - Deactivate Workflow

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 7 - Activate Arg

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 8 - Deactivate Arg

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 9 - Arg Error

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 10 - Cmd Error

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 11 - Executed

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 12 - Activated

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 13 - Deactivated

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 14 - Workflow Name Error

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 15 - List Workflows 1

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 16 - List Workflows 2

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 17 - List Workflows 3

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 18 - If Inactive

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 19 - If Active

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 20 - Workflow Active Error

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 21 - Workflow Inactive Error

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 22 - List Workflows

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 23 - Help

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 24 - Workflow List

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Showing the first 24 of 67 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Control your n8n instance remotely with Telegram bot commands
Complexity advanced
Nodes 67
Categories DevOps
Author Arthur Braghetto
Published 13 Jun 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/4928/4928.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Control your n8n instance remotely with Telegram bot commands do?

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 Te...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.