Package Information
Available Nodes
Documentation generating…
Documentation
Kudosity for n8n
Send SMS, MMS, WhatsApp, and RCS messages — and receive inbound events — directly inside your n8n workflows using your Kudosity account.
What you can do
| Action | Description |
|---|---|
| Send SMS | Send a text message to any mobile number |
| Send MMS | Send a message with an image, video, or document |
| Send WhatsApp | Send a plain text or pre-approved template message |
| Send RCS | Send a rich message (with optional SMS fallback) |
| Receive Events | Trigger a workflow when an SMS/MMS arrives, a delivery status changes, a contact opts out, or a link is clicked |
Before you start
You will need:
- An active Kudosity account with API access enabled
- Your Kudosity API Key (see below)
- An n8n instance with this package installed: Settings → Community nodes → Install, enter
n8n-nodes-kudosity-messaging. (Notn8n-nodes-kudosity— that is an older, unrelated package.)
Step 1 — Get your Kudosity API Key
- Log in to your Kudosity account at app.kudosity.com
- Go to Settings → API
- Copy your API Key — keep it somewhere safe, you'll need it in the next step
Step 2 — Add your API Key to n8n
- In n8n, open any workflow and add a Kudosity V2 node (or Kudosity V2 Trigger node)
- Click Create new credential in the credential dropdown
- Paste your API Key into the API Key field
- Click Save — n8n will verify the key automatically
Your credential is now saved and can be reused across all your Kudosity nodes.
Step 3 — Send a message
Send an SMS
- Add a Kudosity V2 node to your workflow
- Select your saved credential
- Set Operation to Send SMS
- Fill in the fields:
| Field | Description | Example |
|---|---|---|
| Recipient Phone | The mobile number to send to (include country code) | +61412345678 |
| Sender | Your registered sender number or Sender ID | +61481074185 or MYBRAND |
| Message | The text to send (over 160 characters will be split) | Hi John, your order is ready! |
| Message Reference | (Optional) Your own tracking ID | order-1234 |
Send an MMS
- Set Operation to Send MMS
- Fill in the fields:
| Field | Description | Example |
|---|---|---|
| Recipient Phone | Mobile number (with country code) | +61412345678 |
| Sender | Registered sender number | +61481074185 |
| Media URL | A publicly accessible link to your image, video, or document | https://example.com/promo.jpg |
| Subject | (Optional) Subject line for the MMS | Your special offer |
| Message Body | (Optional) Text to accompany the media | Check out this week's deal! |
Note: The media file must be publicly accessible on the internet. Files behind a login or on a private server won't work.
Send a WhatsApp Message
- Set Operation to Send WhatsApp Message
- Choose a Content Type:
Text Message — a free-form message (only works within 24 hours of a contact messaging you first)
| Field | Description |
|---|---|
| Recipient Phone | Mobile number with country code |
| Sender | Your WhatsApp-registered number |
| Text Message Body | The message to send |
Template Message — use a pre-approved WhatsApp template
| Field | Description | Example |
|---|---|---|
| Template Name | The exact name of your approved template | welcome_new_customer |
| Template Parameters | Comma-separated values to fill in placeholders | John, 20%OFF, 31 Dec |
| Template Locale | Language code for the template | en |
SMS Fallback (optional) — if WhatsApp delivery fails, send an SMS instead:
| Field | Description |
|---|---|
| SMS Fallback Sender | The number to send the fallback SMS from |
| SMS Fallback Message | The SMS text to send if WhatsApp fails |
Send an RCS Message
- Set Operation to Send RCS Message
- Fill in the fields:
| Field | Description |
|---|---|
| Recipient Phone | Mobile number with country code |
| Sender | Your RCS Agent ID |
| Message | The message body (up to 3,072 characters, supports emoji) |
| SMS Fallback Sender | (Optional) Fallback SMS number if the device doesn't support RCS |
| SMS Fallback Message | (Optional) SMS text to send as fallback |
Step 4 — Receive events (Trigger node)
Use the Kudosity V2 Trigger node to start a workflow whenever something happens in Kudosity.
- Add a Kudosity V2 Trigger node as the first node in your workflow
- Select your saved credential
- Choose which Events to listen for:
| Event | When it fires |
|---|---|
| SMS Inbound | A contact sends an SMS reply to your number |
| SMS Status | Delivery status update for an outbound SMS |
| MMS Inbound | A contact sends an MMS reply |
| MMS Status | Delivery status update for an outbound MMS |
| RCS Status | Delivery status update for an outbound RCS message |
| Opt Out | A contact opts out of receiving messages |
| Link Hit | A contact clicks a tracked link in your message |
- Activate your workflow (top-right toggle) — this automatically registers the webhook in your Kudosity account
- When you deactivate or delete the workflow, the webhook is removed from Kudosity automatically
Data available in your workflow after a trigger:
| Field | Description |
|---|---|
event_type |
The type of event (e.g. SMS_INBOUND) |
phone |
The contact's phone number |
sender |
The number the message was sent from |
recipient |
The number the message was sent to |
message |
The message content (for inbound events) |
status |
Delivery status (for status events) |
url |
The link that was clicked (for LINK_HIT events) |
message_ref |
Your custom tracking reference (if set) |
id |
The Kudosity message ID |
created_at |
Timestamp of the event |
Tips
- Phone numbers must always include the country code in E.164 format — e.g.
+61412345678for Australia,+12025551234for the US - Message Reference is useful for linking Kudosity messages back to records in your CRM or database
- You can select multiple events in a single Kudosity Trigger node. Use a Switch or Filter node after it to route different event types to different parts of your workflow
- If a WhatsApp or RCS message fails and you have set up an SMS fallback, Kudosity will automatically send the SMS — no extra steps needed in n8n
What this node tells Kudosity
Every request this node makes to Kudosity includes a few headers that identify the
integration, so Kudosity can see how it is used and which versions are still in use:
| Header | Example | Meaning |
|---|---|---|
User-Agent |
kudosity-n8n/0.1.0 |
This integration and its version |
X-Kudosity-Source |
kudosity-n8n |
This integration |
X-Kudosity-Source-Version |
0.1.0 |
Its version |
X-Kudosity-Action |
sms.send |
What the request is for, e.g. connect (testing your credentials), sms.send, trigger.subscribe |
These headers never contain message content, phone numbers, workflow names or anything
about you. Your account is already identified by your API key, as it is for any request.
Need help?
- Kudosity documentation: developers.kudosity.com
- n8n documentation: docs.n8n.io