Use specific bundle to test rest of the flow during building

:bullseye: What is your goal?

When I was using Zapier I could run a zap while building it and I would get for example three entries. entry 1, entry 2, entry 3 each with their own data.

Then when building the second step in the flow I could choose which “test” data I wanted to use, so for example I could use the data from entry 3 and do all the testing with this data. Once launched all data would flow through.

:thinking: What is the problem?

In Make it also get multiple entries in what seems to be bundles. But I can’t seem to choose a specific bundle (e.g. entry) to built and test the rest of my scenario. It always starts with 1.

:test_tube: What have you tried so far?

I know I could do something with a filter and limit on the beginning, but that seems very cumbersome as I would need to change that back after testing.

Hello,

Yes, you’re right – in Make you can’t select a specific bundle for testing. But there are a few ways around it:

  1. Use a filter. That’s the simplest approach. Right after the Iterator, add a filter so only bundle N passes through.

  2. If the scenario is webhook-triggered, prepare test data and send it – for example using Postman or a second scenario with HTTP call module.

  3. You can also re-run a previous scenario run.

  1. And the most flexible option:
  • Run your scenario to get output data
  • Select the data you want to work with- if you don’t fel comfortable with JSON you can use LLMs → should be helpful
  • Use Parse JSON as your starting module during the building phase
  • Work in your scenario
  • Once done, swap Parse JSON for the actual module that generates the data
  • Use Make DevTool to remap all modules

I highly recommend learning option 4 on a test scenario. It’s the most flexible approach, but it requires understanding the logic and how DevTools work.

Have a nice day,
Michal

Thanks, definitely gonna try all these out. Though it still is huge hassle compared to n8n or zapier, really hope in the future Make also add’s an option to test the steps and caches/temporary saves the data so you can test it step by step easily. Seems it would add a lot of value for people used to the other tooling, while still also having the possibility to use all the other ways you described.