Fixing a Fragile Email Automation in Make.com

Today I worked on stabilizing an Airtable to Email automation that was failing due to validation errors.

The workflow itself was simple Airtable trigger to email send but the details were causing issues. Errors like invalid email address and array of objects expected usually mean the data structure is slightly off even if it looks correct on the surface.

The first step was making the automation future proof by switching all Airtable mappings to Field IDs instead of column names. That way the scenario will not break if fields are renamed later.

Then I rebuilt the To CC and Reply To logic properly. Instead of raw strings I used correct array formatting with split flatten deduplicate and remove. This ensured empty fields do not create invalid values and a fallback email is always included without breaking the module.

Finally I added basic checks so the workflow never attempts to send an email without a subject or body.

This was not about adding complexity. It was about making the automation reliable predictable and safe to run in production.

1 comment