Skip to main content

I have an Airtable automation that uses the AI module to summarize text fields for each record in a view. A repeating group iterates through that list. In Make, those newly updated records are processed through a Word template to output a report. I'd like to figure out a way to trigger them with one button press.

There are three ways I'm aware of for triggering Make, but I can't figure out how to make any of them to work.

  1. Webhook doesn't work (I think) because I need it to happen sequentially, with the Airtable automation running first.
  2. Record update: my original plan was to update the status of a report record that Make was watching after the Airtable automation looped through the whole list, but it doesn't look like you can add another action after a repeating group. So I also tried a script within the group that would count the loop iterations and compare to the list length, and at the end of the last iteration, would update the record. But I don't think it's possible to save the iteration count for the next iteration with input variables.
  3. New record: same problem as record update.

Alternatives I'm trying to avoid

I thought about triggering the Make automation before the repeating group, but then I'd have to set a timer somewhere in the process so the AI summary section has time to finish. The problem is, I think the amount of time this takes will be pretty variable, so I can't estimate how long it will be. I could set a super long one, but since users trigger with a button, I want the output (an email with the annual report) to happen fairly soon after that. This might be my plan B, though.

I know Make has AI modules, they just cost money, whereas I think I can get by on the free Airtable credits.

I know Airtable has document creation integrated in automations, but it's a complex document that it can't handle.

I thought about having like 10 status values that could be updated every time the loop went through, but that caused multiple problems, not the least of which is that there might be different numbers of records at different times.

Probably the easiest would be to just have two buttons, one to summarize fields and one as a webhook to launch Make, I just hate that from a UI standpoint.

It sounds like you want the Make scenario to run after all the actions in the repeating group have run for all of the records in the repeating group. You are running into difficulties because currently Airtable automations do not have a method of placing an action after all the repeating groups are done. You cannot even easily tell which record in the repeating group is the “last one” because records can be processed out of order. 

The solution is to have all the records being processed linked to a single parent record. Have a single select (or checkbox) field in each record that is to be processed. Inside the repeating group, after the other actions, update the single select to say that that record is processed. You will also need a rollup field in the parent record that will check if all the records are processed. Finally, have a second automation that is triggered when the rollup field says that all records are processed.

Depending on your workflows and if things need to be repeated, you may also need actions that reset the single-select. 

If you want to get fancy and avoid the rollup, you could use a script that checks the single-select of all the records to be updated and call the Make webhook only if all the records are processed. However, that might be harder to maintain.  

It sounds like you want the Make scenario to run after all the actions in the repeating group have run for all of the records in the repeating group. You are running into difficulties because currently Airtable automations do not have a method of placing an action after all the repeating groups are done. You cannot even easily tell which record in the repeating group is the “last one” because records can be processed out of order. 

The solution is to have all the records being processed linked to a single parent record. Have a single select (or checkbox) field in each record that is to be processed. Inside the repeating group, after the other actions, update the single select to say that that record is processed. You will also need a rollup field in the parent record that will check if all the records are processed. Finally, have a second automation that is triggered when the rollup field says that all records are processed.

Depending on your workflows and if things need to be repeated, you may also need actions that reset the single-select. 

If you want to get fancy and avoid the rollup, you could use a script that checks the single-select of all the records to be updated and call the Make webhook only if all the records are processed. However, that might be harder to maintain.  


This is what I ended up doing, thank you! 

For anyone having a similar problem, here's the details: I have a last updated timestamp field pointed at the summary field, and another field that shows the time of the latest update of the child records I'm summarizing. Formula field compares them and marks the field updated if the update stamp is later than the child field stamp. Then I have to do rollups through several levels of hierarchy to get to a final "Annual Report" record, which when all records are summarized, will trigger the Make automation.

Thanks for the insight!

Reply


Terms & Conditions