Description
n8n-nodes-clientify


Connect n8n to Clientify CRM via the Clientify REST API using API keys (Authorization: Token ).
This package stays aligned with the action catalog by generating actions/fields from a single shared connector spec at build time.
Under the hood, requests are executed directly via n8n’s HTTP request helper with Authorization: Token .
Installation
In n8n (GUI)
1. Go to Settings → Community Nodes
2. Click Install
3. Enter: n8n-nodes-clientify
4. Click I understand the risks and then Install
5. Restart n8n (important – it won’t show up until you do)
Via npm (Command Line)
cd ~/.n8n/nodes
npm install n8n-nodes-clientify
Restart n8n
Docker
Persist the nodes directory, or you’ll lose the node on restart:
volumes:
- n8n_data:/home/node/.n8n
Or enable auto-reinstall:
environment:
- N8NREINSTALLMISSING_PACKAGES=true
Prerequisites
You’ll need:
- n8n 2.x
- Node.js 20+
- A Clientify API key
- Use Test URL when executing on the canvas.
- Use Production URL for always-on external calls (runs show up in Executions).
- The trigger verifies the incoming payload
eventmatches the selected event type. - Use the field’s + button (variable picker), or
- Toggle = and use expressions like
{{$node["Create Contact"].json.id}}. - If the node does not appear after install, restart n8n.
- If the API returns
401, verify your API key. - If an operation requires an ID, ensure you mapped the correct numeric ID from a previous node.
- Clientify API docs: https://newapi.clientify.com/
- Triggers reference: LICENSE file for details.
Copyright (c) 2025 Clientify
Configuration
1. In n8n, go to Credentials → New
2. Search for “Clientify API”
3. Enter your API Key
4. Click Save
Nodes
Clientify (action node)
1. Add a node and search for Clientify.
2. Pick an Action.
3. Fill fields directly or map them from previous nodes using expressions.
Clientify Trigger (webhook helper)
Use this when you want a Clientify-branded trigger in the workflow. Under the hood it behaves like an n8n webhook:
For payload formats and examples, see TRIGGERS_REFERENCE.md.
Available Operations
Operations are generated from the bundled catalog (currently 81 actions).
Mapping (inputs from earlier steps)
Mapping is field-based: