- Home
- Resources
- Integrations
- Notifii
Notifii Zapier integrationAutomate Notifii with Zapier.
The Notifii Zapier integration gives you 0 triggers, 1 action and 0 searches. That one action keeps your Notifii recipient list current: a new employee or resident added in another tool shows up in the mailroom's directory without anyone typing it twice.
Verified Trustpilot reviews · AI, automation & growth agency
What the Notifii Zapier integration does for your mailroom
The Notifii Zapier integration lets other apps add or update recipients in Notifii, the tool that tracks packages and notifies people in corporate mailrooms and apartment offices. When a person appears or changes in your HR, CRM or leasing tool, Zapier writes them into Notifii. It works one way: Notifii receives, it starts nothing.
Three results teams build first. New hires ready for their first parcel: a new employee in your HR tool becomes a recipient through Add/Update Recipient, so the mailroom can log a delivery for them from day one. New tenants in the directory on move-in: a signed lease or a new contact in your leasing tool adds the resident, and front desk staff find them at the first package. Name changes that follow through: when a record changes in the source tool, the same action updates the recipient instead of leaving an outdated entry.
All three rely on the same single step, which is why the source tool matters more than the Notifii side.
What the integration does not do: Notifii has no trigger on Zapier, so a package being logged or picked up cannot start a Zap, and there is no search. You cannot read deliveries or remove a recipient from Zapier. If you want package events to reach other tools, this integration does not cover it. The Zapier review explains where Zapier fits, and the Make vs Zapier comparison helps if you need more than a one-way sync.
Zapier vocabulary in one minute
Seven words come back on this page. Here they are, in plain terms.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. With Notifii it always comes from another app, since Notifii has none.
- Action
- What the Zap does once it has started: here, the step that adds or updates a recipient in Notifii.
- Task
- The unit Zapier bills. One action completed 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 its app the moment the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your Notifii account linked to Zapier once, then reused by every Notifii step in every Zap you build.
What Notifii on Zapier really costs
Notifii is not a premium app, so it works from the free plan. You pay in tasks, and each recipient added or updated is one.
- Premium appNo, works on the free plan
- Free plan100 tasks per month, two-step Zaps
- Cost per recipientOne task when it succeeds
- Notifii triggersNone, the trigger comes from another app
The trigger, wherever it lives, never costs a task, and Zapier checking for new records is free too. Each Add/Update Recipient that succeeds counts once; one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. A plain Notifii Zap fits that shape exactly. Add a filter or a second action and it becomes multi-step, which needs a paid plan. The trigger comes from another app, so the interval grid below applies whenever that trigger is a polling one.
Connect your Notifii account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. In the dialog, type Notifii in the search box and pick it from the list of matching apps.
- 02
Sign in to Notifii
Click Add connection. Notifii opens in a new tab: sign in with the account that manages the recipient list of your mailroom or front desk, so new entries land in the right directory.
- 03
Grant access
Allow Zapier to use the account. The tab closes and the connection appears in your list, ready for every Notifii step you add to a Zap, without signing in again.
Your first Zap: new hires straight into the mailroom directory
GoalEach new employee in your HR tool who passes a filter is added as a Notifii recipient.
- 01
Create the Zap
Click Create, then Zap. The editor opens with an empty trigger card and an action card under it. Nothing runs until you publish.
- 02
Set the trigger in your HR tool
Notifii has no trigger, so pick the app where people are created, here your HR tool, choose the new employee event and connect that account.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent items of that account, so you map the next steps on a real employee instead of a blank sample.
- 04
Add the filter
Click the plus icon, choose Filter, then set the location field, a text rule and the site name. The filter makes the Zap multi-step, so it needs a paid plan.
- 05
Add Add/Update Recipient
Pick Notifii and
Add/Update Recipient, select your connection, then map the first name and last name from the employee record. Test the step and read what came back. - 06
Publish
Click Publish. The Zap is on, and the next hire at that site is in Notifii before their first package arrives at the desk.
Notifii actions on Zapier
Notifii 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
Add/Update Recipient
ActionIn Zapier“Adds a new recipient or updates an existing recipient.”
Creates a recipient in Notifii, or updates one that is already there, from a person record sent by another app. The mailroom then finds that person when a delivery comes in, with no manual entry at the desk.
When the Notifii Zap breaks
Zapier attaches no help article to Notifii, so these are the general traps, applied to a recipient directory.
With a single action, failures usually sit in the source data or in the trigger app. The Zapier troubleshooting guide covers the wider list.
A name field arrives empty
Add/Update Recipient needs both a first and a last name. A source record with only a full name, or a blank surname, makes the step fail for that person.New people show up late
Timing depends on the trigger app. A polling trigger is checked every 15 minutes on the free plan, so the recipient waits for that check.Existing staff are never imported
A Zap only reacts to what happens after you publish it. People already in your HR or leasing tool are not added; that first import is a separate job.A bulk upload gets held back
If the trigger app suddenly returns a huge batch, after a migration or a move-in wave, Zapier's flood protection can hold it back instead of running each record.
Need help automating Notifii with Zapier?
A person reads every message.



