NotePM Zapier integrationAutomate NotePM with Zapier.
The NotePM Zapier integration gives you 4 triggers and 1 action, with 0 searches. All four triggers are instant, so a new page, an edit or a comment in your company wiki reaches your other tools at once, even on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the NotePM Zapier integration actually does for your wiki
The NotePM Zapier integration links your NotePM wiki to the other apps your team already uses, with no code. Something happens in NotePM (a page is written, edited or commented on) and Zapier passes it on. Or the reverse: something happens elsewhere and Zapier writes a fresh page into NotePM for you.
Three results people usually build first. A heads-up when documentation lands: New Page fires the second someone publishes, and the team chat gets the title and the link. A change log nobody has to keep: Updated Page (or New Page or Updated Page if you want both in one stream) feeds a spreadsheet row for every edit. Meeting notes or form answers filed as wiki pages: Create Page takes text from another app and drops it into the Note you pick, with a title and a body.
Comments count too. New Comment is the one to watch when reviews happen inside the wiki and the author would otherwise never notice them.
Now what this integration does not do. There is no search step, so a Zap cannot look up an existing page and reuse what it finds. There is no action to edit, move or delete a page either: Create Page is the only thing Zapier can write. If your plan hinges on updating pages already in NotePM, this integration will not get you there. The Zapier review covers where the tool fits in general, and the n8n vs Zapier comparison helps when a missing operation pushes you toward a tool where you can build the missing step yourself.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here they are, in plain terms.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that sets the Zap off. Once the Zap is switched on, Zapier sits and waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
- Task
- The unit Zapier bills. One action that completes successfully is one task, and your plan counts those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it quietly otherwise.
- Connection
- Your NotePM account linked to Zapier once, then reused by every step of every Zap that touches NotePM.
What it really costs to run NotePM on Zapier
NotePM is not a premium app, so it works from the free plan. What you pay for is tasks, and only actions produce them.
- Premium appNo, available on the free plan
- Free plan100 tasks per month, two-step Zaps only
- Trigger costZero tasks
- NotePM triggers4 instant, 0 polling
The trigger never costs a task, and neither does Zapier listening for new events. Every action that succeeds counts once: a Zap with three actions burns three times what a one-action Zap does. An action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Add a filter, a second action or a search and you have a multi-step Zap, which needs a paid plan. The interval grid below only matters for polling triggers, and NotePM has none: its four triggers fire straight away on every plan.
Connect your NotePM account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box: type NotePM and pick it from the list of apps that match your search.
- 02
Sign in to NotePM
Click Add connection. A new browser tab opens on NotePM: sign in with the account the Zaps should act as, ideally one that already sees every Note you plan to automate.
- 03
Grant access
Allow Zapier to reach the account. The tab closes and the connection appears in your list. From then on, every NotePM step in every Zap reuses it without asking again.
Your first Zap: post new wiki pages to the team chat
GoalEach new NotePM page, once it passes a filter, becomes a message in your team chat.
- 01
Create the Zap
Click Create, then Zap. The editor opens with an empty trigger card at the top and an action card below it. Nothing runs until you publish it at the end.
- 02
Set the trigger
Pick NotePM as the app,
New Pageas the event, then your connection. Choose the Note to watch: only pages in that Note will start this Zap. - 03
Test the trigger
Run the test. Zapier pulls the three most recent pages of that Note, so you map the next steps on a real page instead of a blank sample.
- 04
Add the filter
Click the plus icon, choose Filter, then set the field to look at, the rule and the value. This step makes the Zap multi-step, so it needs a paid plan.
- 05
Add the chat action
Add your chat app as the action, pick the channel and drop the page title and link into the message. Test the step and read what came back.
- 06
Publish
Click Publish. The Zap is now on, and since the trigger is instant, the next page written in that Note shows up in the channel at once.
NotePM triggers on Zapier
4 events start a Zap when something happens in NotePM, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.
New Comment
Instant triggerIn Zapier“Triggers when a new comment is added.”
Someone leaves a comment on a page and this trigger hands the comment to your Zap. It is the way to stop feedback from dying inside the wiki: the author gets pinged, or the remark lands in your task tracker as a to-do.
New Page or Updated Page
Instant triggerIn Zapier“Triggers when a new page is created or a page is updated.”
This one merges two events into a single stream: a page appears, or an existing page changes, and the Zap runs either way. Handy for one log of all wiki activity, with no need to maintain two Zaps side by side.
New Page
Instant triggerIn Zapier“Triggers when a new page is created.”
Fires once per page created, and ignores later edits. That makes it the right base for announcements, onboarding checklists or anything that should happen exactly one time when documentation goes live.
Updated Page
Instant triggerIn Zapier“Triggers when a page is updated.”
Only edits count here: creation is ignored, every change to an existing page starts the Zap. Use it when the version of a page matters more than its birth, such as a policy or a pricing sheet people rely on.
NotePM actions on Zapier
NotePM gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Page
ActionIn Zapier“Creates a New Page”
Writes a brand-new page into NotePM from data another app sends: a form answer, a meeting summary, an email turned into documentation. You choose the Note, then map a title and a body.
When the NotePM Zap breaks
Zapier does not attach any help article to NotePM, so the traps below are the general ones, applied to a wiki.
Most failures come from timing and from loops, not from the connection itself. Read these before you switch anything on.
Old pages are never picked up
A Zap only reacts to what happens after you publish it. Pages already in NotePM stay where they are; moving that backlog is a separate job.New Page plus Create Page in one Note
A Zap that writes into the Note its own trigger watches sets itself off again and again, and eats through your task count fast.Bulk import floods the trigger
After a migration or a mass import, a sudden batch of events can be held back by Zapier's flood protection instead of running one by one.Note missing from the dropdown
The connected account needs access to the Note. Without read or write rights there, the field stays empty and the step cannot be set.
Need help automating NotePM with Zapier?
A person reads every message.



