NOTION n8n INTEGRATION: AUTOMATE NOTION WITH N8N

This action creates a new page inside a specified Notion database, complete with properties you define. It's one of the most frequently used Notion actions in n8n because it enables you to push data from any source directly into your Notion workspace.

Key parameters:

• Credential to connect with: Your Notion OAuth2 credential. Required.
• Database: Select the target database (by ID) where the new page will be created. Required.
• Title: The title of the new page—accepts text input and dynamic expressions from previous nodes. Required.
• Simplify: Toggle for streamlined output formatting. Optional.
• Properties: Add custom property values (text, select, multi-select, date, etc.) that match your database schema. Optional but typically essential.
• Blocks: Add content blocks (paragraphs, headings, lists) directly to the page body. Optional.

Use cases:

• Create a new lead entry when a form is submitted on your website
• Add a task to your Notion project tracker when a GitHub issue is opened
• Generate a meeting notes page automatically when a calendar event starts

This action adds new content blocks to an existing Notion page. Use it to programmatically build out page content—adding paragraphs, to-do items, headings, or any other block type Notion supports.

Key parameters:

• Credential to connect with: Your Notion credential. Required.
• Block: Specify the parent block or page (by URL or ID) where new blocks will be appended. Required.
• Blocks: Define the content blocks to add—click "Add Block" to configure each one. Optional but central to the action's purpose.

Use cases:

• Append daily standup notes to a running team log page
• Add new bullet points to a meeting agenda as items come in via Slack
• Build out documentation pages incrementally from external data sources

This action retrieves all child blocks nested within a specified parent block. It's essential for reading page content programmatically—whether you need to process, transform, or sync that content elsewhere.

Key parameters:

• Credential to connect with: Notion credential. Required.
• Block: The parent block (by URL or ID) whose children you want to retrieve. Required.
• Return All: Toggle to fetch every child block without pagination limits. Optional.
• Limit: Maximum number of blocks to retrieve (default: 50). Required if Return All is off.
• Also Fetch Nested Blocks: Toggle to retrieve blocks nested within child blocks for deeper content extraction. Optional.
• Simplify Output: Returns a cleaner data structure. Optional.

Use cases:

• Extract all content from a Notion page for backup or migration
• Process page content to generate summaries or analytics
• Sync Notion content to a CMS or website builder

This action searches within a specific database, letting you find pages that match your criteria. It's incredibly useful for retrieving records before updating them or checking if an entry already exists.

Key parameters:

• Credential to connect with: Notion credential. Required.
• Search Text: The keyword or phrase to search for within database entries. Optional but typically used.
• Return All: Retrieve all matching results. Optional.
• Limit: Maximum results to return (default: 50). Required if Return All is off.
• Simplify: Streamlined output format. Optional.

Use cases:

• Find a contact record before updating it with new information
• Check if a task already exists before creating a duplicate
• Retrieve all entries matching a specific project name for reporting

This action retrieves metadata and schema information about a specific Notion database—its properties, structure, and configuration details. It's useful for dynamic workflows that need to understand database structure.

Key parameters:

• Credential to connect with: Notion credential. Required.
• Database: Select the database to retrieve (by ID). Required.
• Simplify: Returns simplified metadata. Optional.

Use cases:

• Dynamically build forms based on database property structure
• Validate database schema before bulk operations
• Document your Notion workspace structure automatically

This action retrieves a list of multiple databases from your Notion workspace. It's helpful for workspace auditing, building database selection interfaces, or iterating across multiple databases programmatically.

Key parameters:

• Credential to connect with: Notion credential. Required.
• Return All: Fetch all accessible databases. Optional.
• Limit: Maximum databases to retrieve. Optional.
• Simplify: Simplified response format. Optional.

Use cases:

• Generate a workspace inventory showing all databases
• Build a selection menu for user-facing automation interfaces
• Audit database access and permissions

This action archives a specified Notion page, effectively soft-deleting it from active view while preserving its data. It's the standard way to clean up completed or obsolete pages programmatically.

Key parameters:

• Credential to connect with: Notion credential. Required.
• Page: Identify the page to archive (by URL or ID). Required.
• Simplify: Simplified confirmation output. Optional.

Use cases:

• Archive completed project pages after a defined period
• Clean up test entries created during automation development
• Implement "soft delete" functionality triggered by external events

This action retrieves a single specific page from a Notion database, returning all its properties and metadata. Use it when you need complete details about one particular entry.

Key parameters:

• Credential to connect with: Notion credential. Required.
• Database Page: Specify the page (by URL or ID). Required.
• Simplify: Returns cleaner data structure. Optional.

Use cases:

• Fetch full details of a lead record for personalized email content
• Retrieve task information to include in a status report
• Get page data before performing conditional updates

This action retrieves a list of users from your Notion workspace—team members with access to the shared workspace. Useful for user management workflows and access auditing.

Key parameters:

• Credential to connect with: Notion credential. Required.
• Return All: Fetch all workspace users. Optional.
• Limit: Maximum users to retrieve (default: 50). Optional.

Use cases:

• Sync Notion users with your HR system or directory
• Generate reports on workspace membership
• Validate user access as part of onboarding/offboarding workflows

This action retrieves details about a specific Notion user by their User ID. It returns profile information useful for personalization or identity verification in workflows.

Key parameters:

• Credential to connect with: Notion credential. Required.
• User ID: The unique identifier of the user to retrieve. Required.

Use cases:

• Personalize notifications with user names from Notion user data
• Verify user identity before executing sensitive operations
• Enrich records with user profile details

This action searches across all pages (not just within a database) in your Notion workspace. It's broader than database search and useful for finding content across your entire workspace.

Key parameters:

• Credential to connect with: Notion credential. Required.
• Search Text: The keyword or phrase to find. Required.
• Return All: Retrieve all matching pages. Optional.
• Limit: Maximum results (default: 50). Optional.
• Simplify: Cleaner response format. Optional.

Use cases:

• Find all pages mentioning a specific client name
• Locate documentation pages for a particular feature
• Build a workspace-wide search interface

This action retrieves multiple pages from a specific database—essentially a bulk read operation. It supports filtering to narrow down results based on property conditions.

Key parameters:

• Credential to connect with: Notion credential. Required.
• Database: The database to query. Required.
• Return All: Fetch all pages in the database. Optional.
• Limit: Maximum pages to retrieve (default: 50). Optional.
• Simplify: Simplified output format. Optional.
• Filter: Apply conditions to narrow results (by property values, dates, etc.). Optional.

Use cases:

• Export all records from a database to a spreadsheet
• Retrieve active tasks for a daily summary report
• Sync entire database contents to an external system

This action creates a standalone page (not a database entry) within your Notion workspace. It's used for creating regular pages nested under a parent page.

Key parameters:

• Credential to connect with: Notion credential. Required.
• Parent Page: Where the new page will live (by URL or ID). Optional.
• Title: The page title. Required.
• Simplify: Simplified confirmation output. Optional.
• Blocks: Add content blocks to the page body. Optional.

Use cases:

• Create meeting notes pages under a Meetings parent page
• Generate documentation pages from templates
• Build hierarchical page structures programmatically

This action modifies an existing page in a Notion database—updating properties, changing status, editing content. It's essential for keeping Notion data current with changes from external systems.

Key parameters:

• Credential to connect with: Notion credential. Required.
• Database Page: The page to update (by URL or ID). Required.
• Simplify: Simplified response format. Optional.
• Properties: Specify which properties to update and their new values. Optional but typically central to the action.

Use cases:

• Update deal status when it changes in your CRM
• Mark tasks complete when they're closed in another project tool
• Sync updated contact information from forms or other sources