I created a Zapier workflow that makes a new Airtable entry whenever someone creates a Jira ticket with specific criteria. This part works fine.
Now I want to build another automation that updates the Airtable entry when someone modifies the Jira ticket. The main thing I need is for status changes in Jira to automatically sync to the matching Airtable row.
My current setup looks like this:
Trigger: Jira > Issue Updated
Action 1: Airtable > Find Record
Action 2: Airtable > Update Record
The problem is that the Find Record step keeps failing. It cannot locate the right Airtable row that matches the Jira ticket. Has anyone dealt with this before? What am I missing in my configuration?
hey, i had similar issues before. make sure the columns in airtable and jira have consistent naming. sometimes one little difference can cause the find record to fail. try that and see what happens!
This is usually a timing issue between your two automations. When the first Zap creates the Airtable record, there’s often a delay before the second Zap can find it. I had this exact problem last month - fixed it by adding a 2-minute delay before the Find Record step. Also check if you’re searching the right view. Airtable searches are view-dependent, so if your default view has filters, it won’t find records even though they exist. Switch your search to the main table view instead of any filtered views.
Your Find Record action isn’t working because the search criteria don’t match what’s actually in Airtable. When you first create the record from Jira, make sure you’re saving a unique identifier - usually the Jira issue key or ID. Then in Find Record, search that same field using the exact same format. I had this same problem when my Jira key got stored differently than what the trigger was sending. Double-check you’ve got the right Airtable base and table selected too. Pro tip: add a filter to your Jira trigger so it only processes updates for records that actually exist in Airtable.