n8n

Send email from an n8n workflow, list mailboxes, and trigger workflows on inbound Kerabie Mail events.

Status

The n8n-nodes-kerabie-mail package builds and lints clean, but is not yet published to npm.

Publishing (npm publish, plus n8n's verified-community-node review) is a manual step the project runs separately. Until then, use n8n's built-in Webhook and HTTP Request nodes below, which work today with no waiting.

Right now: build it with webhooks

n8n ships a generic Webhook trigger node and an HTTP Request node. Together they cover the same ground the community node will, calling the exact same endpoints.

Trigger a workflow on new email

Add a Webhook trigger node to your workflow. Note the production webhook URL it generates.
Register that URL as a Kerabie Mail webhook endpoint, from Settings → Webhooks in the console, or via the API:

curl -X POST https://api.kerabie.email/webhooks \
  -H "X-API-Key: $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
        "url": "https://your-n8n-instance.com/webhook/kerabie-mail",
        "events": ["email.received"]
      }'

To verify the X-Kerabie-Signature header inside the workflow (recommended), enable the Webhook node's raw-body option and add a Code node using the same HMAC scheme as the signature verification guide.

Send email from a workflow

Add an HTTP Request node configured as:

Method: POST
URL:    https://api.kerabie.email/mail/send
Headers:
  X-API-Key: YOUR_API_KEY
Body (JSON):
{
  "from_email": "support@yourdomain.com",
  "to": ["{{ $json.customer_email }}"],
  "subject": "{{ $json.subject }}",
  "body_html": "{{ $json.html_body }}"
}

See the full field list in the Send email API reference.

The community node (pending npm publication)

Once published, n8n-nodes-kerabie-mail replaces the manual wiring above with a credential, an action node, and a trigger node, still calling the exact same underlying endpoints.

Credential: Kerabie Mail API

Two fields: API Key (required, sent as X-API-Key) and API Base URL (defaults to https://api.kerabie.email, override only for a self-hosted/local backend). The credential is tested against GET /api-keys/whoami.

Node: Kerabie Mail

Resource	Operation	Calls
Message	Send	POST /mail/send
Mailbox	List	GET /mail/mailboxes

Message → Send exposes From Email, To, Subject, and Sandbox as top-level fields, with CC, BCC, Body HTML, Body Text, Template ID, Reply To, Track Opens, and Scheduled At grouped under "Additional Fields".

Attachments, unsend_window, and threading headers (in_reply_to/references) aren't exposed as fields yet in the node; use the HTTP Request fallback above if you need them.

Trigger node: Kerabie Mail Trigger

Activating the workflow calls POST /webhooks with the events you picked from a dropdown (populated live from GET /webhooks/events). Deactivating calls DELETE /webhooks/{id}.

Every delivery's X-Kerabie-Signature header is verified against the stored endpoint secret before the payload is handed to the workflow, using the same timestamp-plus-HMAC-SHA256 scheme described in the signature verification guide. An invalid or missing signature returns 401 without running the workflow.

Authentication

Create an API key under Settings → API Keys with the scopes your workflow needs: send to send mail, webhooks to manage trigger subscriptions, and mailboxes:read to list mailboxes.

n8n