How to Send Notion Database Updates to Slack with Zapier

zapier.com > Dashboard > Create Zap

Create a new Zap

Log into zapier.com and click the orange 'Create Zap' button in the left sidebar. You land on the Zap editor, which shows a two-block canvas: Trigger on the left, Action on the right. Give your Zap a name at the top — something like 'Notion DB → Slack #dev-updates' — so it's identifiable later in your dashboard. You'll configure the trigger first.

1. 1Log into zapier.com
2. 2Click 'Create Zap' in the left sidebar
3. 3Click the name field at the top and type a descriptive name
4. 4Click the Trigger block to begin configuration

Zap Editor > Trigger > App & Event > Search 'Notion'

Set Notion as the trigger app

In the trigger search bar, type 'Notion' and select it from the results. Zapier will show you a list of available Notion triggers. For new database rows, choose 'New Database Item'. For updates to existing rows (like a status change), choose 'Updated Database Item' — pick only one and stay consistent. Both triggers work via polling, so Zapier checks Notion every 1-15 minutes depending on your plan.

1. 1Type 'Notion' in the trigger app search bar
2. 2Click 'Notion' in the results
3. 3Click 'New Database Item' for new rows OR 'Updated Database Item' for status changes
4. 4Click 'Continue'

Zap Editor > Trigger > Account > Sign in to Notion

Connect your Notion account

Click 'Sign in to Notion'. A popup opens asking you to authorize Zapier. Notion requires you to explicitly select which pages or databases Zapier can access — it does not grant blanket access to your entire workspace. On the Notion authorization screen, click 'Select pages' and check the specific database you want to monitor. If you skip this, Zapier won't see the database in the next step.

1. 1Click 'Sign in to Notion'
2. 2In the Notion authorization popup, click 'Select pages'
3. 3Check the box next to your target database
4. 4Click 'Allow access'
5. 5Close the popup and confirm the account appears in Zapier

Zap Editor > Trigger > Configure > Database ID

Select your Notion database

Under 'Configure', click the 'Database ID' dropdown. Zapier lists all databases your Notion account has shared with it. Find and select the database you want to monitor — for example, 'Feature Requests' or 'Sprint Board'. If you're using the 'Updated Database Item' trigger, you'll also see a 'Filter by Property' option where you can narrow alerts to only rows where a specific property changed, like Status.

1. 1Click the 'Database ID' dropdown
2. 2Select your target database from the list
3. 3Optional: Click 'Filter by Property' and select a property like 'Status' to restrict which updates fire the trigger
4. 4Click 'Continue'

Zap Editor > Trigger > Test > Test trigger

Test the Notion trigger

Click 'Test trigger'. Zapier fetches the three most recent rows from your Notion database and displays the raw field data. Look through the returned sample — you'll see every property your database has, including internal Notion IDs for relation and person fields. Make a note of which fields you want to include in your Slack message: title, status, assignee, priority, due date, and URL are the most common picks.

1. 1Click 'Test trigger'
2. 2Review the returned sample data
3. 3Identify the fields you'll use in the Slack message
4. 4Click 'Continue with selected record'

Zap Editor > Action > App & Event > Search 'Slack'

Add Slack as the action app

Click the Action block on the canvas. Search for 'Slack' and select it. For the event, choose 'Send Channel Message' — this posts to a public or private channel. If you want to DM a specific person instead, choose 'Send Direct Message', but channel messages work better for team visibility. Click 'Continue' to move to account connection.

1. 1Click the Action block
2. 2Type 'Slack' in the search bar and select it
3. 3Choose 'Send Channel Message' as the action event
4. 4Click 'Continue'

Zap Editor > Action > Account > Sign in to Slack

Connect your Slack workspace

Click 'Sign in to Slack'. A popup opens asking which Slack workspace to authorize. Select the correct workspace from the dropdown — if you're in multiple workspaces, this is easy to get wrong. Zapier requests permission to post messages and read channel lists. After authorization, your workspace name appears in the Account field.

1. 1Click 'Sign in to Slack'
2. 2Select the correct workspace in the Slack authorization popup
3. 3Click 'Allow'
4. 4Confirm the workspace name appears in Zapier's Account field

Zap Editor > Action > Configure > Channel + Message Text

Configure the Slack message

Select the Slack channel from the Channel dropdown — type a # to filter by name. Then build your message in the 'Message Text' field using dynamic data from the Notion trigger. Click inside the field and use the '+' button to insert Notion fields. A clear message format: start with a bold title using Slack markdown (*Title*), then list status, assignee, and a direct URL to the Notion page. Keep it under 4 lines so it's scannable in Slack.

1. 1Click the Channel dropdown and select your target Slack channel (e.g. #dev-updates)
2. 2Click inside the Message Text field
3. 3Click '+' to insert dynamic fields from Notion — start with the page title
4. 4Build a multi-line message using Slack markdown: *Title*, Status, Assignee, URL
5. 5Set 'Send as Bot' to Yes and give it a name like 'Notion Bot'

📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}

Zap Editor > Between Trigger and Action > + > Filter

Add a filter for status changes (optional but recommended)

If you're using the 'Updated Database Item' trigger and only want notifications when the Status property changes to a specific value (like 'In Review'), add a Filter step between trigger and action. Click the '+' icon between the two blocks and select 'Filter'. Set the condition: 'Status' (from Notion) 'Exactly matches' 'In Review'. This prevents Slack from getting flooded every time any field on any row changes.

1. 1Click the '+' icon between the Notion trigger block and the Slack action block
2. 2Select 'Filter'
3. 3Set Field to your Status property from Notion
4. 4Set Condition to 'Exactly matches'
5. 5Type the status value you want to trigger on (e.g. 'In Review')
6. 6Click 'Continue'

Zap Editor > Action > Test > Test action

Test the full Zap

Click 'Test action'. Zapier uses the sample Notion row from Step 5 and sends a real message to your Slack channel. Open Slack and verify the message looks correct — check that the title, status, and URL all resolved properly and aren't showing raw Notion IDs. If the format looks off, go back to Step 8 and adjust the message template before publishing.

1. 1Click 'Test action'
2. 2Open your Slack channel to see the test message
3. 3Verify all dynamic fields resolved to readable values
4. 4If anything looks wrong, click 'Back' and edit the message template

Zap Editor > Publish Zap

Publish the Zap

Click 'Publish Zap' in the top right. The Zap goes live and Zapier begins polling your Notion database. On the free plan, polling runs every 15 minutes. On the Starter plan ($19.99/month), it drops to every 2 minutes. On Professional ($49/month), it's every minute. After publishing, go to your Zap's history page and wait for the first poll to confirm it's running cleanly.

1. 1Click 'Publish Zap' in the top right corner
2. 2Confirm the Zap status shows 'On' in your dashboard
3. 3Click 'Zap History' to monitor the first few runs

Paste this into a 'Code by Zapier' step (Python) placed between the Notion trigger and the Slack action. It formats the due date into a readable string, builds a clean Slack message with conditional priority emoji, and handles blank fields so your message never shows 'undefined'. In Zapier, add a Code step, choose 'Run Python', and map the Notion fields as input variables named title, status, assignee, priority, due_date, and url.

# Input variables (set these in the 'Input Data' section of Code by Zapier):
# title, status, assignee, priority, due_date, url
import datetime

# Input variables (set these in the 'Input Data' section of Code by Zapier):
# title, status, assignee, priority, due_date, url

import datetime

def format_date(raw_date):
    if not raw_date:
        return 'No due date'
    try:
        dt = datetime.datetime.strptime(raw_date[:10], '%Y-%m-%d')
        return dt.strftime('%b %d, %Y')
    except ValueError:
        return raw_date

def priority_emoji(p):
    mapping = {
        'Critical': '🔴',
        'High': '🟠',
        'Medium': '🟡',
        'Low': '🟢'
    }
    return mapping.get(p, '⚪')

title = input_data.get('title') or 'Untitled'
status = input_data.get('status') or 'Unknown status'
assignee = input_data.get('assignee') or 'Unassigned'
priority = input_data.get('priority') or ''
due_date = format_date(input_data.get('due_date', ''))
url = input_data.get('url') or ''

emoji = priority_emoji(priority)
priority_line = f'{emoji} {priority}' if priority else '⚪ No priority'

message = (
    f'*{title}* → {status}\n'
    f'Assigned to: {assignee} | {priority_line} | Due: {due_date}\n'
    f'{url}'
)

output = [{'message': message}]