Package Information
Documentation
n8n-nodes-azimea
Use Azimea contacts from native n8n workflows. Azimea is an email marketing and automation service.
This first version targets self-hosted n8n. Installation on n8n Cloud requires separate n8n verification;
this package does not claim that approval.
Operations
- Contact / Create or Update: write a profile and patch custom attributes, without changing consent.
- Contact / Get: find by Azimea ID, external ID or email. Store contacts require their Azimea ID.
- Contact / Unsubscribe: look up an existing contact and stop marketing. A missing contact is never created.
Unsubscribe stops marketing only; service messages and bounce/complaint restrictions retain API semantics.
Subscription with proof, custom events, flow triggers and outbound triggers are not included in this version.
Do not infer permission from a form, purchase or profile. Retrying a profile upsert cannot resubscribe a contact.
Credentials
Create a dedicated company API key in Azimea with contacts:read and contacts:write. Enter it in an Azimea API
credential in n8n. Keep the default https://api.azimea.com/v1 base URL; change it only for a trusted private
installation because your key is sent there. n8n stores the credential encrypted; never put keys in workflow JSON.
The credential test needs contacts:read. Read-only keys can get contacts but cannot mutate them.
Installation and development
Once the package is available on npm, open Settings > Community nodes > Install in self-hosted n8n,
enter n8n-nodes-azimea, acknowledge n8n's community-node notice and install. Select Azimea in the node
picker and create an Azimea API credential. If community-node installation is disabled, contact your
instance administrator. Check the npm package for release
availability; a public source repository alone does not mean registry publication has completed.
Use Node 24 and the official n8n-node tool:
npm ci --legacy-peer-deps --ignore-scripts
npm run lint
npm test
npm pack --ignore-scripts
Install the resulting archive in the nodes directory of a self-hosted n8n instance and restart it, following
n8n manual installation.
Import examples/contact-profile.json for a minimal workflow, choose your own credential and replace the
reserved example identity before using it. The example contains no key and does not subscribe the contact.
The package has no runtime dependencies. The programmatic style is required because unsubscribe must resolve
an existing identity before the dependent write, preventing accidental creation through the upsert API.
Usage and errors
Connect a Manual Trigger or your form/CRM node to Azimea. Select Contact, then an operation. Map a stable
External ID under Additional Fields for upserts. Profile fields left empty are omitted; attributes accept a
JSON object patch, with null removing a value and omitted keys staying unchanged. Attribute definitions follow
company settings. Identity conflicts are refused by the API; this node does not merge contacts.
Each input item produces one paired output. Upsert/unsubscribe return the API value {contact, created}; Get
returns the contact. Use n8n retry settings for transient failures/429 with a suitable wait; no internal blind
retry or custom queue is added. Correct invalid fields and insufficient scopes before retrying. Revoked keys
must be replaced. Continue On Fail returns an error item and preserves pairing for later items.
Distribution
Published source: https://github.com/panaionutwteh/n8n-nodes-azimea. npm publication uses GitHub Actions with
provenance; catalogue/Cloud verification is a separate n8n review. MIT licensed; Azimea service terms apply
separately. See https://docs.azimea.com/build/contacts-and-consent/ for the API contract.
Verification
Version 0.1.0 was tested in actual n8n 2.46.6 against a local Azimea API and PostgreSQL with synthetic data.
Twelve native executions cover create/update/get/unsubscribe, duplicate identity, withdrawal preservation,
insufficient scopes, revoked keys, missing contacts, validation and recovery after injected 500/429.
Nine automated unit tests cover request mapping, HTTP status preservation, malformed input, paired items and Continue
On Fail. The actual desktop editor, parameters, consent notice and validation error were browser-tested and
visually reviewed. Broader n8n versions, Cloud and responsive editor compatibility are not certified.
No runtime dependencies, local filesystem access or environment-variable access are used by the node.