Package Information
Available Nodes
Documentation generating…
Documentation
n8n-nodes-monity
n8n community node for monity.ai — start workflows when a
web page changes, and read or manage your monitors along the way.
monity watches web pages and tells you what changed:
competitor pricing, stock and availability, job boards, regulatory pages,
anything that has a URL.
Installation · Credentials ·
Nodes · Examples · Compatibility ·
Resources
Installation
In n8n, go to Settings → Community Nodes → Install a community node, entern8n-nodes-monity, and confirm. Or on the n8n host:
npm install n8n-nodes-monity
Restart n8n. Monity and Monity Trigger appear in the node panel.
Credentials
You need a monity API key:
- Sign in at app.monity.ai.
- Go to Account → Integrations → API keys and click Create key.
- Tick Allow write access if the workflow should create, update, pause or
resume monitors. Leave it unticked for read-only workflows. - Copy the key — it starts with
mk_live_and is shown only once.
Paste it into a new Monity API credential in n8n. The credential is tested
on save, so a green tick means it really works. Base URL only needs
changing for staging or self-hosted deployments.
Nodes
Monity Trigger
Polls monity and starts the workflow on new checks.
| Setting | Notes |
|---|---|
| Monitor | All Monitors (every monitor in the account, from GET /checks) or one monitor from the dropdown, or a UUID via expression |
| Only Monitors With Label | With All Monitors: only monitors carrying this label (e.g. clients). Leave empty for all. |
| Event | Alert Sent (changes only) or Check Completed (every check, as a data feed) |
| Include Full Detail | On by default: adds the AI summary of what changed, the before/after extracted values, and the screenshot / diff-image URLs. Turn off on busy feeds to make fewer API calls. |
It never emits the same check twice, and does not replay history when a
workflow is first activated. Fetch Test Event returns the newest check
without consuming it, so building the workflow does not cost you a real
trigger.
Polling needs no inbound connectivity, which is the usual case for a
self-hosted n8n. If your instance is publicly reachable and you want changes
within seconds, use a Webhook node instead and add its URL as a Webhook
notification channel on the monitor — deliveries are signed withX-Monity-Signature.
Monity
| Resource | Operations |
|---|---|
| Monitor | Create, Delete, Get, Get Latest Result, Get Many, Pause, Resume, Run Check Now, Update |
| Check | Get, Get Many |
Create, Update, Pause, Resume, Run Check Now and Delete need a key with write access. Run Check Now uses one check credit; its result reaches the trigger like any other check. Get Many returns
one item per monitor or check, ready to iterate over.
Examples
Change alerts in Discord, with the diff image
Monity Trigger (Alert Sent) → Discord. Message from{{ $json.aiSummary }}, embed image from {{ $json.artifacts.diffImageUrl }}.
Every check into Postgres
Monity Trigger (Check Completed, detail off) → Postgres Insert on id,createdAt, status, percentDifference.
Pause noisy monitors overnight
Schedule Trigger → Monity (Monitor → Get Many, label noisy) → Monity
(Monitor → Pause, {{ $json.uuid }}). Both operations are idempotent, so a
retry is harmless.
Alert only on what matters
Monity (Monitor → Update) → Alert Me When: "only alert me when the Pro
plan price changes". monity evaluates the sentence on every check, so the
workflow runs on signal instead of filtering noise afterwards.
Longer walkthroughs: https://monity.ai/docs/n8n-integration/
Compatibility
Requires Node.js 18+ and an n8n version with n8nNodesApiVersion 1. Tested
against n8n-workflow 2.16. No runtime dependencies.
Develop
npm install
npm run build # tsc + copies icons and codex files into dist
npm run lint # eslint-plugin-n8n-nodes-base — the rules n8n's reviewers run
npm test # jest, covers the trigger's dedup and failure behaviour
Link into a local n8n for manual testing:
npm run build && npm link
mkdir -p ~/.n8n/nodes && cd ~/.n8n/nodes && npm link n8n-nodes-monity
n8n start
Issues and suggestions: https://github.com/kamilmm21/n8n-nodes-monity/issues or hello@monity.ai.