Skip to main content

Hey automation pros 👋

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.

🔍 The Goal

We want to allow users on Instagram to:

  1. Select their location inside a DM (e.g. Olari, Lauttasaari, etc.)

  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. “✅ 2.5m² – 99€/kk”) 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 and returned real time data back to ManyChat?

  2. How would you structure this flow (or would you even use Make, meaning could this be done with just ManyChat and Storeganise)?

  3. Is there a better way to reliably return multiple filtered results into ManyChat from an external API?

Any help or advice would be insanely appreciated 🙏

Hey ​@Tarve_Automations I haven’t integrated Storeganise, but I’ve integrated a bunch of software with Manychat + Make or direct integrations.

If Storeganise has a JSON API it’s very likely that it could be integrated directly with Manychat. We’d make the request using external requests in Manychat, store the response in User Fields, and then run logic in Manychat to compile the ‘clean’ response to the user. I’ve done this with other platforms and, although it takes a bunch of logic in Manychat, it works like magic!

You may also have a timing issue if you’re using a Webhook response to get the info in Manychat - since Manychat will wait for only 10 seconds for a valid response.

And as you mention, it seems you have an issue aggregating the information in Make into a single text response - that needs to be configured properly.

If you’d like a second pair of eyes feel free to send me a message, we can setup a consulting call where we can probably solve the issue or at least get you much closer to the solution!

Hey ​@Gustavo Boregio ,
Really appreciate your reply, super helpful to get validation from someone who's done similar setups with ManyChat + Make.

Good call on the timing. That was actually the main issue we ran into. Syncing the response cleanly back into ManyChat within that 10s window tripped us up.

Massive thanks for the insight, it helped a lot. If we run into similar issues down the line, I’ll definitely shoot you a message. Would be great to potentially collaborate if the timing lines up!

Thanks again!

Reply


Community Terms & ConditionsCookie settings