trigger/pageAdded

When to Use

• New form submission processing: When users submit a BizFirst Form or a third-party form that writes to a Notion database, this trigger starts a workflow for each new submission row — enabling routing, validation, and downstream system integration.
• Employee onboarding kickoff: When HR adds a new employee page to the onboarding database, trigger an automated onboarding workflow that provisions accounts, sends welcome emails, and schedules check-in meetings.
• New project notifications: Notify the team in Slack when a new project page is added to the project tracking database, including key fields like project lead, start date, and priority.
• CRM-to-external system sync: Sync each new Notion CRM record to Salesforce or HubSpot as a new lead, running deduplication and enrichment steps before writing to the external system.
• Content pipeline initiation: When a new content brief is added to the editorial calendar database, trigger a workflow that assigns a writer, sets deadlines, and notifies stakeholders.

Configuration

Authentication

Trigger Fields

Sample Configuration

{
  "resource": "trigger",
  "operation": "pageAdded",
  "AuthenticationMethod": "ApiToken",
  "ApiToken": "{{ $credentials.notionApiToken }}",
  "Database": "{{ $vars.submissionsDatabaseId }}",
  "PollingInterval": "*/2 * * * *"
}

Validation Errors

Output

Trigger Output (per new page)

Error Port

On poll failure the error port receives errorCode, message, and httpStatus. Wire to a notification node to alert on persistent authentication or permission failures.

Sample Output

{
  "id": "e5f6a7b8-c9d0-1234-efab-345678901234",
  "url": "https://www.notion.so/e5f6a7b8c9d01234efab345678901234",
  "created_time": "2024-06-11T10:45:00.000Z",
  "last_edited_time": "2024-06-11T10:45:00.000Z",
  "properties": {
    "Name": {
      "type": "title",
      "title": [{ "plain_text": "New Support Request: Login Issue" }]
    },
    "Status": {
      "type": "select",
      "select": { "name": "Open" }
    },
    "Email": {
      "type": "email",
      "email": "customer@example.com"
    },
    "Priority": {
      "type": "select",
      "select": { "name": "High" }
    }
  },
  "parent": {
    "type": "database_id",
    "database_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  }
}

Expression Reference

Node Policies & GuardRails

Workflow Examples

Example 1 — New Support Ticket Routing

When a support request is added to the Notion support database, route it by priority to the appropriate Slack channel.

// Trigger: trigger/pageAdded (Support Requests DB)
// Step 1: IfCondition
// Condition: {{ $trigger.properties.Priority.select.name }} === "High"
// True: Slack #p1-support channel
// False: Slack #general-support channel

// Slack message:
{
  "text": "New support ticket: {{ $trigger.properties.Name.title[0].plain_text }}\nEmail: {{ $trigger.properties.Email.email }}\n{{ $trigger.url }}"
}

Example 2 — New Employee Onboarding Kickoff

Trigger an onboarding workflow when HR adds a new employee record to the Notion HR database.

// Trigger: trigger/pageAdded (HR Employees DB)
// Step 1: user/getMany — build manager lookup map
// Step 2: EmailSmtp — welcome email to new employee
// Step 3: Jira issue/create — provision access request ticket
// Step 4: page/update — set Status to "Onboarding In Progress"

Example 3 — Notion-to-CRM Sync on New Record

Each new CRM contact added to Notion is synced to an external CRM system after deduplication.

// Trigger: trigger/pageAdded (Contacts DB)
// Step 1: HttpRequest — check if email already exists in CRM
// Step 2: IfCondition — exists in CRM?
// False: HttpRequest POST → create contact in CRM
//        page/update → set NotionSynced = true
// True: log duplicate and stop