Super CSV Crawler
Pricing
Pay per usage
Super CSV Crawler
Upload or remote CSV file parser, with ability to specify custom column names
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Dean Sofer
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
Apify actor that fetches CSV files from URLs and converts them to datasets. Supports custom field names instead of using the first row as headers.
Features
- Multiple CSV URLs – Fetch and parse multiple CSV files in one run
- Configurable separator – Use
,(comma),;(semicolon), or other delimiter - Custom field names – Optional array of column names; when provided, these are used as keys instead of the first row of the CSV
Input
| Field | Type | Description |
|---|---|---|
csvUrls | array | URLs of CSV files to fetch and convert to dataset |
separator | string | Column separator (default: ,). Often , or ; |
fieldNames | array | Optional. Column names used as object keys. When omitted, the first row of each CSV is treated as the header |
Behavior
- Without
fieldNames: The first row of each CSV is used as the header. Each subsequent row becomes an object with keys from that header row. - With
fieldNames: The provided array is used as headers. All rows (including the first) are treated as data, so the first row is no longer interpreted as column names.
Example
CSV with no header row (use fieldNames):
Alice,30,EngineerBob,25,Designer
Input: fieldNames: ["name", "age", "role"]
Output: [{ name: "Alice", age: "30", role: "Engineer" }, ...]
CSV with header row (omit fieldNames):
Name,Age,RoleAlice,30,EngineerBob,25,Designer
Input: omit fieldNames
Output: [{ Name: "Alice", Age: "30", Role: "Engineer" }, ...]
Schema Validation
The input schema (.actor/input_schema.json) is validated automatically on every push and pull request via the test GitHub Actions workflow.
Local Validation
Install the Apify CLI and run:
$npm test
This uses apify validate-schema, which checks these locations in priority order:
- Object in
.actor/actor.jsonunder the"input"key - JSON file path in
.actor/actor.json"input"key .actor/INPUT_SCHEMA.jsonINPUT_SCHEMA.json
You can also validate a custom path directly:
$npx -y apify-cli validate-schema path/to/INPUT_SCHEMA.json
Visual Schema Editor
For creating and editing input schemas visually, use the Apify Input Schema Editor.
