I built a form in Airtable that has collected more than 50 responses so far. When I set up the form initially, I configured an automation workflow to trigger whenever someone submits the form. This automation is supposed to send out an email notification and generate a new record in my base.
The problem I’m running into is that the automation isn’t working as expected. Instead of creating the record on the same row where the form submission data appears, it’s generating records on completely different rows. This is messing up my data organization and making it hard to track which records correspond to which form submissions.
Has anyone encountered this issue before? What’s the best way to fix this automation so the records get created in the right place?
Sounds like you’ve got multiple automations running or triggers conflicting with each other.
I’ve seen this exact thing when someone accidentally creates duplicate automations that fire simultaneously. Check your automation panel - make sure there’s only one automation triggering on form submissions.
Another common issue: your automation tries creating records in a different table than where the form data lands. Form submissions already create records automatically, so your automation might be making extras instead of working with existing ones.
Turn off the record creation part and just keep the email notification. Forms already handle record creation, so you don’t need automation doing it too.
Need to update existing form records with extra data? Switch your automation to “update record” instead of “create record” and use the record ID from the form trigger.
Had this exact headache a few months back and it drove me crazy for days. Turned out my base structure was the problem - I was working with linked tables and the automation was creating records in the wrong table. Check if your form connects to Table A but your automation creates records in Table B. This happens more than you’d think, especially if you copied automations from other bases or modified them later. Also check your field mappings in the automation. Sometimes it pulls data from the trigger but maps it to fields that don’t match your form’s output fields. Go into your automation settings and verify each field mapping matches your actual form fields. One more thing - check if you’ve got view filters active on your main table. The records might be getting created correctly but filtered out of your current view, making it look like they’re going to wrong rows.
I faced a similar issue with Airtable where my automations weren’t aligning correctly with form submissions. It often happens when the automation is set to trigger on “record created” rather than specifically for form submissions. Airtable may unintentionally create temporary entries that conflict with existing ones. I recommend changing the trigger to “When form is submitted” if possible. If that option is unavailable, consider adding a condition that references a unique field filled out during the form submission. Additionally, verify that there are no filters applied to your view, as they can obscure the records your automation is interacting with.
totally get how an issue like this can mess things up. also, double check how your form is mapped to the table, maybe there’s a config issue? good luck!