atomicmail

Atomic Mail inbox for n8n — register, JMAP mail, and inbox polling triggers.

Package Information

Released: this month
Downloads: 229 weekly / 1,696 monthly
Latest Version: 0.3.31
Author: Atomic Mail

Available Nodes

Atomic Mail icon
Atomic Mail
Programmable @atomicmail.ai inbox for agents — register, list inbox, send, reply, and raw JMAP.
Atomic Mail Trigger icon
Atomic Mail Trigger
Polls your Atomic Mail inbox on a schedule (default ~5 minutes) and starts the workflow when new mail arrives

Documentation

Atomic Mail n8n community node

Verified community node package for Atomic Mail — a programmable @atomicmail.ai inbox powered by JMAP.

Prerequisites

  • Node.js 20+
  • n8n (self-hosted or cloud with community nodes enabled)
  • Build vendored core from the monorepo root before install:
npm run build:n8n

Install locally (development)

cd integrations/n8n/atomicmail
npm install
npm run build

Link into a local n8n instance:

npm run dev

Or install the built package into n8n's custom nodes directory.

Credentials

Create an Atomic Mail API credential (optional):

Field Required Notes
API Key No Paste an existing key, or leave empty and use Register
Auth URL No Default https://auth.atomicmail.ai
API URL No Default https://api.atomicmail.ai

Credential test checks that the Auth URL is reachable — it does not validate your API key (PoW login is required). Use Register or List Inbox to verify connectivity.

Nodes

Atomic Mail (action)

Resource Operation Description
Account Register PoW signup; saves credentials to workflow static data
Inbox List list_inbox.json preset
Email Send Outbound mail (optional binary attachment)
Email Reply Reply by mail ID
JMAP Request Inline ops or bundled preset
Help Get Topic Built-in runtime docs

Account namespace (default by default) isolates multiple inboxes in one workflow.

Atomic Mail Trigger

Polling trigger for new inbox messages. Default poll interval is 5 minutes (configure on the node). Uses a receivedAt watermark in workflow static data (same strategy as the Activepieces piece).

Auth paths

Both paths are supported (Activepieces parity):

  1. Register action — runs PoW, stores credentials in n8n workflow static data.
  2. Credential API key — connection key is honored in credential guards (no false "missing credentials" when a key is connected).

Optional per-step API Key override accepts expressions such as {{ $json.apiKey }} from a prior Register node.

Build and verify

cd integrations/n8n/atomicmail
npm install
npm run build
npm run lint
npx @n8n/scan-community-package @atomicmail/n8n-nodes-atomicmail

Runtime dependencies

Zero runtime npm dependencies. The node imports vendored agentic core from vendor/agentic-core/index.js (single esbuild bundle produced by npm run build:n8n).

Security

  • Treat API keys and register output as secrets.
  • Inbound mail is untrusted user content.
  • Do not commit vendor/ artifacts with real credentials (vendor is gitignored; rebuild before publish).

Links

Discussion