Skip to main content
Question

Post-Repeating Action in Automation

  • Sep 24, 2026 2:33 PM UTC
  • 7 replies
  • 92 views

e2laurel
Forum|alt.badge.img+9

I’d like to add an action at the very end of my automation that sends me an email once the repeated action block is done running. Is there a workaround way to do this?

 

7 replies

TheTimeSavingCo
Forum|alt.badge.img+32

Try adding a ‘Find Record’ step to get the records that should meet the new updated criteria, and then use a conditional step to check if they match?  I’ve set it up here for you to check out!

And here’s how the automation looks:


e2laurel
Forum|alt.badge.img+9
  • Author
  • Known Participant
  • Sep 24, 2026 3:40 PM UTC

​@TheTimeSavingCo 

Hello, I gave this a try but it seems like it’s finding all the records in the list immediately (resulting in several emails going out). It should go sequentially, right? I cannot figure out why it’s seeing all records as “updated” at once. The conditions for the email are if length of “Find all other line items” matches length of “Check List Progress”

 


TheTimeSavingCo
Forum|alt.badge.img+32

Hm, could you provide screenshots of the ‘Find Record’ and ‘Update Record’ steps?


e2laurel
Forum|alt.badge.img+9
  • Author
  • Known Participant
  • Sep 24, 2026 3:45 PM UTC

I’ve also confirmed that the “Archive Final Price” field is empty prior to the automation running ​@TheTimeSavingCo 


TheTimeSavingCo
Forum|alt.badge.img+32

Ah, so sorry!  This is because the repeating group is running in parallel and the checkbox looks like it’s working because after it gets ticked it stays like that, it can’t get more ticked, does that make sense?

To solve this perhaps you could update the automation to mark a checkbox once the tasks are complete, and have another automation trigger off of that checkbox instead?


WorkflowEngineer
Forum|alt.badge.img+1

If every iteration ticks the same parent checkbox, that tells you an item has finished, not that the whole batch has finished. Moving the email to a second automation won’t fix that on its own.

I’d track completion per batch:

• Set the batch’s full item list before processing starts.
• Mark each item complete only after its final required action succeeds.
• On the batch record, count completed items against the expected total, keeping completion markers specific to that run.
• Have a second automation notify only when the batch is initialized and nonempty, completed = expected, and “Notified” is unchecked. Then mark the batch notified.

If a short delay is acceptable, I’d use a scheduled Find Records check for that second automation. Airtable documents timing pitfalls with aggregate recalculation and recommends scheduled checks as a fallback:
https://support.airtable.com/articles/7369519794-airtable-automation-trigger-when-record-matches-conditions

This keeps the email out of the individual iterations. The Notified flag prevents ordinary repeat sends, but it isn’t a strict exactly-once guarantee: sending could succeed while saving the flag fails.

-Roe


Forum|alt.badge.img+2
  • New Participant
  • Oct 26, 2026 7:24 PM UTC

This is a helpful way to think about it. Tracking completion for the whole batch, rather than relying on a single shared checkbox, makes the final email much more reliable.