Hi, I’m a beginner and pretty impressed on make.com’s versatility and usefulness. It was the best automation tool among any other tools I’ve experienced.
However, I couldn’t figure out how I can make an application with it. I could understand basic things like actions and connecting these actions. But I could not understand how I develop and debug my app step by step from the first step.
I’m making a test automation with ‘mailhook.’ I cound start with a wehbhook action and connect it to another action. But when the things didn’t go right, I could not debug them at all. For example, after I send a test email and run once, if any error occurs, then I would like to modify only small part from few actions, and then test from only these step I modified. But if I click ‘run this module only’, it was required to type in any of its inputs, or if I run once again, I need to start from the first thing like sending a test email and see the entire actions were running again. I want to know how I can modify and run only a step in the middle of the entire flow while keeping any inputs and outputs from the previous steps.
You can also use the Make DevTool to debug external requests.
If you have the Make DevTool Chrome extension installed, you should be able to view the request and response headers and body from each module when you manually run the scenario.
Make DevTool allows you to debug your Make scenarios in a completely new way. It adds an extra pane to the Chrome Developer Tools. Using this new debugger pane, you’re able to check all the manual runs of your scenario, review all the performed operations and see the details of every API call performed. It also brings a whole bunch of new opportunities for Apps development. You’re able to check every call that your app has performed. Thanks to this extension, you can easily debug your scenario, see which module, operation, even which single response causes the error, and then get your scenario back on track. Try it out and let your scenarios shine!
Thank you for the quick reply. But I can’t still understand why this is designed to be so unintuitive. Using this way, I would repeatedly try to run the whole scenario from the very beginning each time and consume lots of operations.
For beginners, the easiest way would be to modify and test new steps to get the expected result while leaving the previous steps untouched.
Isn’t there a way to keep the previous step as it is and automatically input the results into the new step, to modify and test new steps? Without manually copying and pasting the results of the previous step or unlinking and linking previous steps.
