n8n-nodes-sendzen 1.0.2 → 1.0.3
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 +33 -7
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -38,6 +38,7 @@ SendZen provides an API on top of the **official WhatsApp Cloud API**, so you ca
|
|
|
38
38
|
SendZen helps developers and software platforms use WhatsApp reliably without dealing with all the Meta Cloud API complexity directly.
|
|
39
39
|
|
|
40
40
|
With this n8n node, you can:
|
|
41
|
+
|
|
41
42
|
- Send **session messages** (within 24-hour customer care window)
|
|
42
43
|
- Send **template messages** (for business-initiated conversations)
|
|
43
44
|
- Mark messages as read
|
|
@@ -76,9 +77,18 @@ To use this node, you need a **SendZen API Key**.
|
|
|
76
77
|
|
|
77
78
|
---
|
|
78
79
|
|
|
80
|
+
## Data & Security Notes
|
|
81
|
+
|
|
82
|
+
- This node sends message content, recipient phone numbers, template names, and template variables to SendZen to deliver WhatsApp messages.
|
|
83
|
+
- Store your SendZen API key only in **n8n Credentials**.
|
|
84
|
+
- For inbound messages, enable **webhook signature verification** (recommended) to prevent spoofed requests.
|
|
85
|
+
|
|
86
|
+
---
|
|
87
|
+
|
|
79
88
|
## Features
|
|
80
89
|
|
|
81
90
|
### SendZen Action Node
|
|
91
|
+
|
|
82
92
|
- **Send Session Message**
|
|
83
93
|
- Send free-form text messages within the active 24-hour window
|
|
84
94
|
- Supports URL previews and E.164 validation
|
|
@@ -94,6 +104,7 @@ To use this node, you need a **SendZen API Key**.
|
|
|
94
104
|
- Show “Typing…” to make automations feel more natural
|
|
95
105
|
|
|
96
106
|
### SendZen Trigger Node
|
|
107
|
+
|
|
97
108
|
- Receive inbound WhatsApp messages in real time via webhook
|
|
98
109
|
- Outputs full message payload (text, media, location, contacts)
|
|
99
110
|
- Simple webhook setup: copy URL from node → paste in SendZen dashboard
|
|
@@ -103,6 +114,7 @@ To use this node, you need a **SendZen API Key**.
|
|
|
103
114
|
## How to Use the SendZen Action Node
|
|
104
115
|
|
|
105
116
|
### Prerequisites
|
|
117
|
+
|
|
106
118
|
- A SendZen account
|
|
107
119
|
- A connected WhatsApp Business Account (WABA) in SendZen
|
|
108
120
|
- Access to n8n
|
|
@@ -137,6 +149,7 @@ To use this node, you need a **SendZen API Key**.
|
|
|
137
149
|
## How to Use the SendZen Trigger Node
|
|
138
150
|
|
|
139
151
|
### Prerequisites
|
|
152
|
+
|
|
140
153
|
- A SendZen account
|
|
141
154
|
- A connected WABA phone number
|
|
142
155
|
- Access to n8n
|
|
@@ -157,7 +170,7 @@ To enable signature verification in n8n:
|
|
|
157
170
|
|
|
158
171
|
If credentials are set, the trigger will return **401** for missing/invalid signatures.
|
|
159
172
|
|
|
160
|
-
Important: signature verification requires hashing the **raw request body**. Avoid any middleware/proxies that reformat/pretty-print the JSON payload.
|
|
173
|
+
Important: signature verification requires hashing the **raw request body**. Avoid any middleware/proxies that reformat/pretty-print the JSON payload. If you run n8n behind Cloudflare / nginx / API gateway, ensure it does not modify request body (no pretty-print, no re-encoding)
|
|
161
174
|
|
|
162
175
|
### Setup Process
|
|
163
176
|
|
|
@@ -166,6 +179,8 @@ Important: signature verification requires hashing the **raw request body**. Avo
|
|
|
166
179
|
- At the top of the node, find **Webhook URLs**
|
|
167
180
|
- Copy the **Production URL**
|
|
168
181
|
|
|
182
|
+
Tip: Use the **Test URL** while testing in the editor. After activating the workflow, set the **Production URL** in SendZen for live traffic.
|
|
183
|
+
|
|
169
184
|
2. **Add webhook URL in SendZen**
|
|
170
185
|
- Open SendZen dashboard webhook settings
|
|
171
186
|
- Paste the Production URL
|
|
@@ -186,6 +201,15 @@ Important: signature verification requires hashing the **raw request body**. Avo
|
|
|
186
201
|
- **Support automation**: Trigger on inbound support message, route based on keywords, reply
|
|
187
202
|
- **Payment reminders**: Trigger from billing system, send WhatsApp template
|
|
188
203
|
|
|
204
|
+
|
|
205
|
+
### Example 1: New lead → WhatsApp template
|
|
206
|
+
|
|
207
|
+
Trigger: CRM/New form submission → Send Template Message → Log result.
|
|
208
|
+
|
|
209
|
+
### Example 2: Inbound WhatsApp → Auto-reply + CRM
|
|
210
|
+
|
|
211
|
+
SendZen Trigger → IF keyword contains "pricing" → Send Session Message → Create lead in CRM.
|
|
212
|
+
|
|
189
213
|
---
|
|
190
214
|
|
|
191
215
|
## Best Practices
|
|
@@ -228,14 +252,16 @@ Important: signature verification requires hashing the **raw request body**. Avo
|
|
|
228
252
|
## Version history
|
|
229
253
|
|
|
230
254
|
### 1.0.1
|
|
231
|
-
|
|
232
|
-
|
|
255
|
+
|
|
256
|
+
- **Robustness:** Added comprehensive Jest test suite for Triggers, Actions, and Template Builders.
|
|
257
|
+
- **Optimization:** Reduced package size by excluding development files.
|
|
233
258
|
|
|
234
259
|
### 1.0.0
|
|
235
|
-
|
|
236
|
-
|
|
237
|
-
|
|
238
|
-
|
|
260
|
+
|
|
261
|
+
- Initial release
|
|
262
|
+
- Support for Session Messages, Templates, Mark as Read, Typing Indicators.
|
|
263
|
+
- Webhook Trigger support.
|
|
264
|
+
- Auto-discovery for WABA Accounts and Templates.
|
|
239
265
|
|
|
240
266
|
---
|
|
241
267
|
|