page/create

When to Use

• Client report generation: After a workflow gathers metrics or analysis results, create a structured report page under a client folder page with headings, tables, and text content blocks pre-populated.
• Meeting notes automation: When a calendar event ends, create a meeting notes page under the team's workspace with the meeting title, date, and attendees in the page body.
• Project wiki from template: Spin up a new project page under the team wiki with standard sections (Overview, Goals, Timeline) populated from a template at project kickoff.
• Weekly summary page: Each Monday, auto-generate a weekly summary page under the team's Updates section and populate it with data pulled from other systems.
• Incident post-mortem: When a critical incident is resolved, create a post-mortem page under the engineering runbook with incident details, timeline, and action items pre-filled from incident data.

Configuration

Authentication

Operation Fields

Sample Configuration

{
  "resource": "page",
  "operation": "create",
  "AuthenticationMethod": "ApiToken",
  "ApiToken": "{{ $credentials.notionApiToken }}",
  "ParentPageId": "{{ $vars.teamWikiPageId }}",
  "Title": "Weekly Summary — {{ $now | date: 'YYYY-MM-DD' }}",
  "Icon": "📋",
  "Blocks": [
    {
      "object": "block",
      "type": "heading_2",
      "heading_2": {
        "rich_text": [{ "type": "text", "text": { "content": "This Week" } }]
      }
    },
    {
      "object": "block",
      "type": "paragraph",
      "paragraph": {
        "rich_text": [{ "type": "text", "text": { "content": "{{ $json.summaryText }}" } }]
      }
    }
  ]
}

Validation Errors

Output

Success Port

Error Port

On failure the error port receives errorCode, message, and httpStatus. Wire to a notification node to alert on creation failures.

Sample Output

{
  "id": "a7b8c9d0-e1f2-3456-abcd-567890123456",
  "url": "https://www.notion.so/a7b8c9d0e1f23456abcd567890123456",
  "created_time": "2024-06-11T08:00:00.000Z",
  "properties": {
    "title": {
      "type": "title",
      "title": [{ "plain_text": "Weekly Summary — 2024-06-11" }]
    }
  },
  "parent": {
    "type": "page_id",
    "page_id": "b8c9d0e1-f2a3-4567-bcde-678901234567"
  }
}

Expression Reference

Node Policies & GuardRails

Workflow Examples

Example 1 — Auto Weekly Summary Page

Every Monday, create a weekly summary page under the team Updates section with data from the previous week's sprint database query.

// Step 1: ScheduledTrigger (Monday 8am)
// Step 2: database/query (last week's completed tasks)
// Step 3: Function node — build summary text
// Step 4: page/create
{
  "ParentPageId": "{{ $vars.teamUpdatesPageId }}",
  "Title": "Week of {{ $now | date: 'MMM D, YYYY' }}",
  "Icon": "📊",
  "Blocks": [{
    "object": "block", "type": "paragraph",
    "paragraph": { "rich_text": [{ "type": "text", "text": { "content": "{{ $json.summaryText }}" } }] }
  }]
}

Example 2 — Incident Post-Mortem Page

When PagerDuty marks an incident as resolved, create a post-mortem page in the engineering runbook.

// Step 1: WebhookTrigger (PagerDuty resolved)
// Step 2: page/create
{
  "ParentPageId": "{{ $vars.postMortemsPageId }}",
  "Title": "Post-Mortem: {{ $json.incident.title }}",
  "Icon": "🔴",
  "Blocks": [
    { "type": "heading_2", "heading_2": { "rich_text": [{ "text": { "content": "Incident Summary" } }] } },
    { "type": "paragraph", "paragraph": { "rich_text": [{ "text": { "content": "Severity: {{ $json.incident.severity }}" } }] } }
  ]
}
// Step 3: Store page ID and add detail blocks via block/appendChildren

Example 3 — Project Wiki Kickoff

Create a project wiki page with standard sections when a new project is registered in the system.

// Step 1: FormTrigger (new project registration)
// Step 2: page/create under team wiki page
// Standard sections: Overview, Goals, Team, Timeline
// Step 3: Share page URL with project lead via EmailSmtp