No-code automation
How to Automate Images from Airtable
Airtable often becomes the working database for campaigns, products, listings, speakers, and content calendars. Image automation works well when the table contains structured values and a clear approval state—not when every edit immediately creates another image.
· 7 minute read
Build a record schema for automation
Keep content fields separate from workflow fields. A campaign table might contain headline, photo, offer, and CTA alongside template_key, generation_status, output_url, generated_at, and error_message.
- ✓One stable record ID
- ✓One field for each dynamic layer
- ✓An explicit Ready or Approved status
- ✓Template and format selection
- ✓Output URL and failure fields
Trigger from approval, not activity
A record can change many times while a campaign is being prepared. Trigger when status becomes Ready, when a checkbox is intentionally selected, or when the record enters a filtered view.
Add a condition that skips records with a completed output unless a separate regenerate flag is present. This prevents harmless copy edits from consuming generation credits.
Choose the connection layer
Zapier is convenient for a straightforward trigger and action. Make is useful for visible branching and transformations. n8n offers more control and self-hosting. A custom service is appropriate when Airtable is part of a larger product workflow.
Regardless of the tool, normalize currency, dates, empty values, and attachment URLs before calling the image API.
Write evidence back to Airtable
Store the generated URL, timestamp, template ID, and completion status in the originating record. When generation fails, write a concise error that an operator can fix without opening the automation platform.
Frequently asked questions
Can one Airtable record generate several image sizes?
Yes. Map the same record to several approved templates and store each output in a dedicated field or linked output table.
What happens when an Airtable attachment URL expires?
Copy the asset to stable public storage or ensure the workflow requests a fresh accessible URL before generation.