Files
Upload and manage CSV/XLSX files for data workflows
Files are uploaded data sources used in ingest and signal workflows. Upload your company or contact lists as CSV or Excel files, then reference them in tasks to enrich the data or monitor for signals.
File Response Structure
When you upload a file, the API returns metadata about the file and its contents.
FileUploadResponse
Response Fields
| Field | Type | Description |
|---|---|---|
file_id | string | Unique identifier for the file |
name | string | Original filename |
s3_uri | string | Internal storage location |
content_type | string | MIME type (e.g., text/csv) |
size_bytes | integer | File size in bytes |
csv_metadata | object | Parsed CSV information |
processing_status | string | Current processing state |
original_file_type | string | Original format if converted (e.g., xlsx) |
CSV Metadata
The csv_metadata object contains information extracted from the CSV:
| Field | Type | Description |
|---|---|---|
row_count | integer | Number of data rows (excluding header) |
columns | array | Column names from the header row |
preview_rows | array | First few rows as key-value objects |
encoding | string | Detected character encoding |
Use csv_metadata to verify your file was parsed correctly before creating tasks.
Processing Status
Files go through a processing pipeline after upload. The processing_status field indicates the current state.
Status Lifecycle
| Status | Description |
|---|---|
pending | File uploaded, waiting to be processed |
processing | File is being parsed and validated |
completed | File ready for use in workflows |
failed | Processing error occurred |
Wait for Processing
Only use files with processing_status: "completed" in your tasks. Using a file before processing completes will cause task failures.
Checking Processing Status
For large files, poll the file endpoint until processing completes:
Supported File Types
| Format | Extensions | Notes |
|---|---|---|
| CSV | .csv | UTF-8 encoding recommended |
| Excel | .xlsx, .xls | First sheet only, converted to CSV |
Excel Conversion
Excel files are automatically converted to CSV format using the first sheet. The original_file_type field will be set to xlsx or xls to indicate conversion occurred.
Using Files in Workflows
Files are referenced by file_id in task configurations. Two workflow types use files:
Ingest Tasks
Import and enrich entities from a CSV file:
See CSV Import for the complete workflow.
Signal CSV Tasks
Monitor entities from a CSV file for signals:
See Topic Monitoring for signal configuration details.
CSV Format Requirements
Required
- Header row — First row must contain column names
- Primary column — At least one column with entity identifiers (company names or person names)
- UTF-8 encoding — Ensure proper character encoding
Recommended Columns
For company data:
| Column | Purpose |
|---|---|
| Company name | Required as primary identifier |
| Website/domain | Improves entity matching accuracy |
| Industry | Additional context for enrichment |
| Location | Geographic information |
For person data:
| Column | Purpose |
|---|---|
| Full name | Required as primary identifier |
| Company name | Associates person with company |
| Job title | Role information |
| Contact information | |
| LinkedIn URL | Profile matching |
Example CSV
Complete Example
Here's a workflow for uploading a file and using it in an ingest task:
Next Steps
- CSV Import — Complete ingest workflow
- Bulk Enrichment — Enriching large datasets
- Topic Monitoring — Signal monitoring including CSV-based signals
- Tasks — Task configuration reference