Top 10 Expert Tips for Efficient Automations in Make [Part 1]

Watch Part 2 here: • Make.com - Top 10 Expe...
Discover 10 expert tips to maximize efficiency and optimize your automations in Make. In this video, I share the best practices I've learned through trial and error, and years of experience working with Integromat and Make. These tips cover various aspects of building automations, from reducing the number of operations per scenario to the proper ways to test scenarios.
Whether you're a beginner or a seasoned Make user, these tips are sure to help you streamline your workflow and make your automations more efficient. Don't miss these valuable insights that will transform the way you build and manage your automations in Make.
➡️ Not Using Make yet? Sign up here: clicklaunch.ai/make
👉🏼 Start your account now, sign up here: clicklaunch.ai/make
👍 Got value from the video? Consider tipping at clicklaunch.ai/tips to help me create more!
00:00 Intro
00:21 Tip 1 - Changing The Starting Trigger
02:54 Tip 2 - Copy, Paste and Clone
04:58 Tip 3 - Add Module Between Modules
06:23 Tip 4 - Quickly Modifying A Field
08:15 Tip 5 - Breaking Scenarios For Testing
*Disclaimer: I am an independent Make Affiliate, not an employee. I receive referral payments from Make if you sign up using my affiliate link above. The opinions expressed here are my own and are not official statements of Make.*
The information contained on this KZbin Channel and the resources that are available for download/viewing through this KZbin Channel are for educational and informational purposes only.​

[@johnvincentramada9717]

Men I learned a lot

[@AaronDelz]

Wonderful! Awesome to hear🙌🏼

[@cre8iongroup796]

Thanks for sharing about how to break and store data to test.

[@cre8iongroup796]

Just realized that this only works for instant triggers, if it's time based that when I think you suggest using your tip number 6.

[@AaronDelz]

Glad it was helpful!

[@AaronDelz]

It doesn’t matter what type of trigger it is, because remember for testing, the scenario is off and when you want to run a test you click the Run Once button.

[@cre8iongroup796]

​@@AaronDelz Maybe the issue is that we are testing with data that is already in a google sheet. We're using a watch row module but the test data that we want to process is already in the sheet. We don't get the option to use existing processes.

[@gavinwiener]

The renaming one/adding field I had never heard of, that's super cool

[@AaronDelz]

Awesome! Glad to hear!

[@bendingreality-]

Great stuff! Yes please, a video where you show the whole scenario would be very helpful

[@AaronDelz]

Im getting several people asking about that. I’ll get to recording a video going over the whole thing.

[@AaronDelz]

Tip number 5 is my favorite and one I use all the time.

[@DaVidiot6000]

I’d love a walkthrough of that scenario!

[@AaronDelz]

I’m getting a lot of people asking about it, I’ll move it up on my priority list 😁

[@patman2193]

great stuff

[@AaronDelz]

I appreciate that. You’re welcome!

[@nicoyou11]

Great job, really useful!

[@AaronDelz]

Awesome, glad you found it useful

[@jamesbusinessgrowth992]

these are super useful make tips. thanks.

[@AaronDelz]

You’re welcome! Just wait till you get to part 2 😁

[@chuntoon1]

Such great little tricks! I've been trying to find more uses for Make these days and these idea are awesome for building new routine!!!

[@AaronDelz]

Awesome! Glad you found use in them.

[@ThomasPacheco80]

bro, great video. I like the use of forcing an error to reuse the data. I would always copy the input data, paste into postman, and resend the data through postman. Love the tip on moving the filter too. very sneaky!

[@AaronDelz]

Awesome! Thanks man! Wait till you see my Tip #6, an alternative to using Postman. kzbin.info/www/bejne/hZOtiGOkj9BnjLc

[@gruesome24]

Cheers buddy for the tips. Can you go through the whole scenario in detail?

[@lexx8869]

Hello! Could you please make a video about ClickUp? In ClickUp tasks, you can use custom fields. However, when retrieving data from a task, ClickUp provides a collection of these fields, and each custom field in this collection has its own index. The issue is that it's not possible to write the specified custom fields in a task with a single operation; you have to use the iterator twice. Then, you need to use the aggregator twice to gather the steps back and avoid triggering the next step with each field. Is there a way to use a JSON array to reduce the number of operations?

[@AaronDelz]

These tips start from very simple and get more advanced. There's a little bit for everyone. If you have any questions about anything in this video, let me know below.

[@vhjvbhjb5280]

Hi, do you know if you can automate follow up emails to non openers in gohighlevel?

[@AaronDelz]

Yes, here you go: kzbin.infoAKwXss2kQDo

[@Imnotarealtor]

Letsgoo

[@AaronDelz]

🙌🏼 Hope you learned something awesome 😁

[@infinixi5]

Bro can you make automation scenario of taking blog post by rss feed and rephrase it in chatgpt and publish in wordpress

[@AaronDelz]

Yea I can do something like that

[@raoulvandine7086]

*Promo SM*

[@AaronDelz]

?