I have a working Zapier automation that creates new Airtable records whenever specific Jira tickets get created. This part works fine.
Now I’m trying to build another Zap that updates the Airtable record when someone changes the Jira ticket status. My current setup looks like this:
- Trigger: Jira > Issue Updated
- Action 1: Airtable > Search Record
- Action 2: Airtable > Modify Record
The problem is that the search step keeps failing. It cannot locate the matching Airtable record that corresponds to the updated Jira ticket. Has anyone dealt with this before? What am I missing in my configuration?
This usually happens because of timing issues between your two Zaps. Your first Zap creates the Airtable record, then your second Zap immediately tries to search for it after the Jira status changes - but there’s often a delay before that record becomes searchable. I ran into this exact problem and fixed it by adding a 2-3 second delay before the search action in my second Zap. Also check if your Jira trigger fires for all field updates or just status changes. If it’s catching every update, you might be searching for records that don’t exist yet. And make sure your Airtable view permissions let the search access all records, not just filtered ones.
hey! i had a similar issue before. make sure ur using the right fields in ur search setup, that can mess things up. also, try using the jira issue ID, it seems to link better. hope that helps!
Search failures usually mean there’s a mismatch between what you’re searching for and how the data’s actually stored in Airtable. I ran into this exact problem last year with a similar setup. Check if your Jira ticket ID is being stored consistently - sometimes the first Zap adds extra characters or formats it differently than what the second Zap expects. Also make sure you’re searching the right column type in Airtable. I had to switch from a generic text field to a more specific field type to get reliable matches. Try testing the search step manually with a record you know exists to see if your parameters are working.