Publish Pipeline
Publish generated outputs to local archives, cloud storage, Immich, WebDAV, and social or video destinations with approvals, retries, provenance, and versioning.
The publish pipeline takes an artifact produced by an agent and sends it to one or more destinations. It is designed for media and content workflows where generated outputs need review, metadata, provenance, resumable uploads, and durable publish history.
Enable Publishing
- Open Settings
- Select Publish
- Turn on Pipeline enabled
- Configure destination defaults
- Choose the C2PA signer mode for provenance metadata
Publishing can be limited to workspace-connected destinations when you want stricter workspace isolation.
Destination Types
Available destinations depend on configured connectors and enabled providers.
| Destination | Use Case |
|---|---|
| Local archive | Save a versioned copy in a local folder |
| Google Drive or cloud storage | Publish files to connected storage |
| Immich | Send generated images or videos back to a personal media library |
| WebDAV or rclone bridge | Publish to self-hosted or mounted storage |
| YouTube or TikTok | Publish video outputs to social video platforms |
| Social destinations | Route prepared assets to supported social accounts |
Some destinations require explicit approval before the publish job can proceed.
Publish an Artifact
- Open a task output, generated media item, or artifact preview
- Click the publish action when available
- Select one or more destinations
- Add title, caption, or other metadata
- Review the publish summary
- Submit the publish job
The job records destination legs separately, so a failure in one destination does not hide progress in another.
Approvals
Approvals are used for destinations that can make public or external changes.
An approval card may show:
- Destination name
- Source artifact
- Required metadata
- Risk or policy context
- Approve and reject controls
Approve only when the destination, content, and metadata are correct. Reject the job when a human edit is needed first.
Versioning
Each destination can use its own versioning mode:
| Mode | Behavior |
|---|---|
| Provider native | Use the destination's built-in versioning when available |
| Content addressable | Store by content hash to avoid duplicate uploads |
| Timestamped folder | Create a new dated folder for each publish |
| Overwrite | Replace the existing object when the destination allows it |
Use non-overwrite modes for generated media that may need auditability or rollback.
Provenance and Disclosure
The publish pipeline can build provenance metadata and inject disclosure into supported outputs. C2PA signing mode controls how provenance manifests are signed.
Use test mode for local evaluation. Use a workspace or cloud signer only after you have configured the signing material and understand how the destination will display provenance.
Publish History
The Library includes a publish history tab that shows recent jobs and their state. Use it to review:
- Job status
- Destination-level progress
- Failed or retried legs
- Published output references
- Provenance and disclosure information
If a publish job is interrupted, the pipeline records enough state to resume or report the final failure.
Troubleshooting
- If no destinations appear, configure the matching connector first
- If a job waits for approval, open Approvals and review the pending publish card
- If upload fails, check destination quota, file size limits, and credential validity
- If a video destination rejects metadata, shorten the title or caption and retry
- If provenance signing fails, switch to test mode or repair the signer configuration