Skip to content
notionsolutions

A practical library for building,
organizing and working in Notion.

Workflow guides

Notion Zapier Integration: Connect It, First Zaps, Cost and Limits

Add Notion from Zapier's Apps page and share only the database the Zap needs. Pick a first Zap, see how tasks are counted, avoid the documented limits that break Notion Zaps, and know when Notion's own automations or Send webhook do the job without Zapier.

Published
Two white ceramic blocks on a white desk joined by a brushed-steel rod with an electric-blue glass ring around its middle, and the headline Notion and Zapier
Share one database, build one two-step Zap, and check the rows it creates before you add a second.

To connect Notion to Zapier, add Notion from Zapier's Apps page, log in to Notion, and on Notion's permission screen select only the pages or databases your Zap needs. Zapier's Free plan gives you 100 tasks per month and two-step Zaps. It can prove a simple workflow when both apps are included on Free. If the work starts and ends inside Notion, skip Zapier: Notion's own buttons and, on a paid plan, its database automations handle it without a second subscription.

Choose Zapier when the trigger or the destination lives outside Notion, such as a calendar, a form, a task app or an inbox. Choose Notion's own automations when a page being added, a property being edited or a schedule inside one database should start the work. Below you'll find the route choice, the connection on both sides, four first Zaps with the catch each one hides, how tasks are counted, and the documented limits behind most failed runs.

Do you need Zapier at all?

Start with where the data begins and where it has to end up. That one question picks the tool, and it also tells you how much of your workspace another service needs to see.

Four routes for Notion automation and when each fits
Where the work happensRouteWhat it needsWatch for
Everything happens inside NotionNotion database automations or buttonsFor most database automations, a paid Notion plan and full access to the database; check the limited Free Slack notification option belowDatabase automations can't be triggered by other automations, and they skip pages whose access is restricted
Another app sends data into NotionZapier with a Notion action, usually Create Data Source ItemA Zapier account and the target database shared with ZapierSelect options must already exist in Notion; dates go in as YYYY-MM-DD
Notion sends data to another appZapier with an Instant Notion trigger, or Notion's Send webhookZapier: the source database shared with it. Send webhook: a paid Notion plan and a receiving URLA Zap doesn't pick up items created before it was turned on; Send webhook carries properties, not page content
You write codeNotion APIA Notion connection and your own codePer-connection request limits that depend on the workspace plan

If the whole job lives in one workspace, Notion does it natively. Click ⚡ at the top of a database → New automation, then pick a trigger (Page added, Property edited or Every {frequency}) and an action such as Edit property, Add page to, Send notification to or Send webhook. Per Notion's database automations help, most database automations require a paid plan and full access to the database; guests can't create them. The help gives conflicting rules for Slack notifications on Free. Open New automation and check whether the Slack action is offered before paying for a simple notification; the customizable Slack automation actions require a paid plan. A recurring Every {frequency} trigger cannot use Edit property; choose a supported action for that schedule. Use a button for a deliberate human action and a database automation for an event or schedule; the reasoning is laid out in Notion buttons vs. database automations.

Whichever side runs it, write the handoff down first: the event, which records qualify, the target and the exceptions. That plan is the same for Notion and for Zapier, and defining the trigger, action and exception walks through it for a native handoff.

If you write code, the API removes the middle layer. Notion's API request limits allow each connection 600 requests per minute (an average of 10 per second) on Business and Enterprise and 180 requests per minute (an average of 3 per second) on all other plans. Data source queries have a separate limit of about three requests per second per connection, and connections also share a workspace budget. For HTTP 429 or 529, wait for the Retry-After value before retrying; a 429 with public_api_request_blocked needs Notion support instead. The request itself, including the data source ID and the property format, is covered in creating a page in a Notion database with the API.

Connect Notion to Zapier, step by step

Check who can connect

Zapier's getting-started help for Notion lists an active Notion account on a free or paid plan. It also says you need to be a Notion admin to the pages or databases you want to connect. Notion's connections help sets a broader rule: both Members and Workspace owners can add connections to a workspace in Settings → Connections. On the Enterprise plan, workspace owners can restrict the ability to add connections and decide who can connect or disconnect them at the page level, so on an Enterprise workspace check with an owner before you start.

On Zapier's side

  1. Go to the Apps page.
  2. Click + Add connection.
  3. Search for and select Notion.
  4. Click Add connection. A new browser tab or window opens.
  5. Log into Notion to authenticate, and grant Zapier permission to access your account if prompted.

On Notion's permission screen

The same Notion help describes the partner screen. It lists the access levels the connection requires, and connections are workspace-specific, so check the workspace name at the top right first.

  1. Click the workspace name at the top right to switch to another workspace if needed.
  2. Press Select pages.
  3. Choose the pages or databases Zapier may use, then press Allow access.

The connection then appears in Settings → Connections. Notion's Zapier connection page lists what Zapier asks for: Read, insert, & update content; Read & add comments; and View workspace users, which reads basic profile details about workspace members and guests, including their email addresses. Every page you select is one Zapier can read and change, so I'd select the one database the first Zap needs on this screen and add more pages later.

Notion page-access picker for Zapier with Tasks selected and the workspace root, Meeting Notes, Team Wiki and Archive unselected
Select the database your first Zap needs; leave unrelated pages unselected.

Support sits on Zapier's side. Notion's connection page lists Zapier as the maker and says connections not designated as Made by Notion aren't supported or maintained by Notion, and Notion's help says Notion doesn't troubleshoot partner connections, so a broken Zap goes to Zapier's support team.

Share pages you create later

Grant access when you add a separate page, database or actual data source outside the content already shared with Zapier. Notion connections inherit access to child content, so a new row inside an already permitted source is not the same as a new unrelated database. Check the source itself, its access and its ID before trying to grant every row separately. To share an additional resource:

  1. Open it and select ••• at the top right, then open More.
  2. In the Connections group, select Add connections.
  3. Search for Zapier and select it. It now appears in the ••• menu for the page.

To remove access from one page, hover over the connection's name in that menu and press Disconnect. On the Enterprise plan only, workspace owners can also grant pages centrally: Settings → Connections → Manage tab → ••• next to the connection → Manage page access → Select pages.

If a database you shared still doesn't show in Zapier's dropdown, Zapier's common-problems help for Notion gives three fixes. Check that Zapier has permission to the database. If the database is a subpage, un-nest it and temporarily make it a page, then change it back after the Zap finds it. Or create a new app account connection to Notion and refresh the fields.

Notion confirmation that Zapier will have access to this page and all child pages, with Confirm and Cancel buttons
Adding Zapier to a page also grants access to its child pages. Check the parent before confirming.

Data source IDs

Notion supports multi-sourced databases, where one database contains several linked data sources, and Zapier's help says most triggers and actions require a data source ID. That's why the step for a new database row is Create Data Source Item, which creates an item in a data source. Create Page does something else: it creates a page inside a parent page.

What Zapier can do with Notion

Every Notion trigger in Zapier's list is marked Instant: New Comment (filtered by database or a specific page), New Data Source Item, Updated Content in a Data Source item, Updated Properties in Data Source Item, Updated Content in Page and Updated Properties on a Page. Instant triggers use webhooks, and Zap workflows with instant triggers display a lightning bolt icon in the Zap editor, per Zapier's guide to how Zap triggers work.

Zapier Notion event field set to New Data Source Item with Change and Continue controls
Choose New Data Source Item for a newly created row. Page-body edits need an Updated Content trigger.

The searches and actions matter more than the triggers, because the step you pick decides whether a run adds a row, updates one or creates a page somewhere else. These are the steps I'd reach for first.

Which Zapier step does the Notion job
JobZapier stepWhat to know
Add a row to a databaseCreate Data Source ItemNeeds the data source ID
Change a row the Zap already foundUpdate Data Source ItemMulti-select values are overwritten, not appended
Avoid duplicate rowsFind or Create Data Source ItemFinds an item or creates one if it is missing; the getting-started help calls it Find or Create Database Item
Look a row up by its fieldsFind Data Source ItemsFinds data source items by their properties
Write into a page bodyAdd Content to Page or Add Block to PageEach block is limited to 2,000 characters
Create a standalone pageCreate PageCreates the page inside a parent page, not a database
Read a page's body after a triggerGet Page and Children or Retrieve Block ChildrenRetrieve Block Children returns text content rendered as Markdown
Attach a fileUpload File to Data Source Item or Upload File to Page or BlockPick the step that matches where the file belongs
Remove a row without losing itArchive Data Source ItemSoft deletes the item; Restore Data Source Item restores an archived one
Reply in a discussionAdd CommentAdds a new comment to a page
Anything the list lacksAPI Request (Beta)A raw HTTP request that includes the integration's authentication

Four first Zaps worth building

Each of these starts from a template on Zapier's Notion integrations page. The template wires the trigger to the action; the gotcha is the part you still have to decide.

Calendar events into a Notion database

Template: "Add new Google Calendar events to databases in Notion", with an Outlook version called "Add new Microsoft Outlook calendar events to Notion databases". The trigger is a new event in the calendar app; the action is Create Data Source Item in your meetings or schedule database.

The gotcha is dates. Notion expects YYYY-MM-DD (ISO 8601), and when you send a date, time and timezone into a date field, Zapier recommends a Formatter step. If no timezone is set in your Zapier account or in the Zap, Zapier uses UTC, so set it to match Notion before the first run. Formatter doesn't use tasks, but it is an extra step, and the Free plan lists two-step Zaps only.

Form submissions into a database

Template: "Generate items in Notion databases with new Jotform submissions". Trigger: a new submission. Action: Create Data Source Item in your intake database.

The gotcha is select fields. Zapier can only add options that match what you have in Notion, so a form answer that isn't an existing option needs that option created in Notion first. Picking the form tool itself is a separate decision, compared in connecting a form to a Notion database.

Tasks from a task app

Template: "Save new tasks in Google Tasks in Notion databases". Trigger: a new task. Action: Create Data Source Item in your task database.

The gotcha is the backlog. Zaps don't trigger for old data, including data created before the Zap was turned on, and Zapier points to its Transfer feature for moving existing items. Testing an instant trigger retrieves the three most recent items, and Zapier warns that test records may not match the data your Zap receives during live runs, so check the first live rows as well as the test.

New Notion items out to another app

Template: "Generate detailed events in Google Calendar from new Notion database items". Trigger: New Data Source Item. Action: create the event in the other app. The same trigger feeds team-chat and email templates, such as Slack messages, Discord channel messages or Gmail drafts for new database items.

This direction has three gotchas:

And never point the action back at the database this trigger watches. Zapier warns that writing to the same app and resource the trigger monitors can retrigger the Zap in an infinite loop that burns through tasks.

What Notion and Zapier cost together

Zapier sells this service, so the plan details below come from its own pricing page, as worded there.

Zapier plans as listed on its pricing page
PlanPrice as listedWhat matters for Notion Zaps
Free$0/month, 100 tasks per monthTwo-step Zaps; unlimited Zaps, Tables and Forms; one user
ProfessionalFrom US$19.99/month billed annuallyMulti-step Zaps, unlimited premium apps and Webhooks; one user
TeamFrom US$69/month billed annually25 users, shared Zaps and folders, shared app connections
EnterpriseContact for pricingUnlimited users and advanced admin permissions and app controls

Paid plans have several task tiers; select the tier before comparing the total. Committing to annual payments lowers the monthly fee. A new Zapier account is enrolled in a free 14-day trial of the Professional plan, and no credit card is required.

Tasks are the unit that runs out. Each successful action in a Zap counts as a separate task, and some apps or actions use more than one. Triggers don't count, a failed action doesn't count, and neither do Filter by Zapier, Formatter by Zapier, Path by Zapier, Delay, Looping, Sub-Zap, Digest, Zapier Manager, Storage, Zapier Tables or Zapier Forms.

On paid plans, pay-per-task billing keeps Zaps running after the plan allowance runs out when the feature is enabled. Extra tasks cost more per task, and Zaps pause at the maximum usage limit. Free has no pay-per-task option. With pay-per-task billing turned off, Zaps pause at the plan limit until the next usage period. Check Billing settings before turning on a high-volume Zap; Zapier emails you near the limit and when you reach it.

On the Notion side, Zapier's prerequisites accept a free or paid Notion account. Send webhook and most native database automations need a paid Notion plan. For a simple Slack notification, check whether your Free workspace offers the native action before paying for another tool.

Limits that break Zaps

Zapier's Notion help and its trigger guide document the failure points below. Most are permission or data-shape problems you can rule out before the Zap goes live.

Notion's Send webhook as the alternative

When Notion is the source and the receiving service accepts a webhook, Notion can post the data itself. Per Notion's webhook actions help, Send webhook works in buttons, database buttons and database automations, sends an HTTP POST request to a URL you enter, and is available to users on paid plans.

  1. In a button, database button or database automation, select Add action.
  2. Select Send webhook.
  3. Enter the URL. Any custom URL can be used.
  4. If the receiver checks a header, select Add custom header and enter its Key and Value.
  5. In a database automation, select the properties to send. Database button properties can't be selected.

The limits are tighter than Zapier's. The action doesn't require authentication, it sends only database page properties and never page contents, an automation can hold up to five webhook actions, and only POST is supported. There's no payload preview; Notion suggests a site such as webhook.site to inspect what arrives. If the action fails, an exclamation mark shows next to where you set up the automation and the automation pauses. For a database automation, after fixing it, open the database and select ••• → Automations, hover over the automation, select •••, and toggle on Active.

Two more boundaries. On the Enterprise plan, a workspace owner can turn the action off for everyone under Settings → Connections by toggling off Allow webhooks in automations. And database automations can't be triggered by other automations, though button actions can trigger them. A recurring template automation won't start a database automation either, the problem behind a repeating template that doesn't trigger its automation.

If the receiver is Zapier itself, the webhook route costs more than it saves. Zapier's pricing page lists Webhooks under Professional, and Send webhook needs a paid Notion plan, while an Instant Notion trigger works without Zapier's Webhooks feature and without a paid Notion plan. I'd use Send webhook only when the receiving service is your own endpoint or another tool that accepts the POST directly.

Troubleshooting Notion Zaps

Common Notion Zap failures, their documented causes and fixes
SymptomDocumented causeFix
The database isn't in Zapier's dropdownZapier has no access, or the database is a subpageShare it with Zapier in Notion; temporarily un-nest a subpage; or create a new Notion connection in Zapier and refresh fields
A newly added page or source is missingIt may be outside the permitted branch, or the Zap may target a different sourceCheck the source and ID. For a separate unshared resource: page ••• → More → Connections group → Add connections
A Formula or Rollup field isn't listedThose property types aren't supportedMap the underlying fields; let Notion calculate
A select value won't saveZapier can only use options that exist in NotionAdd the option in Notion first
Dates land on the wrong day or hourWrong format, or the UTC default timezoneUse YYYY-MM-DD, add Formatter for date and time, set the Zapier timezone to match Notion
Tags vanish after an updateMulti-select updates overwrite existing valuesSend every value the row should keep
The trigger output has no page contentNew Data Source Item returns the item, not its blocksAdd Get Page and Children or Retrieve Block Children after the trigger
Editing page text doesn't start the ZapContent updates don't trigger New Data Source ItemSwitch to Updated Content in Page or Updated Content in a Data Source item
The Zap runs for rows it shouldn'tThe trigger fires on every new or updated itemAdd a filter for the conditions that matter
The task count jumpsThe Zap writes back to the resource its trigger monitors, creating a loopPoint the action at a different database than the trigger watches
"Unexpected error" with DOCTYPE html in the runZapier had temporary trouble communicating with Notion's serversCheck Notion's status page, then replay failed Zap runs
Older items never arriveZaps don't trigger for data created before they were turned onMove the backlog with Zapier's Transfer feature

Which Zapier plan fits your workflow?

Plan fit follows from the app list, step count and usage: Free needs apps included on Free and a two-step Zap; successful actions use tasks. Here is what that means for the Zaps above.

How common Notion Zap shapes map to Zapier plans and tasks
Zap shapeSteps that use tasksLowest plan that fits
Calendar event → Create Data Source ItemThe Notion actionFree when both apps are included on Free
Calendar event → Formatter → Create Data Source ItemThe Notion action; Formatter doesn't countProfessional (multi-step Zap)
New Data Source Item → Filter → action in another appThe other app's action; Filter doesn't countProfessional (multi-step Zap)
Notion Send webhook → Zapier webhook trigger → actionThe action after the webhook triggerProfessional (Webhooks), plus a paid Notion plan

My reading: Zapier's Notion app is broad, with instant triggers and page, database, comment and file actions, but many failures covered here come from permissions, field formats or trigger design; rate limits and temporary service errors need their own checks. Grant pages explicitly, keep Formula and Rollup out of the Zap, format dates, and never write back to the database the trigger watches.

Verdict: when Zapier earns its place

Start by asking whether another app is involved at all. If the work starts and ends inside Notion, such as status changes, assignments or a page created from a button, Notion's own buttons and, on a paid plan, its database automations do it without a second subscription. Zapier earns its place when the trigger or the destination lives outside Notion: a form, a calendar, an inbox, a task app.

For one two-step handoff using apps included on Free, start with Zapier Free; its 100 tasks per month and two-step Zaps are enough to prove the workflow. For Zaps that need Formatter, a filter or a search step, choose Professional, because each one adds a step beyond the Free plan's two; Webhooks sit on Professional as well. Before you turn anything on, share only the one database the Zap needs, keep Formula and Rollup fields out of it, set Zapier's timezone, and never let a Zap write back to the database its trigger watches.

The low-risk trial path I'd follow:

  1. Pick one database and share only that database with Zapier.
  2. Build one two-step Zap from another app into Notion with Create Data Source Item.
  3. Test it, turn it on, and let real items arrive.
  4. Check the task count and the created pages: dates, select values and multi-select fields.
  5. Only then add a second Zap or a second database.

Zapier moves the data; deciding which records it may touch, and which database is the source of truth, stays with you.

Questions people ask about Notion and Zapier

Does Zapier work with a free Notion plan?

Yes. Zapier's prerequisites list an active Notion account on a free or paid plan. Send webhook and most native database automations need a paid Notion plan. For a simple Slack notification, check whether your Free workspace offers the native action before adding Zapier.

Can Zapier read the text inside a Notion page?

It can, with one extra step. A row trigger returns the item; add Get Page and Children or Retrieve Block Children after it, and Retrieve Block Children returns the text as Markdown.

Can I remove Zapier from one page without disconnecting everything?

You can. Open the page's ••• menu, hover over Zapier's name among its connections and press Disconnect. That removes the connection from that page.

Automate the next step