Custom CSV Integration
Not using vAuto, HomeNet, or Elead? No problem. Carfluence supports any CSV or pipe-delimited file format through the custom integration type.
When to Use Custom CSV
- •Your DMS exports data in a proprietary CSV format
- •You have a spreadsheet-based inventory system
- •You want to import data from a source Carfluence doesn't have a built-in connector for
- •You're migrating from another platform
Step 1: Create the Integration
bash
POST /api/v1/integrations
{
"dealershipId": "your-dealer-uuid",
"type": "custom",
"name": "My Custom Feed"
}Step 2: Upload a Sample File
Upload a sample CSV/TSV file to the SFTP folder. Carfluence will:
- 1Auto-detect the delimiter (comma, pipe, tab)
- 2Parse the header row
- 3Generate a field mapping preview
Step 3: Configure Field Mappings
Use the dashboard or API to map your fields:
bash
PATCH /api/v1/mappings/:integrationId
{
"mappings": {
"Vehicle_VIN_Number": "vin",
"Stk_Num": "stock_number",
"Yr": "year",
"Manufacturer": "make",
"Model_Name": "model",
"Asking_Price": "price",
"Odometer": "mileage",
"Color_Ext": "exterior_color",
"Color_Int": "interior_color",
"Vehicle_Type": "body_style",
"New_Used": "condition"
}
}You can preview mappings before committing:
bash
GET /api/v1/mappings/:integrationId/previewThis shows you how your raw data will be normalized, so you can verify everything looks correct.
Step 4: Set Up Automated Uploads
Configure your source system to push files to the SFTP folder on a schedule. Carfluence monitors the folder and processes new files automatically.
Required Fields
At minimum, each record must have:
- •VIN (17-character vehicle identification number) — this is the primary key
- •At least one other field (make, model, price, etc.)
Supported Formats
| Format | Delimiter | Extension | |
|---|---|---|---|
| CSV | Comma | .csv | |
| TSV | Tab | .tsv, .txt | |
| Pipe-delimited | Pipe (` | `) | .txt, .csv |
Carfluence auto-detects the delimiter. Files must include a header row.