Help with Make + Storeganise + ManyChat DM Automation (Real-time Storage Availability Use Case)

How To
, ,
1

Hey automation pros :waving_hand:

I’ve been trying to build a real-time storage unit availability flow inside Instagram DMs using ManyChat, Make.com, and the Storeganise API, but I’ve hit a wall and would love to get your advice or hear how you would tackle this.

:magnifying_glass_tilted_left: The Goal

We want to allow users on Instagram to:

  1. Select their location inside a DM
  2. Automatically fetch the available storage units for that site from Storeganise (using the /unitTypes endpoint filtered by siteId)
  3. Return a formatted list of available units with size and price (e.g. “:white_check_mark: 2.5m² – $99/mo”) back into ManyChat as a response

The idea is to automate the rental discovery process and remove the need for clicking through to the website.

Tech Stack

  • ManyChat (user selects location via buttons → sends webhook to Make)
  • Make.com handles the webhook, fetches unitTypes from Storeganise, parses JSON
  • Storeganise API provides all unit details and availability info
  • Aggregated list is returned to ManyChat via webhook response

The Problem

In Make:

  • We successfully receive the correct data from Storeganise API
  • We parse the JSON
  • We use an iterator to loop through unitTypes
  • We filter only units with availability.available > 0
  • We use Text Aggregator to compile a list of available units
  • We respond back to ManyChat via webhook

BUT — in live tests:

  • Only one unit is returned (even though multiple are available)
  • Sometimes it’s the wrong unit
  • The flow behaves differently in live Instagram tests vs Make test runs
  • Final webhook often shows empty output in live tests

My assumptions:

  • There may be a race condition: aggregator runs before iterator finishes
  • The loop is not bundling all matching units properly
  • JSON structure might be off or too shallow (we only selected unitTypes to iterator)
  • Storeganise + Make are not natively compatible, so maybe a better middle layer is needed?

What I’m asking:

  1. Has anyone successfully used Make with Storeganise?
  2. How would you structure this flow (or would you even use Make)?
  3. Is there a better way to reliably return multiple filtered results into ManyChat from an external API?
  4. Could this be better done with something like Firebase, n8n, a middleware script?

Any help, flow screenshots, or structural advice would be insanely appreciated :folded_hands:

Happy to share more details!

2

Hey Tobias,

just to clarify 2 things - nothing runs before the previous module finishes and there are no loops in Make.

Can you please share some screenshots and sample outputs? Mainly showing the correct working tests and the differences in the Live data that failed?