📤 Magic Inbox Send

📤 Send messages and workflows P2P to any Magic Inbox – direct recipient or fun public forums!

📤 Magic Inbox Send

AI-generated

Overview

This node, "Magic Inbox Send," enables sending messages and optionally workflows directly to a recipient's Magic Inbox URL or to a public forum. It supports peer-to-peer (P2P) communication by posting JSON payloads to specified webhook URLs. Users can share simple text messages or enrich their communication by attaching full n8n workflow exports for easy sharing and importing.

Common scenarios include:

  • Sharing automation workflows with teammates or community members.
  • Broadcasting announcements or requests in themed public forums.
  • Sending private messages or workflows securely to specific recipients via their Magic Inbox URLs.

Practical examples:

  • A user sends a helpful workflow along with a message to a "Help" forum to assist others.
  • An automation team shares a new scraper workflow privately with a colleague using their direct Magic Inbox URL.
  • Posting job offers or collaboration requests to the "Job" or "Business" forums for wider visibility.

Properties

Name Meaning
✨ Send to a forum Boolean toggle to send the message/workflow to a public forum instead of a private Magic Inbox URL.
🌐 Magic Inbox Destination URL The direct Magic Inbox webhook URL of the recipient. Required if not sending to a forum.
🗣️ Forum Select one of the predefined public forums ("General", "Job", "Help", "Business") to broadcast your message/workflow. Only shown if "Send to a forum" is enabled.
🔑 Destination API Key (Optional) Optional API key for authenticating with the destination endpoint if required.
👤 Your Identity Your display name or identifier shown to the recipient or forum readers (e.g., email or nickname).
✉️ Message The personal or public message content you want to send.
📦 Content Type Choose whether to send only the message or both the message and an attached workflow. Options: "Message Only" or "Message + Workflow".
🏷️ Workflow Name Name of the workflow being shared. Required if sending a workflow attachment.
🗂️ Workflow JSON Full JSON export of the n8n workflow to attach. Must be valid JSON. Required if sending a workflow attachment.
📒 P2P Address Book Text area to store favorite Magic Inbox or forum links for quick reference.
⏱️ Timeout (seconds) How long (in seconds) to wait for a response before timing out. Range: 5 to 300 seconds.
🔄 Retry on Failure Whether to automatically retry sending if the first attempt fails (useful for transient network issues).
🔢 Max Retries Maximum number of retry attempts if enabled. Range: 1 to 10.
🔍 Debug Mode Enables detailed logging output to the console for troubleshooting and advanced usage.

Output

The node outputs a single JSON object per input item describing the result of the transmission:

  • On success:

    • action: "magic_inbox_p2p_sent"
    • success: true
    • destination: The URL or forum endpoint used.
    • forum: The forum name if applicable, otherwise null.
    • from: Sender identity string.
    • contentType: Either "message_only" or "workflow_with_message".
    • sentAt: Timestamp when the message was sent.
    • attempts: Number of attempts made to send.
    • originalPayload: Metadata about the message length, presence of workflow, and workflow name.
    • response: The HTTP response body from the destination.
    • responseTime: Timestamp when response was received.
    • magicInboxProtocol: Protocol version string.
    • debugMode: Whether debug mode was enabled.

  • On failure:

    • action: "magic_inbox_p2p_send_failed"
    • success: false
    • error: Error message string.
    • errorType: Always "transmission_error".
    • failedAt: Timestamp of failure.

No binary data output is produced by this node.

Dependencies

  • Requires access to the internet or internal network to POST JSON payloads to Magic Inbox URLs or forum endpoints.
  • Optionally requires an API key credential if the destination endpoint enforces authentication.
  • No additional external libraries beyond standard HTTP request helpers bundled with n8n.
  • No environment variables are explicitly required, but network connectivity and correct URLs are essential.

Troubleshooting

  • Common Issues:

    • Missing destination URL or forum selection will cause an error.
    • Invalid JSON in the workflow attachment will cause a parsing error.
    • Network failures or unreachable URLs may cause transmission errors.
    • Authentication failures if the API key is missing or incorrect.

  • Error Messages:

    • "Please select a forum to send your message." — Occurs if "Send to a forum" is enabled but no forum is selected.
    • "Please provide a destination URL or enable "Send to a forum" and choose one." — Occurs if neither a destination URL nor a forum is provided.
    • "Invalid Workflow JSON: ..." — Indicates malformed JSON in the workflow attachment field.
    • Transmission errors with details logged if debug mode is enabled.

  • Resolutions:

    • Ensure either a valid destination URL or a forum is selected.
    • Validate workflow JSON before pasting it into the node.
    • Verify network connectivity and endpoint availability.
    • Provide correct API keys if required by the destination.
    • Enable debug mode to get detailed logs for diagnosing issues.

Links and References

Discussion