@clubmega/n8n-nodes-mega

This is an n8n community node that lets you use MEGA in your n8n workflows.

See MEGA API coverage for the current resource matrix, output contract and deliberate exclusions.

MEGA is a customer engagement platform that helps businesses manage customer conversations across multiple channels. This node provides comprehensive integration with the MEGA API, allowing you to automate customer support workflows, manage contacts, handle conversations, and more.

n8n is a fair-code licensed workflow automation platform.

Installation
Nodes
Operations
Credentials
Compatibility
Usage
Resources

Installation

Follow the installation guide in the n8n community nodes documentation.

Use this package name to install:

@clubmega/n8n-nodes-mega

Nodes

This package includes two nodes:

MEGA

The main node for interacting with the MEGA API. Supports all CRUD operations for managing your MEGA instance.

MEGA Trigger

A webhook trigger node that listens for MEGA events. Automatically registers and manages webhooks in your MEGA instance.

Operations

Account

Account User

• Create: Associate a user with an account (Platform API)
• Delete: Remove a user from an account (Platform API)
• List: List all users associated with an account (Platform API)

Agent

In Agent create and update, the Role dropdown includes account custom roles.
Selecting a custom role sends custom_role_id automatically.

Agent Bot

Agent Bot (Account)

Supports two bot types: Webhook (receives events via URL) and Typebot (powered by Typebot with trigger configuration). When creating a Typebot, you can configure the API URL, public name, trigger type (all/keyword), and keyword matching options.

Applied SLA

Audit Log

Automation Rule

The Create operation uses visual builders for conditions and actions:

Trigger Events: Conversation Created, Conversation Opened, Conversation Resolved, Conversation Updated, Message Created.

Condition Builder — Add one or more conditions, each with:

• Attribute (18 options): Status, Priority, Assignee, Team, Inbox, Labels, Email, Phone Number, Content, Message Type, Country, Browser Language, Conversation Language, City, Company, Referer, Mail Subject, Contact Label.
• Operator (10 options): Equal To, Not Equal To, Contains, Does Not Contain, Starts With, Is Present, Is Not Present, Is Greater Than, Is Less Than, Days Before.
• Values: Contextual dropdowns — multi-select for Status, Priority, and Message Type; free-text for all other attributes.
• Condition Logic: Combine all conditions with AND (all must match) or OR (any can match).

Action Builder — Add one or more actions (21 types), each showing contextual parameter fields:

Calendar Event

Google Calendar Integration / Sync

Campaign

Canned Response

Captain (AI)

Captain resources need the Captain feature on the account.

Chat Room

Company

Contact

Create and Update also accept Ignore Greeting, Ignore CSAT and Ignore Agent Name. They skip the inbox greeting, the CSAT survey and the agent name prefix for that contact, and only apply to Evolution, WAHA and UAZAPI WhatsApp inboxes.

Contact Note

Conversation

WhatsApp Cloud templates

Send with Template lists only templates approved for the selected inbox. List selections preserve both the template name and language; a saved workflow that contains only the legacy template name continues to work when that name identifies exactly one approved language.

Approved templates containing component types or header formats that this node cannot safely serialize are omitted from the selector, while other compatible templates continue to load.

Guided Inputs is the default. After selecting Account, Inbox and Template, n8n reloads Template Values and shows one field for each value required by that exact approved template. For example, an IMAGE header plus hola {{1}} shows Header image URL and Variable — {{1}}; footer text, call permission and static buttons remain informational and never create editable fields. Values accept n8n expressions normally.

For header media, enter a public URL in the generated field or enter binary:data (replacing data with the n8n binary property name). Document templates generate one additional optional filename field; image and video templates do not. Switch Input Mode to Advanced Components for typed date-time values, low-level troubleshooting or explicit component control. Workflows saved by earlier versions with Components continue to execute through the legacy parser even though Guided Inputs is now the default.

Add the dynamic components shown in Template Structure:

• For positional body variables such as {{1}}, add values in numeric order. For named variables such as {{customer_name}}, also enter the exact Parameter Name.
• A Date Time value is sent as WhatsApp's enhanced date_time object and requires a human-readable fallback value. Use Advanced Components for manual date-time entry; guided expressions may also return { "type": "date_time", "value": "2026-07-11T12:00:00Z", "fallback_value": "July 11, 2026" }.
• IMAGE, VIDEO and DOCUMENT headers accept an externally reachable HTTP(S) URL or an n8n binary field. Literal local/private/link-local addresses are rejected, but the node does not perform DNS resolution. Binary input is uploaded to MEGA only after the full template input validates; documents may include a safe filename displayed by WhatsApp.
• Add only dynamic URL or Copy Code buttons and use their actual zero-based template index, including indexes after static buttons.

Example processed parameters for a document template:

{
  "body": { "customer_name": "Ana" },
  "header": {
    "media_url": "https://files.example.com/invoice.pdf",
    "media_type": "document",
    "media_name": "invoice.pdf"
  },
  "buttons": [
    { "type": "quick_reply" },
    { "type": "url", "parameter": "order-42" }
  ]
}

The operation returns the MEGA message record after it is created. WhatsApp delivery is asynchronous, so a successful node execution does not by itself confirm delivery; inspect the later message status or delivery/error events in MEGA.

CSAT Response

Custom Attribute

Custom Role

Help Center Article / Category

Both work inside a portal, identified by its slug.

Inbox

⚡ These operations are only available with MEGA

Kanban Automation

Kanban Config

Kanban Funnel

Kanban Item

• CRUD + movement: List, Batch, Get, Create, Update, Delete, Move to Stage, Move, Reorder
• Search + reports: Search, Filter, Reports, Report Export (CSV), Debug, Export CSV
• Checklist: Create/Get/Update/Toggle/Delete checklist tasks, assign/remove agent, duplicate, search, progress by agent
• Notes: Create/Get/Update/Delete notes
• Attachments: List/Upload/Delete item attachments and note attachments
• Assignment: Assign/Remove/Get assigned agents
• Timing + status: Change status, Time Report, Stage Time Breakdown, Counts
• Bulk: Bulk Move Items, Bulk Assign Agent, Bulk Set Priority
• CSV import: Import Preview, Import CSV (binary file input)

Kanban Stage

• List: List stages by funnel
• Get: Get stage details
• Create: Create a stage in a funnel
• Update: Update stage data
• Delete: Delete a stage and optionally move items to a fallback stage

Kanban UX Notes

• Kanban resources use a guided-first UX for common fields and filters.
• Advanced JSON fields are hidden by default and can be revealed using Show Advanced JSON Options.
• In Kanban Item and Kanban Funnel, advanced query/body JSON overrides guided values when both are provided.
• Kanban Item Create and Update accept funnel Custom Attributes as name/value pairs. On Update, attributes you don't send keep their stored values.
• In Kanban Stage, Kanban Config, and Kanban Automation, create/update payloads are provided through the advanced JSON field.

Label

Macro

Notification

Notification operations act on the user that owns the access token.

Profile

Message Template

Platform Banner

Platform banners allow system administrators to display important notifications or announcements to users across the platform. Users can view and dismiss banners they've seen.

Platform Banner (Platform API)

Platform API operations require platform-level authentication and permissions. These operations are for system administrators to manage banners that will be displayed across all accounts.

The Feature Announcement type opens as a panel over the dashboard and requires a Video URL: a YouTube, Vimeo, Loom, Arcade, Bunny, Guidejar or CodePen link, or the link of an image or video file.

Scheduled Message

Outbound Message

Scheduled Outbound Message

Search

Task (Activity) and Activity Type

Team

User

WhatsApp Group

Works on WhatsApp group conversations (Evolution, WAHA and UAZapi inboxes).

Trigger Events

The MEGA Trigger node supports the following webhook events:

MEGA sends every new message as message_created. Message Incoming and Message Outgoing register that event and the trigger starts the workflow only for messages in the selected direction. Contact, inbox and chat room events are account-wide, so the Inbox filter does not apply to them.

Provider Event Received is still listed as deprecated so saved triggers open, but MEGA no longer sends it and the trigger ignores it.

Credentials

To authenticate with MEGA, you need:

1. MEGA API URL

The base URL of your MEGA instance (e.g., https://app.mega.com or your self-hosted URL).

2. Access Token

A Personal Access Token from your MEGA profile:

1. Log in to your MEGA dashboard
2. Go to Profile Settings (click your avatar → Profile settings)
3. Navigate all the way down to Access Token
4. Copy your token

The token is sent as the Api-Access-Token header with each request.

Compatibility

• Minimum n8n version: 1.0.0
• Tested with: n8n 1.x and n8n 2.34.5 (using n8n-workflow 2.34.2)
• Node.js for n8n 2.34.5: 22.22 or later (n8n requirement)
• MEGA version: Compatible with MEGA v4.x and later
• MEGA exclusive features: WhatsApp provider operations, and additional webhook events

Usage

Basic Workflow: Auto-respond to New Conversations

1. Add a Mega Trigger node
2. Select your account and choose "Conversation Created" event
3. Connect to a MEGA node
4. Set resource to "Conversation" and operation to "Send Message"
5. Use the conversation ID from the trigger output

Working with Contacts

The Contact resource supports E.164 phone number format validation (e.g., +5511999999999). You can also set social profiles and custom attributes when creating or updating contacts.

Using Resource Locators

All resources support two selection modes:

• From List: Browse and search available items (accounts, inboxes, conversations, etc.)
• By ID: Enter the ID directly for dynamic workflows

Custom Attributes

Custom attributes can be specified in three ways:

1. Definition mode: Select from existing attribute definitions
2. Key-pair mode: Enter key-value pairs manually
3. JSON mode: Provide a JSON object for complex structures

AI Tool Usage

This node is enabled as an n8n AI tool (usableAsTool: true), allowing it to be used with AI agents for intelligent automation workflows.

Resources

• Complete MEGA resource and endpoint reference
• Architecture and contract verification
• n8n Community Nodes Documentation

License

MIT

Made with ❤️ by Mega

Node type IDs

From 0.14.0 the nodes are registered as @clubmega/n8n-nodes-mega.mega and @clubmega/n8n-nodes-mega.megaTrigger. Earlier versions used ...chatwoot and ...chatwootTrigger, which MEGA inherited from its original codebase and led AI assistants (for example through the n8n MCP server) to treat the node as Chatwoot.

The previous types are still installed as hidden aliases with the same parameters, so existing workflows, active triggers and credentials keep working without changes. New nodes added from the panel use the new types. Migrating an existing workflow is optional: replace @clubmega/n8n-nodes-mega.chatwoot with @clubmega/n8n-nodes-mega.mega (and chatwootTrigger with megaTrigger) in its JSON. Re-activate a migrated trigger workflow so it re-registers its webhook.

The Platform credential keeps its megaChatwootPlatformApi type name for the same compatibility reason; it is shown as MEGA Platform API.