Notion Automation Sends Duplicate Slack Notifications: Fix

You set up a Notion automation to send a Slack notification when a database item is updated, but you are receiving two or more identical messages for a single change. This duplication wastes time and clutters your team channel. The root cause is usually a misconfiguration in the automation trigger or a conflict between multiple automations running on the same database. This article explains why duplicate notifications occur and provides three specific methods to stop them.

Why Notion Automation Sends Duplicate Slack Notifications

Notion automations run on a per-database basis. When you create an automation that sends a Slack message when a property is updated, the automation watches for any change to that property. If you have two separate automations that both watch the same property in the same database, both fire when the property changes. This is the most common cause of duplicate notifications.

Another cause is an automation that triggers on “any edit” instead of a specific property change. When a user edits multiple properties in one save, the automation may fire multiple times — once for each property change detected by Notion. Additionally, if the database is part of a linked database view that exists in multiple pages, each linked view can generate its own trigger event, causing duplicates.

A less common but real cause is a Slack webhook integration that is configured twice. If you have two separate Slack connections in your Notion workspace, the same automation may send the message through both connections. This happens when the automation action is set to “Send Slack message” and the workspace has two active Slack integrations pointing to the same channel.

Steps to Stop Duplicate Slack Notifications

Follow these steps in order. Test after each step to see if the duplication stops. If it continues, move to the next step.

Method 1: Check for Duplicate Automations

1. Open the automation list for the database
   Go to the database where the automation is running. Click the three-dot menu in the top-right corner of the database view. Select Automations from the menu.
2. Review all automations in the list
   Look for two or more automations that have the same trigger condition. For example, two automations that both say “When a property is updated” and specify the same property name. If you find duplicates, click the three-dot menu next to each duplicate automation and select Delete. Keep only one.
3. Test the remaining automation
   Make a test edit to the property that triggers the automation. Check the Slack channel for the notification. You should see only one message.

Method 2: Change the Trigger from “Any Edit” to a Specific Property

1. Open the automation editor
   Go to the database and click the three-dot menu. Select Automations. Click the automation name to open its editor.
2. Modify the trigger condition
   In the trigger section, if it says “When a database item is edited,” click the dropdown and change it to When a property is updated. Then select the specific property that should trigger the Slack notification. For example, select “Status” instead of leaving it as “any property.”
3. Save the automation
   Click Save in the top-right corner. Test by editing only the selected property. The automation should fire once.

Method 3: Remove Duplicate Slack Integrations

1. Check active Slack integrations
   Go to Settings & Members in the left sidebar. Select Connections. Look for Slack in the list of connected apps. If you see more than one Slack connection, note which one is active.
2. Disconnect the extra Slack integration
   Click the three-dot menu next to the duplicate Slack connection and select Disconnect. Keep only one Slack integration connected to your workspace.
3. Update the automation action
   Go back to the automation editor. In the action step that sends the Slack message, confirm it uses the remaining Slack connection. If the automation was using the disconnected integration, select the active one from the dropdown. Save the automation.

If Notion Still Sends Duplicate Notifications After Fixing Automations

Linked Database Views Trigger Separate Automations

If your database appears as a linked database view in another page, each linked view can act as a separate trigger source. To fix this, ensure that automations are created only on the source database, not on linked views. Open the original database and check its automation list. Delete any automations that exist on linked views. Then edit the source database and make the change there. The linked view will reflect the change but will not fire its own automation.

Slack Channel Has Multiple Incoming Webhooks

In Slack, a channel can have multiple incoming webhook URLs. If you configured a custom webhook in Notion and also used the native Slack integration, both may send messages. Go to Slack and navigate to the channel settings. Under Integrations, review the list of webhooks. Remove any duplicate webhooks. Then in Notion, use only the native Slack integration for automation actions.

Automation Runs on Every Database Item Instead of Filtered View

If your automation triggers on a property change but the database contains many items, the automation may fire for every item that matches the trigger. To narrow this, add a filter to the automation trigger. In the automation editor, click Add filter. Set a condition such as “Status is In Progress” so that only items with that status trigger the Slack notification. This reduces the chance of multiple items causing duplicate messages in quick succession.

Notion Automation Trigger Options Compared

Trigger Type	When It Fires	Duplicate Risk
When a database item is edited	Any change to any property	High — fires on every property edit, even in the same save
When a property is updated	Only when the selected property changes	Low — fires once per property change per save
When a page is added to a database	Only when a new item is created	None — fires only once per new item

Using the “When a property is updated” trigger with a specific property and a filter is the most reliable way to avoid duplicates. The “When a database item is edited” trigger should be avoided for Slack notifications because it fires too broadly.

You can now identify and remove duplicate automations, refine trigger conditions, and clean up extra Slack integrations. Next, test your automation by editing a single property in one item and confirm that only one Slack message appears. As an advanced tip, add a delay action before the Slack message to batch rapid edits — this prevents multiple messages when a user edits several properties quickly.