Draft Recraft hero images for Airtable content briefs

Whenever a new content brief row appears in an Airtable content calendar table, an agent should draft a matching hero image with Recraft and write the resulting image URL back into the row so writers see the visual as soon as they open the brief.

Trigger: Airtable poll for a new_record on the content calendar table (Airtable is a first-class poll provider). The workflow runs once per new row.

For each new row the agent should:

1. If a Hero Image value is already set on the row, stop immediately and do nothing. Never overwrite an image a human has already picked.

2. Read the row's topic, angle, and brand voice fields, plus any asset-type field that indicates whether the piece needs a hero photo, an illustration, or a logo/icon. Also read any per-row or per-base brand style prompt and any Recraft brand style ID that has been stored for this base.

3. Draft a concise Recraft image prompt (2-4 sentences) that combines the topic, angle, and brand voice, and folds in the per-base brand style prompt when present.

4. Pick the Recraft operation based on the asset-type field. If the row calls for a logo, icon, badge, or other flat vector asset, use Recraft's Generate Vector Image (SVG) operation. Otherwise use Generate Image for a raster hero. Pass the Recraft brand style ID when the base has one configured.

5. Take the first returned image URL and use Airtable's Update Record operation to patch that URL into the row's Hero Image field. Do not clear or overwrite any other fields on the row.

Integrations used: Airtable (poll new_record trigger + Update Record) and Recraft (Generate Image for raster and Generate Vector Image (SVG) for logos/icons).

Nuance to bake in: always respect the per-base brand style, pick raster versus vector from the row's asset-type field, skip rows that already have a hero image, and only ever write to the Hero Image field on the triggering row.