n8n-nodes-noovichat

n8n community node for NooviChat — an integration for Chatwoot-based platforms with NooviChat CRM, sales pipeline, lead scoring and WhatsApp automation features.

Works with supported Chatwoot-compatible APIs too. Base operations (Conversations, Contacts, Messages, Inboxes, Agents, Teams, Labels, etc.) target the Chatwoot API shape. NooviChat-only resources require NooviChat.

Why NooviChat instead of other Chatwoot nodes?

Features

Base Resources (Chatwoot & NooviChat compatible)

For retry-safe message sends, set Idempotency Key to a stable value with
1-128 visible ASCII characters and no spaces. Reuse that same key when retrying
the message in the same account and conversation: NooviChat returns the original
message instead of sending a duplicate. Invalid keys return HTTP 422. Leaving the
field empty preserves the regular non-idempotent send behavior. A server that is
still completing the staged rollout returns HTTP 503 for keyed sends; retry only
after its administrator activates message idempotency.

⭐ Exclusive NooviChat Features

These resources are not available in Chatwoot and are unique to NooviChat. They power a full CRM and sales automation layer on top of the customer engagement platform.

🏆 Sales Pipeline & Cards

Full CRM pipeline management directly from n8n. Create pipelines, manage stages, move cards through the funnel and track every interaction.

⚠️ Closing a deal is never a side effect of a generic write. Won and lost
stages stay out of reach of the plain create/update path: Create refuses
to open a card straight into one, and a pipeline_stage sent through Bulk
Update's free-form JSON is refused with HTTP 422 whether it enters a
won/lost stage or takes a closed card out of one. That shortcut used to leave
the deal closed without its closing value or its entry in the opportunity
ledger, so the closing now has to be explicit: Mark Won, Mark Lost and
Reopen.

Nothing here changed for the operations you already use to move cards.
Move to Stage and Bulk Move are unaffected and still accept a won/lost
destination — they post to the dedicated move endpoint, which recognises the
target stage and performs the whole closing itself.

📅 Follow-ups & Activities

Never miss a follow-up again. Schedule tasks, track activities and automate reminders tied to cards and conversations.

🎯 Lead Scoring

Score contacts automatically based on rules and conditions. Build rule-based scoring engines and monitor results via dashboard.

📣 Campaigns

Send targeted messages at scale. Supports both one-off blasts and ongoing automated campaigns.

⏱ SLA Policies

Define, monitor and export SLA compliance metrics. Set resolution and first-response time targets per inbox.

💬 WhatsApp / WAHA Session Management

Manage WhatsApp sessions directly from your n8n workflows. Monitor connection status, reconnect automatically and configure Meta tracking.

Campaign (one-off & ongoing) and SLA policies exist in this node and not in @nooviai/noovichat-mcp. Keep using the Campaign / SLA resources here; do not expect MCP tools for them.

MCP dual path

@nooviai/noovichat-mcp is the LLM/operator surface for NooviChat extras (pipeline, follow-ups, WhatsApp, Captain, companies, internal chat). It does not register conversation/contact/message/inbox CRUD. This n8n node is the automation surface for that helpdesk CRUD and for Campaign/SLA. Captain, UAZAPI and Companies are on both packages.

Operator skills (tool names, dual-path): Noovi-AI/noovichat-skills.

Trigger Node

Automatically registers and removes account webhooks via the NooviChat API when you activate/deactivate a workflow.

Standard events (Chatwoot compatible):
conversation_status_changed, conversation_updated, conversation_created, contact_created, contact_updated, message_created, message_updated, webwidget_triggered, inbox_created, inbox_updated, conversation_typing_on, conversation_typing_off

⭐ Exclusive NooviChat events:
appointment.created, appointment.updated, appointment.confirmed, appointment.completed, appointment.cancelled, appointment.no_show, appointment.rescheduled, reminder.sent, reminder.failed, professional.created, professional.updated, service.created, service.updated, follow_up_scheduled, follow_up_sent, follow_up_failed, follow_up_cancelled, broadcast_follow_up_sent, broadcast_started, broadcast_completed

Pipeline-card webhooks use the dedicated pipeline-webhook API and are not account-webhook events. Optional webhook signature validation is available via shared secret.

Installation

Via n8n Community Nodes (Recommended)

1. Go to Settings > Community Nodes
2. Click Install
3. Enter @nooviai/n8n-nodes-noovichat
4. Click Install

Via npm (self-hosted n8n)

npm install @nooviai/n8n-nodes-noovichat

Restart n8n after installing for the node to appear.

Docker self-hosted

Install inside the running container:

docker exec -it <n8n_container> npm install @nooviai/n8n-nodes-noovichat
docker restart <n8n_container>

Or add to your docker-compose.yml with a custom extensions volume:

environment:
  - N8N_CUSTOM_EXTENSIONS=/home/node/.n8n/custom
volumes:
  - n8n_custom:/home/node/.n8n/custom

Verifying the installation

After restarting n8n, search for "NooviChat" in the node selector. If it doesn't appear, check the n8n logs:

docker logs <n8n_container> | grep -i noovichat

Troubleshooting

See TROUBLESHOOTING.md for a full guide covering:

• Field mapping reference (camelCase UI → snake_case API)
• API compatibility matrix (NooviChat version vs node version)
• Common errors and solutions (401, 404, 422, webhook issues)

Configuration

Same three values as the MCP server (.mcp.json.example): Base URL, API Access Token, Account ID. Token inherits the agent's role. Do not use a super_admin token for routine workflows.

Credentials — NooviChat API

1. In n8n: Credentials → Add Credential → NooviChat API
2. Fill in:
   • Base URL — instance root, no trailing slash (e.g. https://chat.example.com). Not /app and not /api.
   • API Access Token — NooviChat → Profile → API Access. Same token type the MCP uses (api_access_token header).
3. n8n tests the credential with GET /api/v1/profile.

Account ID is not stored in the credential. Each NooviChat node has an Account ID field (default 1, expressions allowed) so one credential can drive several accounts.

Base URL:     https://chat.example.com
API token:    Profile → API Access
Account ID:   per node (not in the credential)

Credentials — NooviChat Webhook API (optional)

Used only with the NooviChat Trigger node to validate incoming webhook signatures.

1. Add Credential > search NooviChat Webhook API
2. Fill in Webhook Secret — The same secret you configure in NooviChat webhooks settings

Workflow Examples

1. Lead Qualification Automation

Trigger: NooviChat Trigger — Contact Created
  → NooviChat — Card: Create (in "Leads" pipeline)
  → NooviChat — Follow-up: Create (due in 3 days)
  → NooviChat — Card: Get Lead Score
  → IF score >= 70
    → NooviChat — Card: Move to Stage ("Qualified")
    → NooviChat — Conversation: Assign (to Sales team)
  → ELSE
    → NooviChat — Conversation: Add Label ("nurturing")

2. Automatic Follow-up

Trigger: NooviChat Trigger — Follow-up Due
  → NooviChat — Conversation: Get
  → IF last message older than 24h
    → NooviChat — Message: Send (template "follow_up_24h")
    → NooviChat — Follow-up: Create (due in 48h)
  → ELSE
    → NooviChat — Follow-up: Cancel

3. Pipeline + WhatsApp (Card Won)

Trigger: NooviChat Trigger — Card Won
  → NooviChat — Contact: Get (contact linked to card)
  → NooviChat — Message: Send ("Congratulations! Your order was confirmed.")
  → NooviChat — Conversation: Add Label ("active-client")
  → NooviChat — Conversation: Toggle Status (resolved)

4. WAHA Session Monitoring

Schedule Trigger: Every 5 minutes
  → NooviChat — WAHA: Get Status (your WhatsApp inbox)
  → IF status != "WORKING"
    → NooviChat — WAHA: Reconnect
    → Wait: 30 seconds
    → NooviChat — WAHA: Get Status again
    → IF still != "WORKING"
      → Slack — Send message to #alerts: "WAHA disconnected on inbox X"

5. Weekly SLA Report

Schedule Trigger: Every Monday at 9am
  → NooviChat — SLA: Get Metrics (last 7 days)
  → IF hit_rate < 80%
    → Email — Send report to manager
    → NooviChat — Activity: Create ("Review SLA compliance")

Development

# Clone
git clone https://github.com/Noovi-AI/n8n-nodes-noovichat.git
cd n8n-nodes-noovichat

# Install dependencies
npm install

# Build
npm run build

# Watch mode
npm run dev

# Lint
npm run lint

# Tests
npm test
npm test -- --coverage

Local Testing with n8n

# Build
npm run build

# Link package globally
npm link

# In your n8n directory
npm link @nooviai/n8n-nodes-noovichat

Compatibility

Resources

• NooviChat Documentation
• NooviChat API Reference
• n8n Community Nodes Guide
• n8n Documentation

License

MIT — see LICENSE for details.

Development

This package lives in the NooviChat workspace. Shared agent policy:
AGENTS.md. Publish is versioned opt-in (G1/G2); the Chatwoot
time window does not apply.

Support

• Issues: GitHub Issues
• Email: contato@nooviai.com
• Website: noovichat.com