sendry

n8n community node for Sendry — transactional email, contacts, audiences, and domains.

Package Information

Downloads: 7 weekly / 135 monthly
Latest Version: 0.1.0
Author: Sendry

Documentation

n8n-nodes-sendry

Official n8n community node for Sendry.

  • License: Apache-2.0
  • Distribution: npm (npm install n8n-nodes-sendry inside your n8n instance,
    or via the Settings → Community nodes UI).
  • Peer dep: n8n-workflow@^1.

Install

In your n8n installation:

# Inside an n8n container or self-hosted setup
npm install n8n-nodes-sendry

Or via the n8n UI: Settings → Community Nodes → Install and enter
n8n-nodes-sendry.

Credentials

Add a Sendry API credential and paste an API key from
Settings → API keys. Use a
sending_access or full_access key for write operations.

Self-hosted users can override API Base URL to point at their own
Sendry deployment.

The credential test hits GET /v1/auth/whoami so n8n confirms the key
is live before saving.

Operations

Resource Operation Endpoint
Email Send POST /v1/emails (idempotent per execution)
Email Get GET /v1/emails/:id
Contact Upsert PUT /v1/contacts/by-email
Domain Create POST /v1/domains
Audience List GET /v1/audiences

The Email → Send action supports:

  • Multiple recipients (comma-separated to/cc/bcc/reply_to).
  • template_id instead of raw html/text.
  • scheduled_at (ISO 8601 or natural language).
  • tags as a JSON array of {name, value}.
  • Explicit idempotency_key or auto-generated per n8n execution.

Build

bun install
bun run build          # tsc + gulp build:icons → dist/
bun run typecheck      # tsc --noEmit

The build produces dist/nodes/Sendry/Sendry.node.js, the bundled SVG
icon, and dist/credentials/SendryApi.credentials.js — which is what
n8n loads via the n8n block in package.json.

Layout

sendry-n8n/
├── credentials/
│   └── SendryApi.credentials.ts
├── nodes/
│   └── Sendry/
│       ├── Sendry.node.ts
│       ├── Sendry.node.json
│       └── sendry.svg
├── gulpfile.js
├── tsconfig.json
└── package.json

License

Apache-2.0. See LICENSE.

Discussion