n8n-nodes-sendy
v0.2.0
Published
n8n community node for Sendy — send SMS, read inbound replies to your virtual number, and manage contacts, segments, senders and credits via the Sendy public API.
Maintainers
Readme
n8n-nodes-sendy
This is an n8n community node. It lets you use Sendy in your n8n workflows.
Sendy is a credit-based SMS marketing platform for the Israeli market — send SMS, read the replies people send back to your virtual number, and manage contacts, segments and senders from your automations.
n8n is a fair-code licensed workflow automation platform.
Installation
Operations
Credentials
Compatibility
Usage
Resources
Installation
Follow the installation guide in the n8n community nodes documentation. In n8n, go to Settings → Community Nodes → Install and enter n8n-nodes-sendy.
Operations
| Resource | Operation | What it does | |---|---|---| | Message | Send | Send a single SMS (optional idempotency key and send mode) | | | Get | Get the status of a sent message | | Contact | Create or Update | Idempotent upsert by phone (merges fields, never removes segments, never re-subscribes) | | | Get | Get one contact by ID | | | Get Many | List contacts (paginated) or look one up by phone | | Segment | Get Many | List active segments and their member counts | | Sender | Get Many | List approved sender IDs usable as From | | Custom Field | Get Many | List the workspace's custom-field slots and labels | | Credit | Get Balance | Get the current credit balance | | Inbound Message | Get Many | List SMS replies received on your virtual number (paginated, optional Received Since) | | Virtual Number | Get | Get your dedicated virtual number and its billing state |
Credentials
You need a Sendy account and an API key.
- In Sendy, open Developers and create an API key (it starts with
sk_live_). - In n8n, create a Sendy API credential and paste the key.
- Leave Base URL as
https://sendy.co.il/api/v1for production (change it only to point at a staging or self-hosted instance).
The credential is validated against GET /credits when you save it.
Compatibility
Requires n8n 1.x. Tested against the Sendy /api/v1 public API.
Usage
- Billing: 1 credit per message per 201 characters, any encoding. Check the balance with Credit → Get Balance before bulk sends.
- Message length: hard limit 603 characters (3 credits). A longer body is rejected with
MESSAGE_TOO_LONG— past that length the SMS gateway silently truncates on the wire, so Sendy refuses instead of charging you for a message that arrives cut short. - Senders: only approved senders work as From, and the value is matched literally — always pick from the dropdown, because a re-typed
0532740000is rejected asSENDER_NOT_APPROVEDeven when it is your own number. If your workspace holds a Sendy virtual number it appears in the list as a+972…phone number: send from it and recipients can reply. - Send mode: Marketing rejects the send (403, nothing charged) when the recipient unsubscribed from your workspace (
RECIPIENT_UNSUBSCRIBED) or is on its blocked-numbers list (RECIPIENT_BLOCKED) — it does not silently skip. Transactional declares the message isn't marketing and skips both checks. Omit it to use your workspace default. - Other rejections:
CONTENT_FLAGGED(422 — the body matched the platform's restricted-content policy, nothing charged) andACCOUNT_UNDER_REVIEW(403 — a new account may only send to its own verified sender number until the review completes). - Inbound replies: Inbound Message → Get Many returns messages oldest first with cursor pagination.
opt_out: "detected"means Sendy already unsubscribed that sender automatically (opt_out_applied_atsays when);"suspected"is a removal word inside a longer message, flagged in the Sendy app but never auto-applied. To poll for new replies, run it on a Schedule trigger with Received Since set to your last run. A long inbound message arrives as one item per SMS part — the gateway does not reassemble them. - Contacts: upsert matches on phone. On an existing contact, blank/omitted fields keep their current value and segments are only added. Provide at least one segment when creating a new contact. Israeli phone numbers are normalized automatically.
- Rate limit: 60 requests/minute per API key.
