Documentation Index
Fetch the complete documentation index at: https://docs.deck.co/llms.txt
Use this file to discover all available pages before exploring further.
Available on Enterprise 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. Each item includes 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 |
deduplication | Skip files already captured from previous runs for the same task and credential |
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
When enabled, Deck compares files against previous runs for the same task and credential using file hashes. Duplicates are skipped. This is useful for recurring tasks like daily statement fetches where you only want new documents.Retrieving files
extraction field with the structured data. To get a signed download URL, retrieve the individual 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.