Prerequisites
- Self-hosted n8n v0.187 or later. n8n Cloud is not supported until cig.chat reaches the verified-nodes program.
- Owner role on the n8n instance.
N8N_COMMUNITY_PACKAGES_ENABLED=true on the n8n container (default since v0.187).- A bot-scoped cig.chat Bearer token (cig.chat → bot → Settings → API → Generate).
Steps
- Open n8n → click your avatar (bottom-left) → Settings → Community nodes.
- Click Install a community node.
- Enter the package name:
n8n-nodes-cigchat
- Tick "I understand the risks of installing unverified code from a public source" and click Install.
- Wait ~20 seconds — n8n will
npm install the package and reload itself. The cig.chat node now appears in the node panel under "Transform".
- Drag a cig.chat node into a workflow → Credential to connect with → Create New → cig.chat API:
- Base URL:
https://app.cig.chat/api (default)
- API Token: paste your bot-scoped Bearer token
Save. The credential validates against GET /flow/tags.
- Pick a Resource (Subscriber, Flow, Sending, …) and an Operation, fill the params, run.
Upgrades
To upgrade to a newer version: Settings → Community nodes → click the package → Update. n8n re-installs the latest published version and hot-reloads.
Uninstall
Settings → Community nodes → click the package → Uninstall. Workflows that reference cig.chat nodes will show a "node not found" error until reinstalled.
Troubleshooting
- "Failed to install" — check
N8N_COMMUNITY_PACKAGES_ENABLED=true and that your n8n process can reach the public npm registry.
- "Authentication failed" on first call — token expired or rotated. Regenerate at app.cig.chat → bot → Settings → API.
- "Add tag to subscriber failed" (HTTP 400) — the named tag does not exist. Add a Tag: Create step before Add Tag by Name, with
continueOnFail enabled (so it's a no-op if the tag already exists).
- "The email must be a valid email address" (HTTP 422) — cig.chat rejects placeholder domains like
example.com. Use a real domain in test fixtures.
