I’m working with Make (formerly Integromat) and trying to connect multiple relation records to a Notion database entry. The problem I’m running into is that when I process multiple items, each new item overwrites the previous one instead of adding to the existing relations.
What I want to happen: All related records should be linked to the main database entry
What actually happens: Only the final item from the iteration gets saved, replacing any previous relations
Has anyone figured out the correct way to handle this scenario? I’ve tried different approaches but can’t seem to get all the relation connections to persist properly. Any tips on the right configuration would be really helpful.
Yeah, this is a super common Make workflow issue. I fixed it by using the Array Aggregator module to collect all the relation IDs first, then sending that whole array to Notion in one go. Without the aggregator, Make processes each item separately and the API overwrites the previous relations every time. Make sure you’re mapping the relation property right in the Notion module - it needs the full array of IDs, not individual values. Also check that your Notion database relation property allows multiple entries, or it’ll just keep the last one.
ugh, this drove me nuts too! you need the aggregator module b4 sending to Notion - it bundles all your relation IDs into 1 array instead of overwriting them. took forever to figure out, but works perfectly once its set up right.
Hit this exact problem six months ago and wasted hours debugging it. Make processes each iteration separately, so Notion gets individual API calls that replace the relation field instead of adding to it. I fixed it by collecting all relation IDs first, then updating Notion once at the end. Used Set Variable and Get Variable modules to build an array of relation IDs during the loop. After the loop finished, I sent one update request to Notion with the complete array. No more overwriting issues - all relations stuck around properly.