How-to

Export and import

A portable package is how you promote a single integration from a laptop to shared, or from staging to production. It is not a cluster config-bundle and not a platform backup.

The artifact is sirius.integration-bundle/v1: signed JSON with a content hash. Secrets travel as references (secretref:…). Import never invents secret material.

Export

In Build, open the integration → History → Export. Toggle full history if you need every published version; the default is the latest published graph.

The package includes:

Workflow name, description, tags, group
Graph nodes and edges
Scrubbed connector snapshots
Studio workspace and milestone links (informational — workspaces are not created on the target)
Compile hints (kinds, language) — not compiled binaries

curl -s "$SIRIUS/workflows/$WF/export" -o orders.sirius.json
# optional: ?history=all

Validate, then import

Always validate first. The preview lists conflicts, missing secret refs, and unbound connectors.

curl -s -X POST "$SIRIUS/workflows/import/validate" --data-binary @orders.sirius.json
curl -s -X POST "$SIRIUS/workflows/import" --data-binary @orders.sirius.json

Import options (console checkboxes or JSON fields):

Option	Meaning
`id_strategy`	Keep source ids or allocate new ones
`conflict`	Fail, rename, or replace on collision
`restore_connectors`	Recreate connector snapshots as secret refs
`publish`	Publish after import, or leave a draft

In the console: Build → Integrations → Import. Read the validate preview, then confirm.

After import

Create or bind the missing secrets on the target tenant.
Probe connectors.
Open Studio links and recreate workspaces if you need the tests, or export/import the Studio bundle separately (GET /studio/workspaces/{id}/export).
Start the integration.

Missing secretref: targets are warnings, not silent omissions. Treat them as a checklist.

See Restore a version for in-place history on the same tenant.