What is your goal?
What do you do when you don’t how to do an automation ?
What is the problem & what have you tried?
Use ai but sometimes is wrong
Error messages or input/output bundles
No error
1 Like
Head over here. It has all the information you need.
Hello,
There are several steps that I take when I can’t seem to figure out how to perform a particular automation. First thing I do is try to search the integration page to see if there is something I missed.
Then I would:
-Google the issue to see if there is a post somewhere of someone having the same issue that I am having that can quickly explain it maybe a community post or even a Youtube tutorial video
-Next I would ask AI which can be very helpful but many times still lacking. A lot of times it can figure out the general idea of everything that needs to be done, especially if it is an organizational issue. AI can output a blueprint which can help establish a working picture for your workflow. Though be careful it tends to use a lot of HTTP requests that are more raw so in some cases it may be hard to modify and map all of the variables as there is a lot of guess work, but in many ways it can be very helpful as it knows the software and easily tell you if something could be done or not in Make and clarify your thinking process in this whole thing.
-Finally if all else fails I would ask a question right here on the Make Community page. This way you can share screenshots and get advice from people who may have actually built similar types of automations with this platform and can point you in the right direction for help.
There are many different avenues for trying to figure out challenges with your automations if you are stuck on something.
1 Like
But do you know if someone explain each make’s module easier that read each API documentation ?
1 Like
Start learning how to connect modules
First you need to understrand the functions of several module make.com Academy should help you with that then gradually start building automation bit bit from there you are good to go that was how i became an expert if you need further guidance i can help you let me know
What I usually do is keep it very simple:
-
Break the automation into small steps
-
Build and test one step at a time
-
Check the input/output bundle after each step
-
Search the Make Community or docs for that exact module/error
-
Use AI only for ideas, not as final truth
A good rule is:
Don’t build the whole automation at once.
Build a small part → test it → then add the next part.
If AI gives wrong answers, I usually:
So in short:
AI can help start, but testing real bundles in Make is what really solves it.
1 Like
My goal is to clearly understand the automation and then build it step by step in a reliable way.
When I don’t know how to do something, I first break the problem into smaller parts (trigger, data, action). Then I check the official documentation to understand the exact parameters and requirements. After that, I test each step separately instead of building the whole workflow at once.
I also use examples and community discussions to get ideas, but I always verify them by testing, because suggestions are not always correct.