Trigger from Notion Database / Page Updated not working

[agentdaddy]

Self Checks

• I have read the Contributing Guide and Language Policy.
• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.10.0

Cloud or Self Hosted

Cloud

Steps to reproduce

1. Create a workflow with start trigger node of Notion - Database Content Updated & Page Content Updated
2. Do updates on Notion and check for trigger event

✔️ Expected Behavior

The workflow should receive the updated trigger and starts running the workflow

❌ Actual Behavior

There is no event showing when I try to run the trigger

[dosubot]

Hi @agentdaddy! I'm Dosu and I’m helping the dify team.

Here’s a focused troubleshooting checklist for Notion triggers in Dify Cloud v1.10.0:

1. Webhook Subscription Setup: Make sure you manually created a webhook subscription in Notion’s integration settings, pasted the Dify trigger endpoint, selected the correct event types (page.content_updated, database.content_updated), and completed the verification handshake with the token provided by Notion. Dify does not create subscriptions automatically—you must do this in Notion’s UI. Reference

2. Integration Token: Double-check that your Notion integration token is valid and correctly pasted into Dify. If the token is missing or invalid, triggers will not work. Reference

3. Event Type & Workspace Filter: Confirm that your trigger node is set to listen for the exact event types you want, and that the workspace filter matches your Notion workspace ID. If the workspace_id in the event payload does not match, the event will be ignored. Reference

4. Signature Verification: If you enabled signature verification, ensure the X-Notion-Signature header is present and matches the verification token. Missing or invalid signatures will cause the trigger to reject the event. Reference

5. Trigger Event Quota: Dify Cloud plans have a limit on total workflow trigger events. If you’ve hit your quota, triggers won’t fire until you upgrade or reset your usage. Reference

6. Recent Bug Fixes: There was a Redis cache key bug that could prevent triggers from firing if multiple apps had nodes with the same node_id. This was fixed in a recent update—if your cloud instance is up to date, this should no longer be an issue. Reference

If you’ve checked all the above and triggers still don’t fire, look for error or warning messages in the Dify UI or logs (if available), especially about signature validation, token errors, or ignored events. If possible, share your workflow config, trigger node details, and subscription status for deeper troubleshooting.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[agentdaddy]

@dosu I'm on the notion webhook subsription page, if im going to use this integration for multiple dify worflow, what would be the Dify endpoint to enter here?

[dosubot]

You can use the same Dify webhook endpoint URL for multiple workflows. The endpoint you need is the one shown in Dify when you set up a Notion trigger connection—just copy that URL and paste it into Notion’s webhook subscription page as the public, SSL-enabled webhook URL. Each workflow in Dify can apply its own event type and workspace filters, so sharing the endpoint won’t cause conflicts; Dify will route and filter events per workflow as needed.

After pasting the endpoint in Notion, complete the verification handshake by copying the verification token from Notion into Dify’s trigger setup. You can then select which event types you want Notion to send, and Dify will handle the rest. For details, see the setup steps in the plugin’s README: Notion Trigger Plugin Setup.

No need to create a separate webhook subscription for each workflow—just reuse the same endpoint and configure your filters in Dify for each workflow as needed.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[agentdaddy]

@dosu I had sucussful connect it following steps above, but it doesn't seems like able to trigger everytime.

I had checked the page connections, it's connected to the Dify webhook integrations

[dosubot]

Intermittent Notion trigger issues in Dify are often caused by event filtering, deduplication, or quota/rate limits. Some events may be silently dropped if the event type or workspace ID doesn't match your trigger config, if the trigger is disabled, or if your plan's trigger event quota is exceeded. Also, the plugin can cancel triggers (for example, to avoid duplicates), and these won't show as errors—they'll just be ignored.

To troubleshoot: check if there's a pattern to the missed triggers (like specific update types or timing), review your workflow trigger logs for skipped or ignored events, and verify your trigger event quota in Dify Cloud. Make sure your trigger node config (event types, filters, workspace IDs) matches what Notion is sending, and check Notion's webhook delivery logs if possible. If you still see gaps, enabling debug logs or sharing detailed logs can help pinpoint the cause.

More details on how Dify processes and sometimes drops triggers can be found in the trigger dispatch logic.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}