Start free

HealthCheckEmail + n8n

Automate email health monitoring with the official HealthCheckEmail community nodes. React to signed DNS-change and DMARC events with the trigger node, then add domains, read health, manage alerts and status pages with 18 operations, all behind one OAuth connection.

Set up in 3 stepsView on npm ↗

Version 3.2.0 · Available on n8n Cloud as a verified node · Self-hosted via Community Nodes · MIT licensed

What you can automate

Everything the dashboard does, without opening the dashboard

One trigger node for live events and one action node for every monitoring, alerting and account operation, so the workflow you build is the workflow your team actually runs.

Onboard client domains in bulk

Add every domain from a spreadsheet or CRM, collect the suggested DMARC record for each and verify it once DNS has been published.

Route email-health incidents

Start from the trigger node and send DNS changes, DMARC misconfigurations and authentication-failure spikes to Slack, PagerDuty, Opsgenie or a ticket queue, with the domain and event attached.

Report without the dashboard

Pull grades, infrastructure snapshots and sending-source diagnostics on a schedule and deliver them by email, in a Notion page or a shared sheet.

Keep alerts and status pages in step

Pause alerts during a migration, re-enable and test them afterwards, and publish or retire public status pages as clients come and go.

Setup

Three steps to connect HealthCheckEmail and n8n

No API key, client secret or token is pasted into a workflow. n8n stores the OAuth credential and refreshes it for you.

  1. 01

    Install the node

    n8n Cloud: available on n8n Cloud as a verified node. Open the node panel, search for HealthCheckEmail and add either the action node or the HealthCheckEmail Trigger to the canvas.

    Self-hosted: go to Settings → Community Nodes → Install, enter n8n-nodes-healthcheckemail and confirm. Both nodes install together (current version 3.2.0).

  2. 02

    Connect your account

    Add either node and create a HealthCheckEmail OAuth2 API credential. Click Connect my account, sign in to HealthCheckEmail, review the consent screen and approve.

    The connection calls the HealthCheckEmail REST API and needs a plan with API access (Pro and above). You can revoke it at any time from the HealthCheckEmail dashboard. The API keys under Dashboard → API are for direct REST calls and are not required for n8n.

  3. 03

    Pick a trigger or an operation and run it

    For live events, set the trigger's Domain ID and events, then activate the workflow; the signed webhook subscription is registered for you.

    For actions, choose a resource and one of the 18 operations, fill in the required fields and execute. Start with List Domains, then map a returned domain ID into the trigger or a second action node.

Prefer to start from a file? The repository ships an example workflow (examples/account-check.json) that runs List Domains from a manual trigger. Open it on GitHub ↗

Triggers

Start a workflow the moment email health changes

The package ships a dedicated HealthCheckEmail Trigger node that receives signed webhooks for a domain, plus the action node for scheduled and app-driven workflows.

HealthCheckEmail Trigger

Receive signed HealthCheckEmail webhooks. Parameters: Domain ID (the owned domain whose events should trigger the workflow) and Events (multi-select, all three on by default).

  • DNS Changeddns_change

    Any monitored record (SPF, DKIM, DMARC, MX, BIMI, MTA-STS, DNSSEC) changed value.

  • Multiple DMARC Recordsdmarc_multi

    More than one DMARC record is published, a misconfiguration that breaks enforcement.

  • DMARC Volume Spikespike

    A sudden rise in mail failing authentication for the domain, a possible spoofing run.

Needs a public HTTPS n8n webhook URL. Each event is verified against the subscription's HMAC signature, rejected if older than five minutes, and matched to the selected domain before your workflow runs.

HealthCheckEmail Trigger node

Domain ID + one or more events

Add the trigger, pick a domain you own and tick the events you want. Activating the workflow registers a signed webhook subscription on that domain; deactivating removes only that subscription. Every incoming event is HMAC-verified, checked for freshness and matched to the domain before your workflow runs.

Scheduled check

n8n Schedule trigger + any read operation

Poll on your own cadence. A Schedule trigger followed by List Domains and Get Domain Health gives you a grade for every domain each morning, week or quarter without touching the dashboard.

Events from other apps

Any n8n trigger + a write operation

A new row in Google Sheets, a won deal in your CRM or a form submission can add a domain, enable its public status page or invite a teammate. The HealthCheckEmail node sits anywhere in the workflow.

Operations

All 18 operations, grouped by resource

Read operations are safe to run on a schedule; list operations offer Return All or a Limit and follow paging for you. Write operations change account data or may use credits as soon as they run.

Domain

Onboard domains, read everything HealthCheckEmail knows about them and control their public status page.

  • Add Domainwrite

    Add a domain to monitoring. Returns its DMARC reporting address and the exact suggested DNS record.

  • Verify Domainwrite

    Check live DNS for the DMARC record and confirm reports route to HealthCheckEmail, with failure details when setup is incomplete.

  • List Domainsread

    List every monitored domain with setup status and public status URLs.

  • Get Domainread

    Get one domain, its DMARC setup record, reporting state and public status configuration.

  • Get Domain Healthread

    Latest health grade, grade history, protected-message counters, compliance checks, recent events and detected mail provider.

  • Get Email Infrastructureread

    Recent SPF, DKIM, DMARC, MX, BIMI, MTA-STS and DNSSEC snapshots plus the detected mail provider.

  • Get Domain Diagnosticsread

    Daily pass/fail volume, report providers, subdomains, geography, sending sources, unknown senders and DKIM selectors.

  • Get Enforcement Readinessread

    Simulate an enforcing DMARC policy and list the legitimate senders that would fail alignment.

  • Enable Public Statuswrite

    Enable the public email-health status page and badge for a domain. Returns the generated URLs.

  • Disable Public Statuswrite

    Disable the public status page and invalidate its public URL.

Alert

Manage the email, webhook and Slack alerts attached to a domain.

  • Create Alertwrite

    Create an email, HTTPS webhook or Slack alert for email-health events. Generic webhooks return a signing secret.

  • List Alertsread

    List the configured email, webhook and Slack alerts for a monitored domain.

  • Update Alertwrite

    Change an alert's target, event rules, label or enabled state.

  • Test Alertwrite

    Send a synthetic test notification through an existing alert channel.

  • Delete Alertwrite

    Permanently delete an alert from a monitored domain.

Team Member

Manage who has access to the HealthCheckEmail account.

  • List Team Membersread

    List people with access to the account and their owner or member role.

  • Invite Team Memberwrite

    Invite a person to the account. Only account owners can invite members or other owners.

  • Remove Team Memberwrite

    Remove a person from the account. Only account owners can remove members.

Recipes

Six workflows teams build in the first week

Each recipe names the HealthCheckEmail operations it uses, so you can rebuild it in a few minutes.

WhenHealthCheckEmail Trigger: any event

ThenSlack or PagerDuty

Start from the trigger node with all three events selected. Route DMARC Volume Spike to a PagerDuty incident and post DNS Changed and Multiple DMARC Records to a Slack channel with the domain and event attached. Use Test Alert to rehearse the path.

  • HealthCheckEmail Trigger
  • Test Alert

WhenNew row in Google Sheets

ThenAdd Domain

When a row is added to an onboarding sheet, add the domain to monitoring, write the suggested DMARC record back to the row and run Verify Domain a day later to confirm reports are flowing.

  • Add Domain
  • Verify Domain

WhenSchedule, every Monday

ThenWeekly email health report

List Domains, split out one item per domain, fetch each Get Domain Health result and send a single email with grades, grade changes and open compliance checks to the people who own email.

  • List Domains
  • Get Domain Health

WhenHealthCheckEmail Trigger: DNS Changed

ThenLinear or Jira issue

When a monitored record changes, fetch Get Domain Health and Get Email Infrastructure for the domain and create a Linear or Jira issue with the new grade, the changed record and the current SPF, DKIM and DMARC snapshot attached.

  • HealthCheckEmail Trigger
  • Get Domain Health
  • Get Email Infrastructure

WhenDeploy or DNS migration starts

ThenPause alerts, then restore them

A webhook from your deploy pipeline lists the domain's alerts and disables them with Update Alert. When the migration finishes, re-enable them and fire Test Alert so the on-call channel sees they are back.

  • List Alerts
  • Update Alert
  • Test Alert

WhenClient signed in your CRM

ThenPublish a public status page

When a deal closes, add the client's domain, enable its public email-health status page and send the generated URL and badge to the client welcome email or their portal record.

  • Add Domain
  • Enable Public Status

Why n8n

Open, self-hostable automation that fits an email-health workflow

Self-hostable

Run n8n on your own infrastructure or on n8n Cloud. Email-health data stays on the path you choose.

Hundreds of integrations

Connect HealthCheckEmail to Slack, PagerDuty, Google Sheets, Linear, Jira, Notion, your CRM and any HTTP API.

Your account, your limits

The nodes sign in with OAuth as you and call the HealthCheckEmail REST API. Roles, plan limits and ownership checks are enforced by HealthCheckEmail, not by the workflow.

Usable as an AI tool

The action node is marked usable as a tool, so n8n AI Agent nodes can call it to inspect a domain or add one while they work.

Package and documentation

Common questions

Do I need an API key to use the HealthCheckEmail n8n node?+

No. Both nodes use OAuth: create a HealthCheckEmail OAuth2 API credential in n8n, click Connect my account, sign in and approve the connection. Nothing is pasted into a workflow field. The API keys page in the dashboard (app.healthcheckemail.com/api-keys) issues keys for direct REST calls and is not used by the n8n nodes.

Which plans include the n8n integration?+

The nodes call the HealthCheckEmail REST API, which is included with API access on Pro, Agency and MCP plans. Every paid plan starts with a 7-day free trial.

Is there a trigger node?+

Yes. The HealthCheckEmail Trigger node receives signed webhooks for one domain and three event types: DNS Changed, Multiple DMARC Records and DMARC Volume Spike. Activating the workflow registers the subscription for you; the signing secret stays in the node's workflow state and is never emitted as event data. It needs a public HTTPS n8n webhook URL.

I installed version 1.x or 2.x. What changed in 3.x?+

Version 3 calls the product REST API at healthcheckemail.com/v1 with its own OAuth audience and adds the trigger node. Create a new HealthCheckEmail OAuth2 API credential and reconnect it before running existing workflows; tokens issued for the earlier resource cannot be reused. Input names are unchanged.

Is HealthCheckEmail a website uptime monitor?+

No. HealthCheckEmail monitors the email side of a domain: SPF, DKIM, DMARC, MX, BIMI, MTA-STS, DNSSEC, TLS reporting, sending sources and reputation. Pair it with a website uptime monitor in the same n8n workflow if you want one incident channel for both.

Can a write operation run twice by accident?+

Selecting a write operation is enough to run it; there is no extra confirmation checkbox in version 3. Each input item makes one request and failed requests stop the workflow unless Continue On Fail is enabled, so deduplicate scheduled workflows that create data and use the read operations for monitoring.

Connect your first domain, then automate the rest

Start free with one monitored domain. Upgrade to Pro when you are ready to connect n8n, the API or the MCP server.

Start free ↗All integrations