Available as an add-on on paid plans.
How storage fits in
Storage is configured on a task. When a task run executes with storage enabled, captured files become storage items tied to that run. Retrieving an individual item gives you a signed download URL and, if extraction is on, structured data pulled from the file.Enabling storage
Storage can be enabled on a task from the Console or the API.| Fields | What it does |
|---|---|
enabled | Capture files produced during execution |
extraction | Parse captured files into structured JSON |
extraction_schema | JSON Schema that controls what fields are extracted (required when extraction is on) |
extraction_prompt | Optional natural-language guidance for the extraction model |
deduplication | Skip files that match a previous capture, based on field values you choose |
deduplication_schema | JSON Schema that defines the fields used for duplicate detection (required when deduplication is on) |
Extraction
Extraction works with PDFs, invoices, receipts, statements, and common document types. Useextraction_schema to define exactly what you want back. If extraction fails on a specific file, the raw file is still available for download.
Deduplication
For recurring tasks, deduplication tells Deck to skip files that match one captured by a previous run. You choose which fields make a file “the same”. For a utility bill, that might be the account number plus the billing period start date. Files matching every chosen field against a prior capture are dropped, so you only ever process new documents. See the storage guide for configuration and field-picking guidance.Input vs. output files
Storage items carry apurpose: output for files the agent captures during a run, attachment for files you provide as task input, and extraction for files Deck processed via direct extraction. All three are returned together with a task run’s storage. File inputs are available on Enterprise plans. See providing files as input.
Retrieving files
url for download and an extraction field with the structured data. URLs are time-limited; refetch the item if one expires. You can also retrieve a single storage item by ID with GET /v2/storage/{storage_id}.
Retention
Retention period varies by plan. All files are deleted after 90 days.Deep dives
Storage & document extraction
Full integration walkthrough with extraction schemas and examples.