Zapier Triggers before "Last modified Time" Airtable

Hi @Rlaurence83 

Good question.

You may need to adjust your View Filter conditions to prevent new/existing record from both triggering the Zap.

Also, you can further control your Last Modified field by limiting it to watch specific fields.

Otherwise, you can use Airtable Automations to have more control over trigger the Zap:

https://community.zapier.com/show-tell-5/advanced-how-to-trigger-zaps-instantly-from-airtable-6816

Hey @Rlaurence83!

EDIT: Troy got to it just before me and offers some great tips :)

I’m not 100% sure I’m following what your Airtable workflow is. Could you clarify what the desired outcome is and how you’ve got Airtable set up?

Is the column you’re using for “last modified time” do you have it set up for all editable fields or specific fields?

Thanks!

Hey nick its set for a specific field.



I have a “all production” view that acts as the main source for all records. When i check mark “description needed” it will then filter into the next view. I am then checking “transcribe to text” which triggers the automation. It works well every time 

The issue is the zap will trigger when the record enters the view and again i checked the “transcribe to text” which is the last modified time for my zap. so thats why im confused.

its not a big deal but does use double the zaps intended for the automation as its ran twice. The first zap gives me different result as i require other process to happen first before i trigger the transcribe to text.

Hope this make sense - ive included some screen shots 

thanks troy - ill work on this now - legend as always :)