CONTENT CREATION

Weekly Ad Variant Batch to R2 Asset Library

On a weekly schedule, pulls active campaign briefs from Airtable, generates fresh ad variants on Replicate.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionFetch Active campaign briefs from AirtableAirtableAirtable
  • ActionGenerate weekly variant set on ReplicateReplicateReplicate
  • LogicBrand-safety gate rejects non-compliant images
  • ActionUpload approved images to R2 bucketCloudflareCloudflare R2
  • OutputWrite asset manifest back to AirtableAirtableAirtable

What it does

Each week it reads every campaign brief flagged Active in Airtable, regenerates a fresh set of creative variants per campaign on Replicate, screens them for brand safety, uploads the approved images to a Cloudflare R2 bucket organized by campaign, and writes a manifest mapping each asset to its brief and seed.

When to use it

When you run always-on campaigns that need a steady supply of new creative to fight ad fatigue, and you want a durable, addressable asset library rather than images scattered across chat threads.

How it works

  1. 1A weekly schedule fires the trigger.
  2. 2All Active campaign briefs are fetched from Airtable.
  3. 3For each brief, Replicate generates the week's new variant set.
  4. 4A brand-safety gate rejects non-compliant images before they ever leave the pipeline.
  5. 5Approved images are uploaded to R2 under a per-campaign path.
  6. 6A manifest of asset URLs, seeds, and source briefs is written back so downstream schedulers can pick from the library.

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 Cloudflare R2Object storage, S3-compatible.
  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.