cigchat

n8n community node for cig.chat - 258 operations across 32 resources for messaging, subscribers, flows and shop management.

Documentation

n8n-nodes-cigchat

n8n community node for the cig.chat messaging platform. Wraps the same endpoints as the official Make.com app, generated from the same shared module table.

Features

  • 258 operations across 32 resources: Flow, Flow Tag, Flow User Field, Flow Bot Field, Flow AI Hub, Flow Segment, Flow Custom Events, Flow Conversation, Flow Shortcut, Flow Closing Note, WhatsApp Template, Facebook Utility Template, Template, Subscriber, Subscriber Cart, Sending, Ticket List, Team Label, Agent Group, Integration, OpenAI, Workspace, User, Shop Product, Shop Product Variant, Shop Product Type, Shop Product Vendor, Shop Product Tag, Shop Order, Shop Discount Code, Shop Location, Shop Business Hours
  • Declarative-style node - n8n handles request building and response parsing automatically
  • Bot-scoped Bearer authentication
  • Auto-pagination for list* operations (response data[] arrays are unwrapped)
  • Idempotent generator: re-emit all descriptions from scripts/gen-n8n-nodes.mjs after table edits

Installation

From npm (when published)

npm install n8n-nodes-cigchat

In n8n: Settings → Community Nodes → Install and enter n8n-nodes-cigchat.

From source

git clone https://github.com/cigchat/n8n-nodes-cigchat.git
cd n8n-nodes-cigchat
npm install
npm run build
npm link
# in your n8n install directory:
npm link n8n-nodes-cigchat

Restart n8n; the cig.chat node appears in the node panel under Transform.

Authentication

  1. In cig.chat, open the bot you want to control.
  2. Go to Settings → API and click Generate.
  3. In n8n, create a new credential of type cig.chat API and paste the token.
  4. The credential is validated by a probe call to GET /flow/tags?limit=1.

The token is bot-scoped - to control multiple bots, create one credential per bot.

Build & contribute

The node is generated from the shared module table at scripts/lib/modules-table.mjs (relative to the parent repo) - the same table that drives the Make.com app. To regenerate:

# From the parent repo root:
node scripts/gen-n8n-nodes.mjs

# In this package:
npm run build       # tsc + gulp build:icons
npm run lintfix     # n8n-nodes-base lint with auto-fix

Dropdowns

Every field that names a flow, tag, label, agent, agent group, AI agent, AI task,
bot field, user field, segment, product or WhatsApp template is a dropdown, filled
from your workspace over the same endpoints the Make app's RPCs use. Pick the
thing by name; the node sends its namespace or ID.

For a WhatsApp template send, choosing the template also fills Parameters > Key
with that template's own variable keys, exactly as the API spells them
(BODY_{{1}}, QUICK_REPLY_1, ...), and Namespace and Template Language
are resolved from the template when you leave them empty.

Known limitations

  • The two "Dynamic Fields" WhatsApp template operations are Make-only, and no longer need porting: the plain Send WhatsApp Template / Send WhatsApp Template by Channel User ID operations now do the same thing. Pick a template and its namespace and language are read from the template at send time, so the fields can stay empty; fill either one only to override.
  • No "Make an API Call" operation. The Make app carries a universal module for endpoints no module covers. n8n does not need one: point the built-in HTTP Request node at cig.chat, set Authentication to Predefined Credential Type and pick cig.chat API, and it signs the call with the same credential.
  • No webhook trigger node yet. cig.chat posts events to a configurable webhook URL - the trigger half of the integration is on the roadmap.

License

MIT - see LICENSE.

Support

Discussion