I’m desperately trying to build Notion - Google Calendar sync. I have two triggers: on a new item and on update items. And it works very badly without any clear logic.
Very often it doesn’t react when the worklow is active. But when I click the button Execute Workflow button, it works… Or it can do nothing, then I make some changes in the final node (let’s say Telegram), resave the workflow — and it sends several execution as if they were in a queue
Sometimes the New trigger doesn’t fire on a new record but the Update trigger does.
I just Today had similar problem, be aware that you need to let n8n how often it should look what new pages (I think it was added with some n8n version)
In my case, added pooling every minute to resolve problem (I am using version 156)
HI @Shirobachi. Yes, I set both triggers for 1 minute polling. It works so bad that I’m frustrated. It is completely unpredictable and depends on the Execution button and on re-saving the workflow.
Thinking about comparing data versions and acting if something new in Notion data.
About comparing data, you may check last update props. But let me know what version do you use.
Try this, disable update trigger for a moment and make new page, be sure at this time to workflow be active. In my case it works with delay but always work. I know that in notion edit and created are related, so maybe it causes some problem (if you create new page at 5:15PM then edit time will be same)
If will be working for new data trigger you could try after update trigger make filter edit time not equal created time (via function note the easiest I think)
Disabled the Update node and waited. On new records the New trigger catches and sends data of some previous data. Like 3 or 4 records before. Seems like there’s some queue and the trigger pulls not the latest one.
Honestly, I don’t know how to fix this. If I were you at this point I would add checkbox props and I would get all pages where this props == false, do what you need and check this props to true.
Thanks very much both for raising this! I haven’t worked too much with the Notion Trigger yet but have blocked some time tomorrow to take a closer look into what might be happening here.
After looking into this I could identify one case where records where missed by the trigger node. The Notion trigger node compares the internal ID of the previous record which it discovered as having changed with the ID of the last updated record it receives when querying Notion (here).
So where you update a record (which is found by the trigger) and would then update that same record again it would miss the second update. This would also miss records that have been updated in the meantime if the last record you update between polling intervals is the one that has previously been found by the trigger.
I shall add this to our bug tracker for a closer look and hopefully resolution.
I hope that this would eventually solve proble with the Notion Triggers in both regimes (New and Updated).
For now, I developed such a versioning polling workflow. This is how I add a new GCal event from Notion. And checking that it wasn’t created in GCal by hands so there’s no need to go to Notion and create a copy.
I can develop this for Updating and Deleting GCal events
