CONTENT CREATION

On-demand variant render from PIM webhook

Accepts a webhook from your PIM or storefront with a SKU and target channels, renders the matching background variants with Replicate.

CategoryContent Creation
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWebhook: SKU + target channelsHTTP webhook
  • LogicValidate SKU cutout and channel presets
  • ActionRender one variant per channel with ReplicateReplicateReplicate
  • ActionStage variants in Dropbox and log to AirtableDropboxDropbox
  • OutputReturn staged variant URLs in webhook responseHTTP webhook

What it does

Lets another system request background variants synchronously. A PIM, storefront, or internal tool posts a SKU plus the channels it needs (web, marketplace, social), and the workflow renders just those background treatments, stages them, and returns the resulting URLs in the webhook response.

When to use it

When variant generation should be triggered by another application rather than a folder drop or schedule, and the caller needs the staged image links back immediately to continue its own flow.

How it works

  1. 1An HTTP webhook arrives with a SKU and a list of target channels.
  2. 2A validation step confirms the SKU resolves to a stored cutout and the channels map to known background presets.
  3. 3Replicate renders one background variant per requested channel.
  4. 4Variants are written to the staged Dropbox folder and review rows are logged in Airtable.
  5. 5The output step returns a JSON payload of staged variant URLs to the calling system.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect ReplicateImage, video, and model inference.
  3. 3
    Connect DropboxFiles and folders.
  4. 4
    Connect AirtableBases, tables, views, automations.
  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.