Configure export jobs and export automations

Export by index or by prompt run

Export by index when the consumer wants the collection view. Export by prompt run when the consumer wants one execution boundary.

export = client.exports.create_index_export(
    index_id="idx_archive",
    prompt_run_ids=["run_123", "run_124"],
    destination_connector_id="conn_export",
    destination_subpath="exports/editorial",
)

Download versus connector delivery

Public exports can target:

• a downloadable artifact
• a connector destination

When using a connector destination, keep the export path within the connector's configured export_base_path.

Configure an export automation

Export automations are saved per index and define:

• destination_connector_id
• optional destination_subpath
• enabled and paused state

{
  "enabled": true,
  "paused": false,
  "destination_connector_id": "conn_export",
  "destination_subpath": "exports/review-team"
}

Operational recommendation

Use explicit subpaths when several downstream systems share the same destination connector. That keeps ownership boundaries obvious and avoids ambiguous output placement.