Vigyata.AI
Is this your channel?

Make.com Sub-Scenarios: See ALL Inputs! (Debug Hack)

106 views· 1 likes· 3:50· Nov 6, 2025

🛍️ Products Mentioned (15)

Struggling to see what data is passed to your Make.com Sub-Scenarios? This simple debug hack will show you all the input parameters directly in your scenario history, making debugging and testing significantly faster and more reliable! The Problem: Make.com's standard 'Call a Scenario' module hides the values passed to your Sub-Scenario's history, forcing you to guess or dig deep for critical data. The Solution: Replace the standard 'Scenario Inputs' module at the beginning of your Sub-Scenario with a 'Start a Scenario' module. This trick makes all the transmitted variables immediately visible in the module's log (e.g., Name = Erwin), so you instantly see if the correct values arrived. The Benefits: Less guesswork with faulty data, much faster testing cycles, and more robust automations. Stop wasting time wondering what's being passed! Got questions about the setup or implementation? Leave a comment below – I'll reply and help you with your debugging challenges! This is the AI-translated version of our YouTube-Video originally posted on our German YT-Channel @pickertgmbh @itsmake 00:00:01 The Problem with Debugging Sub-Scenarios 00:00:27 Building the Example Sub-Scenario 00:00:49 Calling from Parent Scenario & Visible Inputs 00:01:16 Missing Input Data in History 00:01:55 Solution: Use the 'Start a Scenario' Module 00:02:31 Making Inputs Visible in the Start Module 00:02:59 History Now Shows Passed Values & Saves Credits! 00:03:43 Lets debug better! 👉 SOFTWARE, TOOLS & DEALS + MAKE.com*: https://www.make.com/en/register?pc=pickertgmbh + Airtable*: https://airtable.com/invite/r/GbOmyMYx + OpenAI API: https://platform.openai.com/ + Elevenlabs*:https://try.elevenlabs.io/7uf5u0hvrmzs + HeyGen*: https://heygen.com/?sid=rewardful&via=sven-o + 0CodeKit*: https://my.0codekit.com/en/auth/register?via=sven-o + Fillout*: https://www.fillout.com?ref=pickert + tl;dv*: https://tldv.cello.so/cbsANc1a33V *Affiliate links 👉 30-MINUTE STRATEGY CALL You want to get started but don’t know how? Sven O. Rimmelspacher has been working in quality and process optimization for over 30 years. Let’s talk – book your free call with Sven here: https://link.pickert.gmbh/termin-sor 👉 FOLLOW US Follow us, give us a like, and subscribe to our channels! 💻 Our website: https://www.pickert.de 🖊️ Our blog: https://www.pickert.de/blog ➡️ Our LinkedIn page: https://www.linkedin.com/company/pickertgmbh 👉 WHY WORK WITH US? At Pickert, we’ve been focused on quality and process optimization for over 40 years. We offer solutions for process automation and AI – and our team can implement exactly what you need, whether it’s a challenge or a full-service package. As part of the family-owned corporate group about ZERO GmbH, we’re part of a network of companies dedicated to more quality in every area of life. about ZERO GmbH: https://www.about-zero.de Quality Miners GmbH: https://www.quality-miners.de Rocket Routine GmbH: https://www.rocket-routine.com Factory Excellence Network GmbH: https://www.factory-excellence.com Pickert GmbH | Creating space to focus. Enabling clarity. Driving innovation.

About This Video

Wenn du in Make.com mit Sub-Scenarios arbeitest, kennst du wahrscheinlich genau diesen Debug-Frust: Im Parent-Scenario übergibst du sauber deine Variablen – aber in der History vom Sub-Scenario siehst du die Input-Werte nicht. Das Standard-Setup mit „Call a Scenario“ + „Scenario Inputs“ versteckt dir die wichtigsten Infos, und du fängst an zu raten, ob „Name = Erwin“ wirklich angekommen ist oder ob irgendwo ein Mapping kaputt ist. In diesem Video zeige ich meinen einfachen Debug-Hack: Ich ersetze im Sub-Scenario das Modul „Scenario Inputs“ am Anfang durch „Start a Scenario“. Dadurch werden alle übergebenen Parameter direkt im Log dieses Start-Moduls sichtbar – und zwar sofort in der Scenario-History. Das macht Tests deutlich schneller, reduziert Fehlersuche mit Blindflug und sorgt für robustere Automationen, weil du sofort erkennst, ob falsche oder leere Daten reinkommen. Bonus: Du sparst dir unnötige Runs und damit auch Credits, weil du schneller an die Ursache kommst und nicht zigmal „trial and error“ fahren musst.

Frequently Asked Questions

🎬 More from Intelligent Process Automation