Notud Zapier integrationAutomate Notud with Zapier.
The Notud Zapier integration gives you 2 triggers, 4 actions and 0 searches. Handwritten client notes leave Notud as soon as they're saved, and your client list stays in step with the system you already use to manage contacts.
Verified Trustpilot reviews · AI, automation & growth agency
What the Notud Zapier integration is good for
Notud is a note-taking tool for small businesses: you write by hand on a tablet and each note lands in the right client's file in the cloud. Through Zapier and a Zap (an automation you set up once that then runs alone), those notes reach your other tools, and contacts from elsewhere can be created, updated or deactivated in Notud.
Three results people build.
Session notes where the team looks. New Note fires when a note is written for a client, and the Zap copies it into your CRM or a shared folder. A coach's handwritten notes end up next to the client's emails instead of staying on one tablet.
One client list, not two. A new customer is added in your booking or billing tool, and Create or Update Contact creates them in Notud, or refreshes their details if they're already there. Nobody types the same name twice.
Clean files when someone leaves. A client is closed in your main system, and Deactivate Contact switches them off in Notud, so the list on the tablet only shows people you still see.
What Zapier can't do with Notud: there's no search step, so a Zap can't look up a contact or read an older note. The actions only handle contacts; nothing writes a note into Notud from outside. Both triggers are instant, so no plan's polling interval slows them down.
Comparing platforms first? The n8n vs Zapier comparison and the Zapier review are the two pages to read first.
Zapier terms in plain English
Seven words cover the rest of this page. One line each.
- Zap
- Your automation on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts the Zap, such as a new client note in Notud. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, like creating a contact.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's monthly allowance counts these and nothing else.
- Instant vs polling
- An instant trigger is pushed by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it in every other case.
- Connection
- Your Notud account linked to Zapier once, then reused by every Zap and every step that reads from or writes to Notud.
What Notud Zaps cost in tasks
Notud isn't a premium app, so it runs on Zapier's free plan. You pay in tasks, and only actions that complete are counted.
- Free plan100 tasks a month, unlimited Zaps
- Zap size on Free2 steps: one trigger, one action
- Notud triggers2 of 2 instant, no waiting
- Premium appNo, Notud works on Free
The Notud trigger costs nothing: a new note or a saved change is free. Every action that succeeds afterwards costs one task, so copying a note to your CRM uses one, and copying it plus emailing the client uses two. Failed actions aren't charged. The free plan only builds two-step Zaps, one trigger and one action; adding a filter or a second action makes the Zap multi-step, which needs a paid plan. Both Notud triggers are instant, so the polling grid below never delays them.
Connect Notud to Zapier in three steps
- 01
Open the Apps page
In Zapier, open Apps and click + Add connection. You need an existing Notud account, with access to the client files the Zap will read or change inside Notud.
- 02
Choose Notud
Search for Notud in the dialog, select it, then click Add connection. A new tab opens on the Notud side, where you'll sign in with your usual account.
- 03
Sign in and grant access
Log in to Notud in that tab and allow Zapier in. The connection is saved to your list, and each Zap that uses Notud picks it up without asking you again.
Your first Zap: send each new client note to the team
GoalWhen a note is written in Notud, email it to the office and log it in a shared spreadsheet.
- 01
Build: start from Notud
Create a Zap, pick Notud and the New Note event, then your Notud connection. The trigger is instant, so the Zap will start as soon as a note is created.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent notes from your account. Pick a real one, so the next steps are mapped on actual client data and not a blank sample.
- 03
Email the note
Add your email tool as the first action and map the client's name and the note into the message. Send it to the office address so whoever is in sees it.
- 04
Log it in a sheet
Add a second action that writes a row in a shared spreadsheet. This makes the Zap multi-step, which needs a paid plan, and each note now costs two tasks.
- 05
Test, then publish
Test both actions and check the email and the row. Then click Publish to switch the Zap on. Notes written before this moment won't be sent.
Notud triggers in Zapier
2 events start a Zap when something happens in Notud, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
New Note
Instant triggerIn Zapier“Triggers when a new contact note is created in Notud.”
Starts the Zap whenever someone writes a fresh note in a client's file in Notud. It's the trigger Zapier itself puts forward for Notud.
Update Note
Instant triggerIn Zapier“Triggers when a contact note is updated (saved).”
Fires when an existing client note is changed and saved in Notud, so the other tools can catch up with the latest version.
Notud actions in Zapier
Notud gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Contact
ActionIn Zapier“Creates a new contact in Notud.”
Adds a brand new client or business to Notud, so a file is ready before the first meeting.
Create or Update Contact
ActionIn Zapier“Creates or updates contact details as applicable.”
Creates the contact if Notud doesn't have it yet, or refreshes its details if it does, in one step instead of two.
Deactivate Contact
ActionIn Zapier“Deactivates a contact if available.”
Switches off a contact in Notud when it's no longer active elsewhere, instead of leaving it in the client list.
Update Contact
ActionIn Zapier“Updates contact details if available.”
Changes the details of a contact that's already in Notud, found through its External Id.
When it breaks
Zapier links no help article to Notud, and no Notud-specific limit is documented. The cases below are the general ones that apply to any Zap, seen through client notes.
Three situations explain most surprises. When a run fails, the Zapier troubleshooting guide shows how to read the Zap history and spot the step that broke.
Old notes aren't sent
A Zap only reacts to what happens after it's published. Notes and changes made before that never go through; moving the archive is a separate job.The Zap that feeds itself
A Zap that writes back into the very place its own trigger watches sets itself off again and again, and burns through the task count fast.A bulk import held back
When a huge batch arrives at once, after a migration of client files for instance, Zapier's flood protection can hold the runs back instead of processing everything.
Need help automating Notud with Zapier?
A person reads every message.
