The “Find records” action is the cause of your problem, and it’s actually not needed to make this work. Long story short, the documentation for the “Find records” action claims that its output can be used in any later step, but in a recent discussion with another user, it was pointed out that Airtable support claims that it’s only designed for use with email action steps.
Anyway, like I said, it’s not actually needed. When a record triggers the automation, that record’s data is instantly available via the trigger step, so there’s no need to find it separately. Set up the “Update record” action to use the data from the record in the trigger step, and it should work smoothly.
The “Find records” action is the cause of your problem, and it’s actually not needed to make this work. Long story short, the documentation for the “Find records” action claims that its output can be used in any later step, but in a recent discussion with another user, it was pointed out that Airtable support claims that it’s only designed for use with email action steps.
Anyway, like I said, it’s not actually needed. When a record triggers the automation, that record’s data is instantly available via the trigger step, so there’s no need to find it separately. Set up the “Update record” action to use the data from the record in the trigger step, and it should work smoothly.
Thank you, Justin! I spent some hours trying to solve the problem and reading the documentation.
I was just trying to classify my tasks according to the Eisenhower Matrix (using integrations with Todoist).
This is what I did: I used filters within the views, so I could avoid the “finding records” step. Now I have just two steps: when a record enters a view and updating record. It’s working just fine.
I was wondering if I could use “find record” as I intended, because I tried every possible combination and none of them worked. Now I know why: it’s not supposed to be used that way. Hahahaha!
Thank you for taking the time to answer. I am learning a lot from the community.
