Hi Gumloop team,
I’m encountering a persistent issue using the Notion Database Updater module. My workflow involves retrieving the number of drivers through web scraping and AI analysis, then updating this data into a Notion database.
Problem:
Every time the workflow reaches the Notion Database Updater, it consistently fails with the error: "Notion Database Updater Failed: No page found with ID = ID." I’ve experimented extensively with various configurations, including switching from appending items (which always adds them to the top when using the Database Writer) to using the updater module, but the same error persists.
What I’ve tried:
- Verified Notion database connection and permissions
- Checked the output and format of previous workflow steps (Web search, Website Scraper, Ask AI, Combine Lists)
- Tested multiple IDs and mappings
- Inserted various additional nodes (like Flatten List, ID mappings) between workflow steps
- Added explicit IDs into the Notion database to attempt targeted updates
- Experimented with a variety of different modules and node configurations to identify the key issue
I’m attaching a screenshot showing my current configuration and the error for clarity.
Could someone please advise on what might be causing this specific error and how I can correct the Notion database updater step?
Thank you!
Hey @FwuuEq_224_tA2! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.
-
Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={your_run_id}&workbook_id={workbook_id}
-
Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
-
Provide details about the issue—more context helps us troubleshoot faster.
You can find your run history here: https://www.gumloop.com/history
Hey @FwuuEq_224_tA2 - Could you share the failed run link using the instructions from the message above please 
Do you think you can help?
Hey @FwuuEq_224_tA2! Apologies for the late response, I can definitely help
The Notion Database Updater (or any updater node) needs two key inputs: Search Column and Search Value.
Think of these fields as a way to filter your database and find the right row:
- Search Column: The fixed column used to identify rows (e.g.,
"Order Number").
- Search Value: The specific value to look for in that column (e.g.,
"ORDER-456").
Here’s an example:
| Search Column |
Search Value |
Matching Row in Notion |
Order Number |
ORDER-123 |
Finds the row where Order Number = ORDER-123 |
Order Number |
ORDER-456 |
Finds the row where Order Number = ORDER-456 |
You can check out more details here:
Right now, your flow is hardcoding "ID" as the Search Value, but it should be dynamically connected to the Notion Database Reader’s ID output.
I’d also highly recommend this tutorial on subflows:
Subflows in Gumloop
Since your flow is running in loop mode, if anything fails, the whole process stops. A better approach is to:
- Create a subflow that handles a single search input.
- Loop it over the Notion Database Reader.
- Wrap the subflow in an error shield, so if something fails, it just skips that step instead of stopping everything.
Basically, everything downstream of the Notion Database Reader would be in a subflow.
Let me know if this makes sense and works for you.
I do not think I am going to get from point A to point B on this one. I am an executive, not a developer. Thank you though!
Alright, no worries. If you or anyone on your team wants to take this further, I’m happy to hop on a quick 15-minute call to walk you through it.
You’re also welcome to join our educational cohort if you’d like to learn step by step how to build flows like this: Join Here.
I’ll take you up on the call. I would like to make the tool work I just do not have huge amounts of time to learn it. Send me a link to your calendar and I will book at slot. Thanks again!
