Hey ​@darioschiraldi99!

Welcome to the automation journey lol.
The courses on the Airtable Academy should cover automations for sure.

What exactly are you trying to build? We can go through any of your use cases for a more practical approach to your questions. 

Mike, Consultant @ Automatic Nation

Welcome to the community, ​@darioschiraldi99!

Here a few automation tips to get you started:

1. Airtable’s automation instructions are located here.
    
2. One of the most common pitfalls that people stumble upon is when they try to use Airtable’s automation trigger “When a record is created”.
   
   Most people don’t realize that this trigger happens the very moment the record is created, which means that it will trigger while your new record is still completely blank, because you just created the record.
   
   The only time that this trigger wouldn’t trigger on a completely blank record is if the record was created through a form or created through Airtable’s REST API.
   
   And speaking of forms, you’ll definitely want to check out Fillout’s advanced forms for Airtable, which offer hundreds — possibly thousands — of advanced features to Airtable that you can’t get with Airtable’s forms, such as updating Airtable records with a form.

   
   I show off a few of Fillout’s advanced features in this video:
   Using Fillout to create an eSignature approval process with PDF file creation.
    

3. Another common pitfall occurs when people try to use the automation trigger “When a record is updated”, and then they tell Airtable to watch a text field.
   
   This will be problematic and will never work properly, because every single keystroke that somebody types into a text field will trigger the automation over & over & over again, because each keystroke counts as “updating the record”.
   
   The best solution for this is to use the “when a record matches conditions” trigger, or use this trigger is to watch a checkbox field or a single-select field.
   
   My favorite way of triggering an automation is a single-select field, because you can give the user feedback about their automation while the automation is running by changing the value in the single-select field. I write more about this technique in this thread.
    

4. The most important thing to know about Airtable’s automations is that they are very limited, and are best used for simple automations.
   
   For example, you are limited to 50 automations and 25 action steps per automation, you can’t combine repeating loops & conditionals within the same automation, you can’t have multiple conditional paths within the same automation, you can’t exit out of a conditional path to run additional actions, and you can’t integrate with too many external apps.
   
   The best way to solve all of these issues is to combine Airtable with Make’s advanced automations & integrations.
   
   If you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is one of the ways that you could instantly trigger a Make automation from Airtable.
   
   I also give live demonstrations of how to use Make in many of my Airtable podcast appearances. For example, in this video, I show how to work with Airtable arrays in Make.

Hope this helps!

If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld