Skip to content
Img PilotImg Pilot

Automation workflows

Orchestration-only workflows that chain existing image features — triggers, conditions, and actions. Not AI agents; R2 remains the source of truth.

Orchestration only — not AI agents

Workflows automate sequences of features that already exist in Img Pilot: validation, processing, metadata approval, exports, Cloudinary publish, and webhooks.

They do not replace R2 object storage, invent new processing engines, or run autonomous AI agents. Every step delegates to the same server-owned services used by the dashboard and public API.

Disabling or deleting a workflow never deletes images, derivatives, or metadata in R2.

Triggers

Event triggers fire when domain events occur: image uploaded, validated, metadata approved, processing completed, bulk processing completed, or image published to an integration.

Manual triggers let authorized members queue a run from the dashboard (optionally scoped to a project and image).

Scheduled triggers run on an hourly, daily, or weekly interval for workspace-wide maintenance tasks such as batch exports.

Conditions and actions

Condition steps filter the run context — format, dimensions, byte size, metadata language, approval state, or publish state — before subsequent actions execute.

Action steps call fixed allow-listed operations: validate, optimize, resize (256/512/1024/2048 presets), convert format, generate metadata, wait for metadata approval, publish to Cloudinary, export CSV/JSON, send webhook, update status, or notify a user.

Each action step declares onFailure behaviour: fail the run, skip the step, or retry according to the workflow's retry policy.

Runs, limits, and permissions

Workflow definitions must be disabled before editing steps or metadata. Enabling requires at least one valid step.

Run history records step-level logs, error codes, and durations. Failed runs can be retried when policy allows.

Availability, concurrent runs, monthly run quotas, and maximum workflow count depend on your plan. View and manage permissions follow the workspace role matrix (view, manage, run).