Hi everyone,
I’m running into a multi-bundle variable overwrite issue and looking for a clean workaround.
My Setup: I have a scenario triggered by HubSpot deal stage changes (runs every 1 hour). The scenario creates a ClickUp list for each deal and then adds the deal’s existing sales task to that newly created list.
What works (single deal): When only one deal triggers per cycle, everything works perfectly — the list is created, the list ID is stored via Set Multiple Variables, retrieved via Get Multiple Variables, and the sales task gets added to the correct list.
What breaks (multiple deals in same cycle): When two deals trigger in the same cycle (e.g., deal 18063 and deal 18147), the scenario creates two separate ClickUp lists with correct, different list IDs. However, Set Multiple Variables stores the “To-Do List ID” and since variables are global to the execution, the second bundle overwrites the first bundle’s value. By the time the downstream module (Add Sales Task to List) runs, both bundles read the same list ID — so both sales tasks get added to the same list.
I also tried mapping the createList module’s output (16.body.id) directly to a downstream “Edit Task” module (module 451), but because there’s an aggregator/router between them that breaks the bundle chain, both operations still received the same body ID.
My question: Has anyone found a clean pattern for preserving per-bundle data across an aggregator in Make? Is the Data Store approach the best practice here, or is there a simpler way to scope variables per bundle?
Any help is appreciated. Thanks!