CONTENT CREATION

Upscale and publish localized images once review is approved

Triggered when a localized variant is approved in the review queue, upscales it to print resolution via Replicate, archives the final to object storage.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNotion card status changes to ApprovedNotionNotion
  • LogicConfirm approval is final with no open comments
  • ActionUpscale the approved variant via ReplicateReplicateReplicate
  • ActionUpload the production final to AWS S3AWS S3
  • OutputMark the Notion card Shipped with the S3 URLNotionNotion

What it does

Closes the loop after translation review. When a localized image variant is marked approved, it upscales the draft to delivery resolution using a Replicate model, stores the production-ready file in object storage, and updates the queue record to shipped.

When to use it

Use it as the publish half of a localization pipeline, paired with a regeneration workflow that fills the review queue. It guarantees only human-approved variants get upscaled and released, keeping compute off rejected drafts.

How it works

  1. 1A Notion event fires when a review-queue card's status flips to Approved.
  2. 2A logic step confirms the approval is final and the variant has no open reviewer comments.
  3. 3The flow sends the approved draft image to a Replicate upscaling model to reach print or retina resolution.
  4. 4The upscaled final is uploaded to an AWS S3 delivery bucket under its locale and campaign path.
  5. 5The Notion card is updated with the S3 URL and a Shipped status, completing the audit trail.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Connect ReplicateImage, video, and model inference.
  3. 3
    Connect AWS S3Buckets, objects, signed URLs.
  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.