I’m trying to set up an automation between Jira and Airtable. I’ve got it working one way. When a new Jira issue is made, it creates a record in Airtable. But I’m stuck on making updates work.
I want Airtable to update when a Jira issue changes, especially the status. I tried setting up a Zap like this:
- Jira trigger: Updated Issue
- Airtable action: Find Record
- Airtable action: Update Record
But it’s not working. The ‘Find Record’ step can’t seem to locate the right Airtable record. I’m not sure what I’m doing wrong.
Has anyone done this before? Any tips on how to make it work? I can give more info if needed. Thanks!
I’ve actually encountered this exact issue before when setting up a similar integration. The key is definitely using a unique identifier, but there’s a bit more to it. What worked for me was creating a custom field in Airtable specifically for the Jira issue ID. Then, in the Zap, I used a ‘Formatter’ step between the Jira trigger and the Airtable ‘Find Record’ action. This step extracted just the issue ID from Jira’s data.
For the ‘Find Record’ step, I set it to search only that custom Jira ID field in Airtable. This approach made the matching much more reliable. Also, don’t forget to handle edge cases - like what happens if a Jira issue is updated before the Airtable record is created. You might need to add a Create Record action as a fallback if the Find step fails.
Hope this helps! Let me know if you run into any other snags.
My experience with integrating Jira and Airtable shows that a unique identifier is essential for smooth automation. I recommend adding a dedicated Jira Key field in Airtable and ensuring it is populated when records are created. When setting up your update automation, use the Jira issue key to locate the corresponding Airtable record. Adjust the Find Record step to search specifically in the Jira Key field. This method has worked consistently for me. Exploring nuanced features like Zapier’s Paths can further enhance your workflow by catering to specific update scenarios.
heya SwiftCoder42, i’ve done smthing similar. try using the Jira issue key as a unique identifier in both systems. in airtable, add a field for the Jira key. then in ur zap, use that to find the matching record. might need to tweak the ‘find record’ step to search the right field. lmk if u need more help!