When creating a trigger using the “When Record Matches A Condition”, is there a way to enter a table value into the matching field, other than a hard-coded value? For example, the table has 2 columns, nCost] and aOriginal Cost]. Want to trigger an update when hCOST] != Original Cost], but it seems to only allow entering of an actual value. “When Record is Updated” trigger does work to accomplish this, but it can take about 10 seconds to update the destination field, and begins to execute the trigger the moment the value box is changed (If the value entered 100, it seems to run for 1,0,0 and then 100, as I can see the other fields updating with multiple values until the final value). Sometimes, if we type too quickly, it doesn’t update and will update based on “10” rather than “100”.
In my opinion, this is one of the big problems with automations — the fact that they trigger while users are still editing a field.
I feel like automations should WAIT until users have left the field before triggering an automation.
So for now, the best workaround for this is to trigger your automations with either a checkbox field or a single-select field.
Single-select fields are particularly useful, because you can have the automation change the value of the single-select field while the automation is running.
This can be used to give information to your user during the automation run, such as “Running”, “Complete”, “Error”, etc.
You can read more about this technique in my posts in this thread.
You could also run your automations on a schedule. This would be considered a “delayed trigger”, so you might be waiting for a while until the automation kicks in.
However, if you go down this path, you could end up eating your limited amount of automation runs every month, and that is a major problem because Airtable gives no way to add more automation runs into your monthly set of runs!
So, for scheduling automations (or creating more advanced automations with Airtable), I would highly recommend using Make’s advanced automations & integrations.
Make’s automations are way more advanced than Airtable’s automations, and they also let you purchase more runs if you go over your monthly limit.
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 have a budget and you’d like to hire the best Airtable consultant to help you with this or anything else that is Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld
Having the same issue here… Were you able to solve it @Ryan_Taliercio Or any new ideas on how to pass this @ScottWorld ?
Tnx
Having the same issue here… Were you able to solve it @Ryan_Taliercio Or any new ideas on how to pass this @ScottWorld ?
Tnx
Which issue are you having?
- ScottWorld, Expert Airtable Consultant
Think I may have figured this out (or at least a workaround) -
- Create a formula field in the table where you have the fields you want to compare, written as IF({Field 1)}={Field 2}, “Yes”, “No”)
- You could also use other output values like 1, 0
- You could also use other output values like 1, 0
- In your automation, you can then use the trigger “When a record matches conditions” and simply add the condition as “When tChoose your formula field created above] is eyes]”, and proceed with whatever update action you’d like after that.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.