ERR_MISSING_FIELD on Airtable: Required field missing. Root cause: A required field was not included in the incoming data payload. This occurs when the source record is missing a mapped field, when a field was renamed or deleted in the source system after the automation was configured, or when conditional logic skips populating a mandatory field. Step 1: Identify the missing field. Open the failing Airtable automation run log and look for the error message — it will name the exact field that is missing. Note the field name precisely, including capitalisation. Step 2: Check the source record. Go to the source table or app that triggered the automation. Confirm whether the field exists and has a value. If the field was recently renamed, the automation still references the old name and will fail until updated. Step 3: Update the field mapping in the automation. In Airtable Automations, open the action step that is failing. Under "Field mapping", find the entry for the missing field and either correct the source mapping or set a static default value (e.g. "Unknown") so the step always has something to write. Step 4: Add a conditional check before the action. Add a "Conditional" step before the failing action. Set the condition to check that the required field is not empty. If it is empty, route the automation to a separate "Send notification" action so you are alerted rather than silently failing. Step 5: Test with a real record. Manually trigger the automation using a test record that has the field populated, then one that does not. Confirm the first succeeds and the second hits the conditional branch correctly. Step 6: Audit all required fields in the table. In the Airtable table settings, review which fields are marked as required. Cross-check each required field against your automation mapping to ensure none are missing. Document this mapping so future schema changes are caught early.