Reusable workflows for product content.

Build the pipeline once: ingest, AI cleanup, approvals, metadata, and publishing. Run it from the dashboard today. Triggered runs for uploads, schedules, and webhooks are planned next. Workflow run history is available today. Workflow definition versioning is planned separately from triggers and requires a dedicated versioning system.

Start free - 25 credits Book a demo

Visual builder, no code

Manual dashboard runs today

Upload triggers planned next

Reusable templates

workflow · spring-26-product-pipeline

running

Source: Drive

/spring-26/raw

Remove BG

Auto edge refine

Auto-tag

Vision · GPT-4o

Upscale 4x

Topaz · 4096px

running

Save to DAM

Sirv · /processed

Step 3 of 5 · ETA 1.4s1,847 assets processed

−92%

Hands-on time per batch (vs scripted ad-hoc edits)

100s

Items per workflow run, processed in parallel

Manual

Workflow starts today. Upload triggers are planned next.

Servers to babysit. Runs on Sirv infrastructure.

Four steps to a reusable pipeline

Compose nodes once, save the workflow, and run it on the next batch.

Start from the dashboard

Run a saved workflow manually on images, batches, or saved product sets.

Chain AI ops

Background remove, upscale, generate, alt-text, composed in one pass.

Route for approval

Send to a reviewer, queue for QA, or auto-publish if rules pass.

Publish anywhere

Push to Shopify, your CDN, a vendor folder, or a webhook payload.

Starts

Today, next, later.

Manual runs are the shipped path. Upload, schedule, webhook, and change starts are planned in phases so the automation has the right org, credit, and safety guardrails.

Manual run today

Pick assets or a batch in the dashboard and run a saved workflow when you are ready.

Upload triggers planned

Next phase: dashboard upload batches can start a workflow automatically after the files are ready.

Scheduled runs planned

Later phase: run saved workflows on a clock against saved collections, smart collections, or product groups.

Webhooks planned

Later phase: secure inbound webhooks can queue workflows after HMAC verification and safe asset import.

Change events later

Product, asset, and approval change events need loop prevention before they become workflow triggers.

Actions

Six action families to compose.

Drag actions onto the canvas and wire them together. Each action is a node, branch, approve, transform, write back, notify.

AI ops

Background remove, upscale, generate variants, write alt text, detect objects, smart crop.

Conditional branches

Route by attribute, file type, dimensions, brand, or any catalog field. If/else without code.

Approvals

Send to a reviewer, hold for QA, or auto-approve when validation passes the spec floor.

Publish

Push to Shopify, your CDN folder, a vendor return path, or a webhook payload downstream.

Catalog writes

Update product attributes, tags, status, or PIM fields when the run completes.

Notify

Email, Slack, or webhook on success, failure, or partial. One summary per batch, never per file.

Templates

Six workflows you can adapt.

Each template is a working pipeline you can clone, point at your products, and run from the dashboard. Triggered starts can attach later.

Catalog ingest → live products

Raw photos in, store-ready products out. Background, upscale, lifestyle variant, alt text, then Shopify push.

1Manual batch run
2Background remove + upscale
3Generate lifestyle variants
4Alt text
5Approve in batch
6Push to Shopify

Vendor submission → approved asset

Vendor drops files in the portal. Validate, auto-fix the small stuff, route the edge cases to a human, publish.

1Manual run on accepted uploads
2Spec validation
3Auto-fix where possible
4Reviewer queue for edge cases
5Publish to CDN + Shopify

Nightly catalog hygiene

Planned schedules will sweep the catalog, fix drift, and refresh anything that's missed the spec since the last pass.

1Planned schedule
2Find products missing alt text or below spec
3Re-run the relevant AI ops
4Notify catalog owner of changes

Marketplace channel pack

One source asset, six channel-ready variants. Each marketplace gets exactly the spec it requires.

1Hero asset approved
2Branch by channel rules
3Resize + reframe per channel
4Validate against marketplace specs
5Deliver per channel

Alt-text + tag refresh

Run AI copy refreshes on products where text is thin or the image changed.

1Manual or API run
2Re-run alt text
3Suggest tags
4Diff vs current → write back to PIM

Rejected asset cleanup

A future change trigger can remove rejected assets from downstream delivery and notify the right team.

1Planned rejection event
2Pull from CDN folders
3Detach from Shopify product
4Restore prior version if any
5Notify vendor

Operating modes

Manual today. Event-driven later.

The current workflow engine runs saved pipelines on demand. The planned trigger layer will add upload batches first, then schedules and webhooks.

Event-driven

Upload batches are the first planned trigger. A dashboard batch should become one workflow run with all matching assets, not a pile of per-file runs.

1Dashboard upload batch completes
2One workflow run receives the matching assets
3AI ops, validation, approval, publish
4Notification on success / failure

Scheduled & batch

Catalog hygiene, alt-text refreshes, marketplace re-packs, monthly archives. These are planned after the upload-trigger path is proven.

1Saved schedule selects a collection or product group
2Filter the catalog by the saved selector
3Run the AI ops in parallel across the batch
4Single summary report with counts, costs, errors

Guardrails

Production-grade by default.

Workflows fail in messy ways when you build them yourself. The shipped runner handles execution history and retries. Trigger-specific budgets and runaway controls are planned before automatic starts ship.

Retries with backoff

Transient failures retry automatically with backoff. A flaky third-party API doesn't blow up your run.

Per-step error routing

Catch a step failure and branch to a human, to a quarantine queue, or to a fallback path.

Parallel by default

A workflow over 200 SKUs runs items in parallel on Sirv infrastructure. You don't hand-tune concurrency.

Run history and replay

Every run is logged with inputs, outputs, and timing per step. Replay a failed run after a fix without rebuilding state.

Credits-aware

Each manual run shows credit cost up front. Trigger-level monthly credit caps are planned before automatic starts ship.

Scoped to your workspace

Workflows respect workspace permissions and product scoping. Planned trigger runs will use the same org boundary.

FAQ

What ships now, what comes next.

Do I need to write code to build a workflow?

No. The visual builder covers AI ops, branching by catalog attributes, approvals, and publishing. Triggered starts are planned, but saved workflows already run manually from the dashboard.

What kinds of triggers can fire a workflow?

Manual dashboard runs are available today. Upload triggers are planned next. Scheduled runs and secure inbound webhooks come after the trigger foundation is in place. Change-event triggers come later because they need loop prevention.

Can workflows talk to Shopify and our PIM?

Yes, bi-directionally. A workflow can read from Shopify (pull a product to process), write to Shopify (push the approved image, update alt text), and write back to your PIM via the REST API or webhooks. Pull-then-push patterns are first-class.

What happens when a workflow run fails halfway?

Per-step error routing. Branch on failure to a human, to a quarantine queue, or to a fallback path. Transient errors retry automatically with backoff. Every run is logged with full step history so you can replay from the failed step after a fix, not the start.

How do credits work inside a workflow?

Each AI op inside a workflow consumes credits exactly like the same op run by hand. The builder shows manual-run cost up front. Trigger-level credit budgets are planned before upload, schedule, or webhook triggers ship.

Can vendors trigger a workflow?

Not yet. Vendor uploads can be processed through workflows manually today. Vendor-originated triggers are a later phase, and they will only resolve products and assets inside that vendor's grant.

How many workflows can I run on each plan?

Free has no saved workflows. Core includes 10 saved workflows with up to 500 batch items per run. Growth includes 50 saved workflows with up to 2,000 batch items per run. Enterprise is custom.

Can I version a workflow definition?

Workflow run history is available today. Workflow definition versioning is planned separately from triggers and requires a dedicated versioning system.