CONTENT CREATION

Publish localized annotated screenshots to ReadMe docs on schedule

Each day, syncs newly approved localized screenshot sets from R2, checks which docs pages reference them.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionList approved localized image sets in R2CloudflareCloudflare R2
  • LogicFilter to sets whose checksum changed since last publish
  • ActionUpload images and update matching ReadMe pages per localeReadMeReadMe
  • OutputPost per-language update summary to SlackSlack

What it does

Keeps your published help center in sync with the latest annotated, localized screenshots. On a daily schedule it scans R2 for image sets marked approved, matches each set to the ReadMe doc pages that reference it, and replaces the live images with the newest annotated versions per language so localized docs never drift behind the source.

When to use it

Use it when annotated tutorial images are regenerated frequently and you publish multilingual docs in ReadMe. It removes the manual step of re-uploading images to each language's page after every refresh.

How it works

  1. 1A daily schedule fires the trigger.
  2. 2The flow lists R2 objects under the approved-sets prefix and reads each set's locale and target page metadata.
  3. 3A logic check filters to only sets whose checksum differs from what is currently live in ReadMe.
  4. 4For each changed set it uploads the new images and rewrites the image references on the matching ReadMe page for that locale.
  5. 5It posts a summary of updated pages per language to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Cloudflare R2Object storage, S3-compatible.
  2. 2
    Connect ReadMeAPI docs, changelog, auth.
  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.