Teleport workflows between n8n instances with Magic Inbox P2P system
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Telegram, Magic Inbox (community) and Magic Dev (community).
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Magic Inbox Send: uses Magic Inbox Send
- Message server n8n send (Magic Inbox Send): uses Magic Inbox Send
- Receiving message server n8n trigger (Magic Inbox): uses Magic Inbox
- Receiving message server n8n (Telegram): uses Telegram
- Magic Dev: uses Magic Dev
- Magic Inbox: uses Magic Inbox
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 3 community packages, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-magic-inbox is verified or supports 3.0 (used in Message server n8n send, 📤 Magic Inbox Send P2P).
- Check that n8n-nodes-magic-inbox is verified or supports 3.0 (used in Receiving message server n8n trigger, 📬 Magic Inbox P2P).
- Check that n8n-nodes-magic-dev is verified or supports 3.0 (used in 🪄 Magic Dev 5.2).
Nodes used (6)
- Telegram Trigger
n8n-nodes-base.telegramTrigger - Magic Inbox Send
n8n-nodes-magic-inbox.magicInboxSend - Magic Inbox
n8n-nodes-magic-inbox.magicInbox - Telegram
n8n-nodes-base.telegram - Manual Trigger
n8n-nodes-base.manualTrigger - Magic Dev
n8n-nodes-magic-dev.magicDev
From the author
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. 📬 Magic Inbox P2P for n8n — ✨ Instantly Teleport Workflows Magic Inbox is the simplest, most powerful way to TELEPORT your workflows, messages, or files…