Issue Station
Sign In
Tools hereToolbox

n8n - ✅(Solved) Fix The Notion trigger in n8n is not working, even though I’ve created everything again. [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28463•Fetched 2026-04-15 06:44:23
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
axieworks21-wqaxieworks21-wq
Participants
axieworks21-wqaxieworks21-wqn8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
closed ×1commented ×1cross-referenced ×1labeled ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • error: all

Root Cause

Describe the problem/error/question

I’ve had this flow working for almost a year now, but it suddenly stopped working properly because the Notion trigger is not providing the correct data. it always get the same ID again and again.

Fix Action

Fixed

PR fix notes

PR #28480: fix(notion): improve trigger polling logic and resolve database loadi…

Description (problem / solution / changelog)

…ng error #28463

Summary

This PR fixes two major issues with the Notion Trigger:

  1. Duplicate Executions: Resolved an issue where the trigger fetched the same items repeatedly due to Notion's minute-level timestamp accuracy and a "Greater Than or Equal To" filter logic.
  2. UI Loading Errors: Fixed a "can't get data for expression" error in the getDatabases load option by making the resource parameter optional in notionApiRequestAllItems.

Changes

  • State Management: Switched lastTimeChecked from a Moment object to an ISO String for reliable persistence in staticData.
  • Atomic Updates: The polling timestamp now updates at the end of a successful poll rather than the beginning.
  • Duplicate Filtering: Improved the possibleDuplicates logic to track IDs within the same minute window, preventing re-processing of items Notion returns during high-frequency polling.
  • Generic Function Fix: Updated notionApiRequestAllItems in GenericFunctions.ts to prevent crashes when called from triggers/load-options where a specific resource context is missing.

Testing

  • Verified with a local n8n instance and a Notion test database.
  • Confirmed that multiple edits within the same minute no longer trigger duplicate workflows.
  • Confirmed that the "Database" dropdown in the node UI now loads correctly without errors.

Related Issues

Fixes #28463 Internal Ref: GHC-7732

Changed files

  • packages/nodes-base/nodes/Notion/NotionTrigger.node.ts (modified, +16/-7)
  • packages/nodes-base/nodes/Notion/shared/GenericFunctions.ts (modified, +1/-1)

Code Example

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

I’ve had this flow working for almost a year now, but it suddenly stopped working properly because the Notion trigger is not providing the correct data. it always get the same ID again and again.

What is the error message (if any)?

there was a problem loading the parameter options from server "cant get data for expression". and when notion trigger is excute it always get the same ID again.

Please share your workflow/screenshots/recording

<img width="1897" height="857" alt="Image" src="https://github.com/user-attachments/assets/cd44ec21-95e8-4701-ab93-132f1905245c" /> <img width="1891" height="873" alt="Image" src="https://github.com/user-attachments/assets/86ae1aa6-7a4c-44b8-a176-dc18d9d6b980" /> 
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

  • n8nVersion: 2.9.4
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.13.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: community

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-14T10:44:25.276Z}

extent analysis

TL;DR

The Notion trigger issue may be resolved by re-configuring the trigger or checking the Notion API connection.

Guidance

  • Verify the Notion API connection and credentials to ensure they are valid and have not changed.
  • Check the Notion trigger configuration to ensure it is set up to retrieve the correct data and IDs.
  • Review the workflow and node settings to ensure that the issue is not caused by a misconfiguration or incorrect data processing.
  • Consider checking the Notion API documentation to see if there have been any changes to the API that may be causing the issue.

Example

No code example is provided as the issue does not contain sufficient information to create a specific code snippet.

Notes

The issue may be caused by a change in the Notion API or a misconfiguration in the workflow. Further investigation is needed to determine the root cause of the issue.

Recommendation

Apply workaround: Re-configure the Notion trigger and verify the API connection to resolve the issue. This is recommended as the issue seems to be related to the Notion trigger and API connection, and re-configuring these may resolve the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#autograd error#model save/load#optimization#mixed precision

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - ✅(Solved) Fix The Notion trigger in n8n is not working, even though I’ve created everything again. [1 pull requests, 1 comments, 2 participants]