CONTENT CREATION

Re-restore previously rejected low-resolution archive images

On a weekly schedule, finds Airtable rows marked 'Rejected — too low res', retries them through a higher-strength Replicate restore profile.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionQuery Airtable for rejected low-res rowsAirtableAirtable
  • ActionRerun through higher-strength Replicate profileReplicateReplicate
  • LogicQuality check against publish threshold
  • ActionPromote passing images to R2 and update AirtableCloudflareCloudflare R2
  • OutputPost recovered-image summary to DiscordDiscordDiscord

What it does

This workflow rescues images that failed an earlier restoration pass. It pulls rows flagged as rejected for low resolution, reruns them through a stronger Replicate restore profile, and re-evaluates — promoting the ones that now clear the bar and leaving the rest flagged for manual triage.

When to use it

Use it after model upgrades or when a new, heavier restoration profile becomes available and you want to reclaim assets that were previously unusable. It prevents good source material from being permanently abandoned in the reject pile.

How it works

  1. 1A weekly schedule starts the run.
  2. 2Query Airtable for rows with Status equal to Rejected — too low res.
  3. 3Rerun each source image through the higher-strength Replicate restore profile.
  4. 4A quality check compares the new output sharpness and resolution against the publish threshold.
  5. 5Passing images upload to R2 and their Airtable status flips to Restored.
  6. 6A summary of newly recovered images is posted to a Discord approvals channel for a final sign-off.

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
    Connect DiscordCommunity channels + voice + bots.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.