DOCUMENT OPS

Promote a tagged Figma asset set from staging R2 to production with Slack sign-off

When a release row is tagged ready in Coda, copies that version's assets from the staging R2 bucket to the production bucket and posts the live URLs to Slack for the team.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCoda release row marked readyCodaCoda
  • LogicVerify approval and read version asset keys
  • ActionCopy staging R2 objects to production bucketCloudflareCloudflare R2
  • ActionUpdate Coda release row with prod URLsCodaCoda
  • OutputPost live CDN links to SlackSlack

What it does

Gates CDN promotion behind an explicit release tag. Designers stage exports to a non-public R2 bucket; when a release row in Coda is marked ready, the flow copies exactly that version's assets into the production bucket and announces the live URLs in Slack.

When to use it

Use it when you need a deliberate staging-to-production step for brand or product assets — for example, holding a redesigned icon set behind a launch date instead of letting every Figma save go live immediately.

How it works

  1. 1A Coda row update where a release is flagged ready triggers the flow.
  2. 2A logic step confirms the row is approved and reads the version id and its asset keys from the manifest.
  3. 3Each staging R2 object for that version is copied to the production R2 bucket at its public key.
  4. 4The Coda release row is updated with the production URLs and a promoted-at timestamp.
  5. 5A Slack message posts the release name and the list of newly live CDN links to the team channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CodaDocs, packs, automations.
  2. 2
    Connect Cloudflare R2Object storage, S3-compatible.
  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.