sendbaze

n8n community node for Sendbaze: send email and SMS from South Africa, manage contacts and consent, and start workflows from delivery, bounce and STOP-reply events.

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.0
Author: Sendbaze

Documentation

n8n-nodes-sendbaze

The Sendbaze community node for n8n: send email and SMS from South Africa, keep contacts and their consent, and start workflows from delivery, bounce and STOP-reply events.

Install

In n8n open Settings → Community Nodes → Install, enter n8n-nodes-sendbaze and confirm. Self-hosted instances can also run npm install n8n-nodes-sendbaze in the n8n user folder. The node needs n8n 1.0 or later.

Credentials

Create a Sendbaze API credential with an API key from the API keys page of your dashboard. A test key (sk_test_…) validates and stores messages without sending anything, which is the right key while you build the workflow. n8n checks the key against GET /v1/usage when you save it.

Sendbaze node

Resource Operations Notes
Email Send, Get HTML and text, or a saved template with variables; transactional or marketing; CC, BCC, Reply-To, tags, send at a later time, idempotency key
SMS Send, Get One E.164 number; transactional or marketing; sender id, tags, send at a later time, idempotency key
Contact Create or Update, Get, Opt Out By email address or phone number, with fields and the consent the person gave (channel, source, evidence)

Everything goes through the same API your code would call, so the rules are the API's: live email needs a verified domain, a marketing SMS needs a consent record for the number, STOP replies and unsubscribes are honoured, and errors come back with the API's code and message (for example consent_missing: …). Turn on Continue on fail to keep going and put the error on the item instead.

Sendbaze Trigger

Starts a workflow when Sendbaze reports an event: email sent, delivered, bounced, complained, failed or unsubscribed; SMS sent, delivered, failed or opted out (a STOP reply); and the account events usage threshold, credits low and payment failed. Choose the events, or leave the list empty for all of them.

When the workflow is activated the node registers its own endpoint with POST /v1/webhooks and keeps the signing secret; when it is deactivated the endpoint is removed. Every delivery is verified against the Sendbaze-Signature header before the event reaches your workflow, and the dashboard's Send test event button reaches it too. The event has id, type, occurredAt and data as documented under Webhooks.

Example: SMS after a form

  1. Form Trigger collects a name, a number and a consent tick box.
  2. Sendbaze → Contact → Create or Update with the phone number, first_name as a field and Record Consent on (source Form, evidence the form URL).
  3. Sendbaze → SMS → Send, marketing, Hi {{ $json.first_name }}, thanks for signing up.
  4. Sendbaze Trigger on SMS Opted Out updates your CRM when someone replies STOP.

Documentation

docs.sendbaze.com/resources/n8n. Support: support@sendbaze.com.

License

MIT

Discussion