n8n-nodes-didar-crm 0.0.24 → 0.0.25
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +32 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -173,7 +173,7 @@ n8n-nodes-didar-crm/
|
|
|
173
173
|
│ ├── note/ # Note operations
|
|
174
174
|
│ ├── case/ # Case operations
|
|
175
175
|
│ ├── product/ # Product operations
|
|
176
|
-
│ └──
|
|
176
|
+
│ └── supplementary/ # Complementary actions (base info, didaryab, popup caller ID)
|
|
177
177
|
│── lib/
|
|
178
178
|
│ ├── http.ts # Request helper
|
|
179
179
|
│ └── loadOptions.ts # Dropdown population
|
|
@@ -181,6 +181,37 @@ n8n-nodes-didar-crm/
|
|
|
181
181
|
|
|
182
182
|
---
|
|
183
183
|
|
|
184
|
+
## ✅ Compatibility
|
|
185
|
+
|
|
186
|
+
- n8n: v1.20.0+ (Community Nodes enabled)
|
|
187
|
+
- Node.js: v18+
|
|
188
|
+
- Didar CRM account with API access
|
|
189
|
+
|
|
190
|
+
---
|
|
191
|
+
|
|
192
|
+
## 🧪 Quick Start Checklist
|
|
193
|
+
|
|
194
|
+
1. Install and build this package.
|
|
195
|
+
2. In n8n, create credentials of type "Didar API".
|
|
196
|
+
- Set `Base URL` (default `https://app.didar.me`).
|
|
197
|
+
- Set `API Key`.
|
|
198
|
+
- Optional: enable `Use Cookie Header` and set `Cookie` if your instance requires it.
|
|
199
|
+
- Use the Test button to verify connectivity.
|
|
200
|
+
3. Add the `Didar CRM` node and pick a resource/operation.
|
|
201
|
+
4. For dropdown fields (pipelines, stages, owners, activity types), you can either pick from list or provide manual IDs.
|
|
202
|
+
5. For lists (IDs, labels, phones, emails, etc.), you can provide JSON arrays or comma/newline separated strings.
|
|
203
|
+
|
|
204
|
+
---
|
|
205
|
+
|
|
206
|
+
## 🧯 Troubleshooting
|
|
207
|
+
|
|
208
|
+
- 401/403 errors: re-check `API Key`, `Base URL`, and whether cookie auth is required.
|
|
209
|
+
- Empty dropdowns: ensure the credential test passes and your user has permission to view the entities.
|
|
210
|
+
- Webhook not triggering: the trigger node accepts only POST; verify the sender uses POST and sends valid JSON.
|
|
211
|
+
- Popup Caller ID: requires a separate fixed API key provided by Didar.
|
|
212
|
+
|
|
213
|
+
---
|
|
214
|
+
|
|
184
215
|
## 🛠 Development
|
|
185
216
|
|
|
186
217
|
1. Clone the repo
|