How to Send Notion Database Updates to Slack with n8n

notion.so/my-integrations > New Integration > Capabilities

Create a Notion Integration and Share Your Database

Before n8n can read your Notion database, you need an internal integration token. Go to notion.so/my-integrations, click 'New integration', name it (e.g. 'n8n Notifier'), and set the capability to 'Read content'. Copy the Internal Integration Token — you'll paste it into n8n next. Then open the Notion database you want to monitor, click the three-dot menu in the top right, scroll to 'Connections', and add your new integration by name.

1. 1Go to notion.so/my-integrations and click '+ New integration'
2. 2Name the integration 'n8n Notifier' and select your workspace
3. 3Under Capabilities, check 'Read content' only — uncheck Insert and Update
4. 4Click Submit and copy the 'Internal Integration Token'
5. 5Open your Notion database, click '···' (top right), go to Connections, and add 'n8n Notifier'

n8n Dashboard > Add Workflow

Create a New Workflow in n8n

Open your n8n instance (cloud at app.n8n.io or self-hosted). Click 'Add workflow' in the left sidebar. Give it a clear name like 'Notion → Slack Row Notifications'. You'll land on a blank canvas with a single Start node. This is where you'll build the polling trigger.

1. 1Click 'Add workflow' in the left sidebar
2. 2Click the workflow title at the top and rename it to 'Notion → Slack Row Notifications'
3. 3Click the Start node on the canvas to see your trigger options

Canvas > + > Schedule Trigger

Add a Schedule Trigger Node

Since Notion doesn't offer native webhooks, you'll poll on a schedule. Click the '+' button on the canvas, search for 'Schedule Trigger', and add it. Set the interval to every 5 minutes — this is the lag time between a Notion change and the Slack message. For most teams, 5 minutes is fine. If your team needs faster alerts, 1 minute is the floor before you hit Notion API rate limits under load.

1. 1Click the '+' icon on the blank canvas
2. 2Search 'Schedule' and select 'Schedule Trigger'
3. 3Set 'Trigger Interval' to 'Minutes'
4. 4Set the value to '5'
5. 5Click outside the node to close the panel

Canvas > + > Notion > Database Page > Get Many

Add a Notion Node to Query the Database

Click '+' after the Schedule Trigger and search for 'Notion'. Select the Notion node and set Operation to 'Get Many' under the 'Database Page' resource. Connect your Notion credentials by clicking 'Credential for Notion API' and pasting your Internal Integration Token from Step 1. Set the Database ID — you can find this in the Notion database URL: it's the 32-character string after the last slash and before the '?v=' parameter. Enable 'Return All' if your database has under 500 rows; otherwise set a page size of 100.

1. 1Click '+' after the Schedule Trigger and search 'Notion'
2. 2Select 'Notion' node, set Resource to 'Database Page', Operation to 'Get Many'
3. 3Click 'Credential for Notion API', select 'Create New', and paste your integration token
4. 4Paste your Notion Database ID into the 'Database ID' field
5. 5Toggle 'Return All' on (or set Page Size to 100 for large databases)

Canvas > + > Code

Add a Code Node to Filter New and Updated Rows

This is the critical step. Notion has no built-in 'changed since last poll' filter via the API, so you need to compare timestamps in code. Add a Code node after the Notion node. You'll write logic that checks each row's 'created_time' and 'last_edited_time' against a threshold (the last poll time minus a buffer). The pro tip section below has the full working code. This node outputs only the rows that are new or changed since the last execution.

1. 1Click '+' after the Notion node and search 'Code'
2. 2Select the 'Code' node (JavaScript mode is default)
3. 3Paste the code from the Pro Tip section below into the code editor
4. 4Click 'Test step' to verify filtered rows appear in the output panel

Paste this into the Code node (Step 5). It reads the last-processed timestamp from n8n static workflow data, filters Notion rows to only those created or edited after that threshold, marks new vs. updated rows, persists the new high-water mark timestamp, and deduplicates by page ID across executions. The POLL_WINDOW_MINUTES buffer (set to 6) overlaps slightly with the 5-minute schedule to catch rows that land on a boundary.

// n8n Code Node — Filter new/updated Notion rows and deduplicate
// Paste this into the Code node between the Notion node and the IF node
const POLL_WINDOW_MINUTES = 6; // Slightly wider than your 5-min schedule interval

// n8n Code Node — Filter new/updated Notion rows and deduplicate
// Paste this into the Code node between the Notion node and the IF node

const POLL_WINDOW_MINUTES = 6; // Slightly wider than your 5-min schedule interval

// Get persisted state from n8n static workflow data
const staticData = $getWorkflowStaticData('global');
const lastRunTimestamp = staticData.lastRunTimestamp
  ? new Date(staticData.lastRunTimestamp)
  : new Date(Date.now() - POLL_WINDOW_MINUTES * 60 * 1000);

const processedIds = new Set(staticData.processedIds || []);

const now = new Date();
const cutoff = new Date(now.getTime() - POLL_WINDOW_MINUTES * 60 * 1000);
// Use the later of: lastRunTimestamp or the rolling window
const threshold = lastRunTimestamp > cutoff ? lastRunTimestamp : cutoff;

const allItems = $input.all();
const filteredItems = [];

for (const item of allItems) {
  const row = item.json;
  const pageId = row.id;
  const createdAt = new Date(row.created_time);
  const editedAt = new Date(row.last_edited_time);

  const isNew = createdAt >= threshold;
  const isUpdated = editedAt >= threshold && !isNew;

  // Skip if we've already sent a notification for this exact edit cycle
  const dedupeKey = `${pageId}_${row.last_edited_time}`;
  if (processedIds.has(dedupeKey)) continue;

  if (isNew || isUpdated) {
    // Resolve the page title safely
    const titleArr = row.properties?.Name?.title;
    const title = titleArr && titleArr.length > 0
      ? titleArr[0].plain_text
      : '(Untitled)';

    const status = row.properties?.Status?.select?.name || 'No status';
    const assignee = row.properties?.Assignee?.people?.[0]?.name || 'Unassigned';
    const dueDate = row.properties?.['Due Date']?.date?.start || 'No due date';
    const editedBy = row.last_edited_by?.name || 'Unknown';
    const pageUrl = row.url || '';

    filteredItems.push({
      json: {
        pageId,
        dedupeKey,
        changeType: isNew ? 'NEW' : 'UPDATED',
        title,
        status,
        assignee,
        dueDate,
        editedBy,
        pageUrl,
      }
    });

    // Track this ID so future polls don't re-send it
    processedIds.add(dedupeKey);
  }
}

// Persist state — cap processedIds to last 500 to avoid unbounded growth
const idsArray = Array.from(processedIds);
staticData.processedIds = idsArray.slice(-500);
staticData.lastRunTimestamp = now.toISOString();

return filteredItems;

Canvas > + > IF

Add an IF Node to Handle Empty Results

When nothing changed in Notion, the Code node returns an empty array. You need an IF node to stop the workflow there instead of sending blank Slack messages or hitting errors. Add an IF node after the Code node. Set the condition to check if the item count is greater than 0 using the expression '{{ $input.all().length > 0 }}'. Connect the 'true' branch to your next step. The 'false' branch needs no connection — n8n will stop silently.

1. 1Click '+' after the Code node and search 'IF'
2. 2Set Condition type to 'Expression'
3. 3Enter the expression: {{ $input.all().length > 0 }}
4. 4Leave the False branch unconnected

Canvas > + > Slack > Credentials > OAuth2

Connect Slack Credentials

Click '+' on the true branch of the IF node and search 'Slack'. Select the Slack node. For credentials, click 'Credential for Slack API' and choose 'OAuth2' — this is the recommended method. Click 'Connect', sign into your Slack workspace, and authorize n8n to post messages. You'll need the 'chat:write' scope at minimum. If you want to tag users in notifications, also add 'users:read'.

1. 1Click '+' on the IF node's true branch and search 'Slack'
2. 2Select the Slack node, set Resource to 'Message', Operation to 'Send'
3. 3Click 'Credential for Slack API', select 'Create New', choose 'OAuth2'
4. 4Click 'Connect my account' and authorize in the Slack popup
5. 5Confirm the green 'Connected' indicator appears next to the credential name

Slack Node > Parameters > Channel / Message Text

Configure the Slack Message

Set the Channel field to your target channel name (e.g. '#project-updates'). In the Message Text field, build a dynamic message using n8n expressions that pull values from the Notion row. Set Message Type to 'Block Kit' for formatted output, or use plain text for simplicity. A good plain-text template: '📋 Notion Update: *{{ $json.properties.Name.title[0].plain_text }}* — Status: {{ $json.properties.Status.select.name }} — Updated by: {{ $json.last_edited_by.name }}'.

1. 1Type your channel name in the 'Channel' field (include the # prefix)
2. 2Click the 'Message Text' field and switch to Expression mode (lightning bolt icon)
3. 3Paste your message template with dynamic {{ $json.properties... }} references
4. 4Optionally set 'Message Type' to 'Block Kit' for richer formatting
5. 5Click 'Test step' to send a test message to your Slack channel

Code Node > JavaScript Editor

Add Deduplication Using n8n Static Data

To prevent the same row triggering a Slack message twice across poll cycles, store the last-processed row IDs in n8n's static workflow data. In the Code node from Step 5, use $getWorkflowStaticData('global') to read and write a Set of processed IDs. The pro tip code handles this automatically. This is the most important production safeguard for polling-based notification workflows.

1. 1Open the Code node from Step 5
2. 2Confirm the static data read/write logic is present in your code (see Pro Tip)
3. 3Run a test execution and check that the same row does not produce two Slack messages
4. 4Open n8n's execution log and verify only new rows appear in Code node output

Workflow Canvas > Top Bar > Active Toggle

Set the Poll Interval and Activate the Workflow

Go back to the Schedule Trigger node and confirm the interval. For most teams, 5 minutes balances freshness against API usage. Click 'Save' in the top right, then toggle the workflow from 'Inactive' to 'Active' using the toggle in the top bar. n8n will now run the workflow automatically on your schedule. Check the Executions tab after 10 minutes to confirm it's running and the Notion node is returning data.

1. 1Click 'Save' in the top right corner
2. 2Toggle the workflow status from 'Inactive' to 'Active'
3. 3Wait 5 minutes, then click 'Executions' in the left sidebar
4. 4Open the most recent execution and verify each node shows a green checkmark