I created a Zapier workflow that makes a new row in my Airtable database whenever someone creates a Jira ticket with specific criteria. This part works fine.
Now I want to build another Zap that updates the Airtable row when someone changes the Jira ticket. The main thing I want to sync is when the status gets updated in Jira, it should change the status in the matching Airtable row too.
My current setup looks like this:
Trigger: Jira issue gets updated
Action 1: Search for the matching record in Airtable
Action 2: Update that record with new info
The problem is the search step keeps failing. It cannot locate the right Airtable record that matches the Jira ticket. Has anyone dealt with this before or know what might be going wrong?
check your search criteria in the airtable lookup step - you probably need a unique field like the jira ticket id or key. had the same issue, and it turned out i was searching by title, which isn’t always an exact match. make sure you’re storing the jira key when you create the initial record.
This sounds like a field mapping issue. I’ve hit this before - usually the lookup field has different data types or formatting between Jira and Airtable. Check that your lookup key (ticket number, ID, whatever you’re using) is stored exactly the same way in both systems. Test the search step independently with a known record to see what’s actually getting passed through. Sometimes extra characters or spaces break the match. If you’re still stuck, use Zapier’s formatter to clean up the search value before it hits Airtable.