Search documentation
Search pages, API reference sections, and guide headings.
Summary
This guide covers one-time import jobs and persistent index-level import automations that watch a storage location and trigger processing with a prompt preset.
Start with a one-time import job
job = client.import_jobs.create(
connector_id="conn_archive",
index_id="idx_archive",
source_prefix="incoming/2026/04/",
file_pattern="*.mp4",
recursive=True,
)
Poll or retrieve the job to inspect:
progress- imported
video_ids - failed files
- skipped files
Add an import automation
Import automations are index-level saved configurations. They require:
connector_id- source prefix and file pattern
debounce_intervalprompt_presetwith at leastprompt_id
{
"enabled": true,
"paused": false,
"connector_id": "conn_archive",
"source_prefix": "incoming/daily/",
"file_pattern": "*.mp4",
"recursive": true,
"debounce_interval": "10m",
"prompt_preset": {
"prompt_id": "prompt_episode_extract"
}
}
Debounce intervals
Supported public debounce intervals are:
5m10m1h1d
Use the shortest interval that matches the business process rather than trying to simulate near-real-time internal polling behavior.
An import automation requires a prompt preset snapshot. If the automation needs to run prompt processing after
import, do not omit prompt_id from the preset.
Pause and resume
Import automations can be paused and resumed without deleting the saved configuration. That is the preferred control for temporary operational freezes.
Related documentation
Import jobs bring cloud storage media into a target index. Use automations when the same connector path should feed recurring media intake.
Automations watch connector paths, trigger prompt presets, and deliver index exports for recurring VideoVector workflows.
Connectors provide the storage access boundary for imports and exports. This guide shows how to create them, test them, and choose scopes safely.
