n8n-nodes-appmindmax

Читать на русском

An n8n community node package for the MAX messenger (dev.max.ru), built on top of the
official Bot API: https://dev.max.ru/docs-api

The package ships two nodes:

• APPMINDMAX — a regular action node for calling the API (send/update/delete messages,
  manage chats and members, manage bot commands, answer inline-button callbacks).
• APPMINDMAX Trigger — a trigger node that registers a Webhook subscription
  (POST /subscriptions) when the workflow is activated and removes it
  (DELETE /subscriptions) on deactivation, then receives incoming events. By default it
  subscribes to: User Joined Chat, User Left Chat, Bot Added to Chat, Bot Removed From Chat,
  Button Clicked — other event types are available in the Update Types list.

Installation

This package is not published to the public npm registry, so the built-in
Settings → Community Nodes → Install UI in n8n won't work for it directly. Instead, build a
custom n8n Docker image that compiles the node and loads it via N8N_CUSTOM_EXTENSIONS.

Docker (recommended)

The repository includes a multi-stage Dockerfile: the builder stage clones this repo and
compiles it with pnpm, the final stage is a plain docker.n8n.io/n8nio/n8n image with only the
compiled dist/ + package.json copied in (no node_modules, so the extra image size is a few
hundred KB, not the ~100 MB you'd get from shipping full dev dependencies).

If the repository is public, you can point docker-compose.yml straight at it as the build
context — no need to have the source checked out on the server at all:

services:
  n8n:
    build:
      context: https://github.com/alexbruin/appmindmax.git
      # args:
      #   APPMINDMAX_REF: v0.1.0   # pin to a tag/commit instead of `main`
    environment:
      - N8N_CUSTOM_EXTENSIONS=/home/node/custom-nodes/n8n-nodes-appmindmax
    # ...keep your existing volumes/ports/env

docker compose build --no-cache
docker compose up -d --force-recreate

If the repository is private, git clone/Docker's git context need credentials on the
server (deploy key or PAT). The simplest alternative without setting that up is to sync the
source to the server yourself and point the build context at the local copy instead:

rsync -avz --exclude node_modules --exclude dist ./ user@server:/opt/n8n-nodes-appmindmax/

services:
  n8n:
    build:
      context: /opt/n8n-nodes-appmindmax

Local build for development

npm install
npm run build

To try it against a local n8n instance:

npm link
cd ~/.n8n/custom   # or whatever directory N8N_CUSTOM_EXTENSIONS points to
npm link n8n-nodes-appmindmax

Credentials

Credential type APPMINDMAX API:

• Access Token — your bot's token from MAX: "Chat-bots" → your bot → "Advanced settings" →
  "Configure".
• Base URL — defaults to https://platform-api2.max.ru; leave it as-is.

MAX API quirks this node accounts for

• chat_id cannot be looked up directly — it only ever arrives via an event (bot_added,
  bot_started, etc.) delivered through Webhook/Long Polling. Use APPMINDMAX Trigger to
  capture chat_id from incoming events and persist it (e.g. via a separate workflow into a
  database) for later use in the APPMINDMAX node.
• Webhook and Long Polling cannot both be active at once — this package only implements Webhook
  (the mode MAX recommends for production).
• Uploading media attachments (image/video/audio/file) is a two-step process
  (POST /uploads → multipart/form-data upload) — the node handles this automatically
  whenever you set a Binary Property in Message → Send/Update.
• Rate limit: no more than 2 messages/answers per second per dialog/chat/channel — account for
  this in your workflow design (e.g. with Wait / Split in Batches).

Supported resources and operations

License

MIT