Skip to main content

Teleport workflows between n8n instances with Magic Inbox P2P system

Workflow preview

Workflow preview
100%
Teleport workflows between n8n instances with Magic Inbox P2P system 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. Magic Inbox P2P for n8n — Instantly Teleport Workflows Magic Inbox is the simplest, most po...

Best for

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

Tools used

n8n-nodes-base.telegramtrigger, n8n-nodes-magic-inbox.magicinboxsend, n8n-nodes-magic-inbox.magicinbox, n8n-nodes-base.stickynote, n8n-nodes-base.telegram, n8n-nodes-base.manualtrigger, n8n-nodes-magic-dev.magicdev

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Teleport workflows between n8n instances with Magic Inbox P2P system
Workflow name
Teleport workflows between n8n instances with Magic Inbox P2P system

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 between any two n8n instances — instantly, securely, and with no central server.

All you need:

A Magic Inbox receiver ("Inbox" node, webhook trigger) A Magic Inbox sender ("Send" node, transformer) A trusted peer’s webhook URL — and the magic happens! ✨ Teleport Your Automation 🚀 Click, Send, Teleport: Send a workflow or any file to another n8n, anywhere in the world, with a single node. 🪄 No cloud, no barriers: Pure peer-to-peer transfer. Your workflow arrives instantly and privately on the recipient's machine, ready-to-use and auto-imported if you wish. 🔁 Collaborate with your team: Share, delegate, or migrate automations on demand, without manual copy-paste or API scripting. 🔹 Features 📤 Teleport workflows, files, and secure messages P2P between n8n servers 📬 Receive and auto-import (optional) any incoming workflow — no extra steps! ⚡️ Works across docker, cloud, self-hosted — anywhere n8n runs 🔐 Whitelist option: restrict trusted senders 🔄 Simple vs Advanced: auto-import for speed, raw mode for power users 🛠️ Installation npm: npm install n8n-nodes-magic-inbox

Docker volume: cd /var/lib/docker/volumes/n8n_data/_data/nodes/ npm install n8n-nodes-magic-inbox docker restart

🚦 Usage: Teleport in 3 Steps Create a workflow on n8n-A with your favorite nodes Add Magic Inbox Send. Set "Destination Magic Inbox URL" to your teammate’s or other n8n’s Inbox node webhook. Choose content type: Workflow + Message for teleportation. On n8n-B: Add and enable a Magic Inbox node (receiver) in any workflow. When you hit “Send” on n8n-A, your workflow is instantly delivered/teleported! Auto-import enabled? The workflow appears, active, in the recipient’s n8n — like magic 🪄

⚙️ Main Parameters Destination Magic Inbox URL: Where to teleport your automation (recipient's webhook). Workflow JSON: Paste the full export from n8n’s workflow page (no manual API!). Auto Import: If enabled, new workflows are instantly usable by the recipient. Whitelist: Allow only trusted emails/IDs as senders. 📝 Example — Teleport a Workflow On n8n-A:

Export your workflow as JSON (from the workflow menu) Use Magic Inbox Send with destination URL from n8n-B’s Inbox node Attach the exported JSON and an optional message On n8n-B:

Magic Inbox node receives, parses, and (optionally) auto-imports the workflow into your library No code, no copy-paste, no cloud — just teleport!

🐞 Bug Report / Contribute Email : [email protected] 📜 License MIT © Charles Magic Dev

🎁 Magic Dev

📋 1. Presentation and Prerequisites - Quick Without Blabla

Essential: manual trigger + n8n-nodes-magic-dev

🤖 Magic Mapping → A prompt, instance URL, N8N API key, OpenRouter API to teleport your workflow to your instance.

🎁 Creator Mapping → Instance URL, N8N API key and a random creator workflow teleports to your instance.

🔑 Quest Mapping → Instance URL, N8N API key, secret code found in Creator Mapping to win a premium workflow.

🗃️ Magic Market: PUBLISH — Share your workflow with a public Google Sheets URL. SEARCH — Find workflows to teleport by keyword in our community database.

⚠️ REQUIRED! Your Google Sheet must have a column named WORKFLOW (all caps, no spaces).

Do not use any other column name — otherwise mapping and teleportation will fail.

Each row must contain a single n8n workflow as a JSON string in that column.

Always check the column header before using Magic Market Teleport!

⭐ FEEDBACK: Optional rating system (1-20 stars) + comments available in all modes

🤝 Creators: Want to collaborate? Contact me via Telegram @magicdev_bot! 💝

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 - Message server n8n trigger

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

Block 2 - Message server n8n send

Type / Role
n8n-nodes-magic-inbox.magicInboxSend - magicInboxSend
Config choices
Version 7.6

Block 3 - Receiving message server n8n trigger

Type / Role
n8n-nodes-magic-inbox.magicInbox - magicInbox
Config choices
Version 7.6

Block 4 - 📤 Magic Inbox Send P2P

Type / Role
n8n-nodes-magic-inbox.magicInboxSend - magicInboxSend
Config choices
Version 7.6

Block 5 - 📬 Magic Inbox P2P

Type / Role
n8n-nodes-magic-inbox.magicInbox - magicInbox
Config choices
Version 7.6

Block 6 - Sticky Note – Magic Inbox

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

Block 7 - Sticky Note – Features

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

Block 8 - Sticky Note – Modular

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

Block 9 - Sticky Note – P2P Send

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

Block 10 - Sticky Note – P2P Receive

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

Block 11 - Receiving message server n8n

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

Block 12 - When clicking

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

Block 13 - Sticky Note – Features1

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

Block 14 - Sticky Note – Magic Inbox1

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

Block 15 - Sticky Note – Modular2

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

Block 16 - 🪄 Magic Dev 5.2

Type / Role
n8n-nodes-magic-dev.magicDev - magicDev
Config choices
Version 5.2

3. Summary Table

Workflow Teleport workflows between n8n instances with Magic Inbox P2P system
Complexity advanced
Nodes 16
Categories DevOps
Author Charles
Published 04 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6960/6960.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 Teleport workflows between n8n instances with Magic Inbox P2P system do?

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

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.