Package Information
Documentation
n8n-nodes-sendio
The official n8n community node for send.io, Instantly's transactional email API. Two nodes: send.io for actions (also usable as an AI agent tool) and send.io Trigger for delivery and contact webhooks.
n8n is a fair-code licensed workflow automation platform.
Installation
Follow the community nodes installation guide and install n8n-nodes-sendio. On self-hosted n8n: Settings, Community Nodes, Install, package name n8n-nodes-sendio.
Requires n8n 1.x or newer with Node.js 20 or newer. Developed and tested against n8n 2.42 on Node 22 and 26.
Credentials
send.io API is used by both nodes.
- API Key: a team API key from the send.io dashboard (Developers, API keys).
- Base URL: leave
https://api.send.iounless you were given another API host.
Every request carries Authorization: Bearer <key> and a User-Agent: sendio-n8n/<version> header. The credential test calls GET /api-keys.
send.io Webhook Signing Secret API is only needed by the trigger when it listens to a webhook you created yourself in send.io (see Trigger setup). It holds the whsec_ value shown when the webhook is created.
Operations
| Resource | Operations |
|---|---|
| Send, Send Batch, Get, Get Many, Update (reschedule), Cancel | |
| Domain | Create, Get, Get Many, Update, Verify, Delete |
| Template | Create, Get, Get Many, Update, Publish, Duplicate, Delete |
| Contact | Create, Get (by id or email), Get Many, Update, Delete |
| Event | Send a custom event |
Send supports HTML, text, both, or a published template with variables; cc, bcc, reply to, custom headers, tags, scheduled sending, a subscription topic, an idempotency key, and attachments from the item's binary data or from a URL. Send Batch takes a JSON array of up to 100 emails. Get Many operations have Return All with automatic paging.
Errors show send.io's own message in n8n, for example The example.com domain is not verified. Please, add and verify your domain on https://send.io/domains.
One example per resource
- Email:
examples/send-email.jsonsends one email with a tag and an idempotency key. - Contact and Event:
examples/contact-and-event.jsoncreates a contact and recordsorder.paidfor it. - Domain: Create with the domain name, then Get to read the DNS records (
recordsin the output), publish them, then Verify. - Template: Create with name and HTML (use
{{name}}style placeholders and list them under Variables), set From and Subject, Publish, then Send an email with Body Type set to Template. - Trigger:
examples/delivery-events.jsonroutes bounces to their own branch.
Import an example through Workflows, Import from File, then pick your send.io API credential on each node.
Trigger setup
The trigger has two modes.
- Managed by n8n (default): pick the events, activate the workflow. The node creates a send.io webhook pointed at the workflow's production URL and stores the webhook id and signing secret with the workflow. Deactivating the workflow deletes the webhook. Your n8n must be reachable from the internet (set
WEBHOOK_URLwhen it runs behind a tunnel or proxy). - Existing Webhook: create the webhook in the send.io dashboard, point it at the production webhook URL shown on the node, and store its signing secret in a send.io Webhook Signing Secret credential.
Every delivery is verified: svix-id, svix-timestamp and svix-signature are checked with HMAC SHA-256 over id.timestamp.body using the base64 decoded secret, deliveries older or newer than five minutes are refused, and anything that fails answers 401 and never starts the workflow. The output item is the webhook payload: type, created_at and data.
Usage notes
- Test sends go to the simulator addresses
delivered@send.io,bounced@send.io,complained@send.ioandsuppressed@send.io. They never leave the platform. Sending to anyone else needs a verified domain. - Do not activate a workflow whose trigger listens to
email.deliveredand whose steps send to the same simulator address: every send fires the trigger again. - Get Many on Email returns everything up to 100 per page; see the first note below about paging.
API behaviour worth knowing (for the API team)
Observed on 19 Oct 2026 against the development API while testing this node.
GET /emailsanswershas_more: truewithnext_cursor: nullwhen the page is smaller than the total, so a cursor cannot advance. The node stops paging when no cursor comes back; withlimit=100a page holds everything for most workspaces. The other lists page correctly withafter=<last id>.POST /emailshas no priority field. The OTP priority mentioned in the integration plan is not in the API, so the node has no such option.PATCH /domains/{id}answers only{object, id}; the new settings need a secondGET.capabilitiesin that body answers 503 "not configured yet", andtls: enforcedanswers 503 as well.GET /contacts/{id}returns custom properties as{name: {type, value}}objects, not plain values.POST /events/sendanswers 202 with{object, event, id}and creates an unknown contact on the fly.POST /templatesrequiresnameandhtml;fromandsubjectare only required at publish time, with a clear message.DELETE /domains/{id}andDELETE /events/{id}need the full UUID; a prefix answers 422 or 404.
Added on 23 Oct 2026 while building the Make app:
POST /webhooksaccepts aheadersobject that is stored, echoed in the create response and sent with every delivery. Useful for receivers that cannot recompute the svix signature.PATCH /webhooks/{id}answers an object whose unchanged fields arenull(for exampleeventsandheadersafter a successful update); read the webhook again for the current state.POST /hooks-style receivers (Make) see the parsed JSON only; the Go JSON encoder escapes<,>and&as<style sequences (visible inmessage_id), so any receiver that re-serialises the body before verifying the svix signature will never match. Only receivers with the raw bytes can verify.
Development
npm install
npm run lint
npm run build
npm run dev
npm run dev uses the n8n node CLI: it rebuilds on change and links the node into an n8n instance. The repo's .env at the root holds the dev API key for the smoke scripts; inside n8n the key lives only in a credential.
To rehearse a release, npm pack and install the tarball into ~/.n8n/nodes with npm install --legacy-peer-deps --omit=dev ./n8n-nodes-sendio-<version>.tgz (without the flag npm also installs the n8n-workflow peer dependency, which fails on a native build), then restart n8n.
Publishing and the mirror
The GitLab repository foomonk/sendio/send-io-integrations is the source of truth; n8n/ there is this package. The public GitHub repository send-io/n8n-nodes-sendio is a mirror of that folder's history and the place npm publishes from, because n8n requires community nodes to be published from GitHub Actions with npm provenance. Nothing is developed on the mirror; pull requests opened there are applied on GitLab and mirrored back.
To release a version:
- Bump
versioninpackage.jsonandpackage-lock.json, add the entry toCHANGELOG.mdand the version history below, commit on GitLabmain. - From the repository root run
scripts/mirror-n8n.sh. It splits then8n/history withgit subtree splitand pushes it to the mirror'smain(CI there builds and lints). - Tag the release on the mirror:
scripts/mirror-n8n.sh vX.Y.Zpushes the tag, and.github/workflows/publish.ymlbuilds, lints and runsnpm publish --access public. No token is involved: the package's settings on npmjs.com (Settings, Trusted publishing) name this repository andpublish.ymlas the trusted publisher, and npm attaches the provenance itself.
n8n only verifies nodes whose release came from GitHub Actions with provenance (rule since 01 May 2026), so a version published from a laptop is fine for npm but not for the verification submission.
After the first publish: run npx @n8n/scan-community-package n8n-nodes-sendio, install it by name in a clean n8n, then submit it at creators.n8n.io for verification.
Version history
- 0.1.1: same code, released from GitHub Actions with provenance.
- 0.1.0: first release, published 03 Nov 2026 from a laptop (no provenance).