CONTENT CREATION

Route generated hero captions through Slack approval before Coda

Exports a Figma hero, drafts a caption with generate-image, posts it to Slack for human sign-off.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerFigma frame marked readyFigmaFigma
  • ActionExport hero + generate candidate captionImage generation
  • ActionPost image and caption to Slack review channelSlack
  • LogicBranch on editor approve/reject reaction
  • OutputWrite approved caption to Coda draftCodaCoda

What it does

Adds a human checkpoint to AI-written hero captions. After exporting the frame and generating a caption, it posts the image and proposed caption to a Slack review channel. An editor approves or rejects with a reaction; only approved captions land in Coda, keeping off-brand copy out of the pipeline.

When to use it

Use it when brand voice matters and you don't want machine-generated captions published unreviewed, but you still want the speed of auto-drafting. Good for teams piloting AI captioning who need a safety gate.

How it works

  1. 1A Figma frame is marked ready (webhook fires).
  2. 2The flow exports the hero PNG and generate-image writes a candidate caption and alt text.
  3. 3The image plus proposed caption are posted to a Slack review channel.
  4. 4A logic step waits for an approve or reject reaction from an editor.
  5. 5On approval, the caption is written to the Coda draft row; on rejection, the row is flagged for a manual rewrite.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect FigmaFiles, frames, comments, assets.
  2. 2
    Connect Image generationManaged Nano Banana image renders, metered per image.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Connect CodaDocs, packs, automations.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.