CONTENT CREATION

Nightly batch restyle with Slack approval gate

On a schedule, restyles every pending packshot in Airtable through Replicate, then posts each variant to Slack for human approval before marking it publish-ready.

CategoryContent Creation
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires
  • ActionFetch pending packshots from AirtableAirtableAirtable
  • ActionRestyle each via ReplicateReplicateReplicate
  • OutputPost variants to Slack for approvalSlack
  • LogicBranch on approve vs reject, update AirtableAirtableAirtable

What it does

Runs an overnight batch that restyles all queued packshots and routes the results to a Slack channel where a brand reviewer approves or rejects each one. Approved shots are flagged ready; rejected ones loop back for a re-render.

When to use it

Use it when volume is high enough to batch overnight but brand quality still requires a human eye before anything goes live. Good for teams processing dozens of SKUs per day with a single approver.

How it works

  1. 1A nightly schedule triggers the batch run.
  2. 2The flow queries Airtable for all packshot rows with status "Pending restyle."
  3. 3Each pending packshot is sent to Replicate's background-replacement model with the brand scene preset.
  4. 4Each rendered variant is posted to a Slack channel with approve and reject buttons.
  5. 5A branch routes the reviewer's choice: approvals update the Airtable row to "Publish ready," rejections reset it to "Pending restyle" for the next run.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect ReplicateImage, video, and model inference.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.