n8n-nodes-wb-crm

WB-CRM community nodes for n8n — interact with the WB-CRM REST API and react to real-time CRM events.

Nodes

WB-CRM (Action Node)

Perform CRUD operations on WB-CRM resources.

| Resource | Operations | Required Scopes | |-----------|---------------------------------------|-----------------------------| | Lead | Create, Get, Get Many, Update, Delete | leads:read, leads:write | | Contact | Create, Get, Get Many, Update, Delete | contacts:read, contacts:write | | Task | Create, Get, Get Many, Update, Delete | tasks:read, tasks:write | | Project | Create, Get, Get Many, Update, Delete | projects:read, projects:write | | Campaign | Create, Get, Get Many, Update, Delete | campaigns:read, campaigns:write |

Get Many supports pagination (per_page, page) and filtering (search, status, project_uuid).

Note: Creating a Lead requires a Project UUID — the project the lead is assigned to. Use Project → Get Many to look up UUIDs, or copy them from the WB-CRM project detail page.

WB-CRM Trigger

Starts a workflow when a WB-CRM event fires in real-time (REST Hooks pattern — the node subscribes on activation, unsubscribes on deactivation).

Supported events:

• contact.created, contact.updated, contact.deleted
• lead.created, lead.updated, lead.deleted

Required scopes: webhooks:read, webhooks:write plus the read scope of whichever resource you listen to.

Installation

In n8n (Community Nodes)

1. Go to Settings → Community Nodes
2. Click Install a community node
3. Enter: n8n-nodes-wb-crm
4. Click Install

Self-hosted n8n (manual)

cd ~/.n8n
npm install n8n-nodes-wb-crm
# Restart n8n

Setup

1. In WB-CRM go to Settings → API Tokens and create a token. Select the scopes you need — at minimum leads:read / contacts:read for read-only workflows, add :write variants for mutations, and webhooks:read webhooks:write if you use the Trigger node.
2. Copy the token — it starts with wb_live_. It is shown only once.
3. In n8n go to Credentials → New → WB-CRM API and paste:
   • Base URL: https://api.wb-crm.net (or your self-hosted WB-CRM API domain)
   • API Token: the wb_live_... value
4. Click Test — it calls GET /health and should report success.

Webhook Signature Verification

When the WB-CRM Trigger node registers a subscription, WB-CRM returns a signing_secret. Each incoming webhook request includes an X-WB-Signature: sha256=<hmac> header — the node verifies this automatically using the stored secret and responds 401 on mismatch.

Rate Limits

• 60 requests / minute per IP (global hard limit)
• Monthly API-call quota per tenant (plan-dependent; Leads/Contacts write operations are exempt)
• The nodes surface 429 responses as errors — use n8n's built-in retry / error-output settings to handle them.

API Reference

The WB-CRM REST API is served from https://api.wb-crm.net/v1/. Authentication is via Bearer token (Authorization: Bearer wb_live_...). Connectivity can be verified with a public GET /health (no auth required).

For detailed endpoint reference, contact Wissen Beratung or check the WB-CRM admin console for your tenant's API section.

Development

git clone https://github.com/SyncMasta/wb-crm_n8n.git
cd wb-crm_n8n
npm install
npm run build    # compile TS + copy icons
npm run lint     # n8n-nodes-base community rules

License

MIT © Wissen Beratung