Skip to main content

​
What It Does

  • Imports CSV Data: Load structured data from a locally uploaded CSV file.
  • Targeted Column Selection: All columns are included by default; choose specific ones if needed.
  • Trigger-Friendly: Use it to start a play or drop it mid-play as a flat-file ingest step.
  • Column Name Safety: Handles duplicate column names automatically to prevent issues downstream.

​
🏁 Getting Started

CSV Read node configuration screenshot
1

Add the Node

Add the CSV Read node to your play. It works as a trigger node (no upstream input) or can be inserted mid-play to bring in CSV data.
2

Upload Your File

Upload a local .csv file from your device.
3

(Optional) Select Columns

All columns are selected by default. Use the dropdown to include only the ones you need.
4

Run the Node

Click Run. Once it executes, click the file icon on the node to preview your data.
This node doesn’t require upstream inputs — use it to kick off a play or inject data mid-play from a CSV file.
When the node is toggled to purple, it will preview only the first 5 rows. Switch to green to load the entire file into your play.

​
Inputs

🚀 This is a trigger node — no inputs are required from upstream nodes.

​
Output

After execution, your selected CSV data is available for downstream nodes.
  • Outputs all columns by default (or just the selected ones)
  • Data can be previewed from the node’s output panel
  • Duplicate column names are automatically renamed (e.g., email, email_1, email_2) to maintain integrity
CSV Read node output example
📝 The first row of your CSV must contain column headers. If not, the first row will be treated as headers — which may cause issues downstream.

​
How It Works

  1. Validates the file format and confirms it’s a readable CSV
  2. Applies column filtering if selected
  3. Reads and loads your data into the play
  4. Auto-renames duplicate columns as needed to avoid conflicts
  5. Displays the processed data in the output panel

​
✨ Pro Tips

Start with only what you need: Selecting key columns keeps your play focused and reduces clutter as your data moves through more nodes.
Preview before proceeding: After upload and execution, click the file icon to inspect your data before passing it downstream.
Avoid duplicate column names when possible — but if they exist, we’ll rename them for you (e.g., name, name_1) to keep everything running smoothly.

​
⚠️ Important Considerations

CSV must include headers. If not, the first row will be used as headers, which may lead to data mapping issues later in your play.
Duplicate headers are renamed. If your CSV includes duplicate column names, they’ll be renamed automatically to avoid conflicts. (e.g., email, email_1)

​
🛠 Troubleshooting & Gotchas

SymptomCauseQuick Fix
No data shown in previewFile is empty or improperly formattedOpen the file and check contents before uploading
Missing or extra columnsColumn selection mismatchReopen the node and adjust your column choices
Unexpected column namesDuplicate headers were renamedPreview output to see updated field names (e.g., email_1)

​
📝 FAQ

Yes. By default, all columns are included, but you can select just the ones you need from the dropdown.
The first row will be treated as headers, which may lead to issues in downstream nodes that rely on proper column names.
Yes. After uploading and running the node, click the file icon on the node card to view a preview of the data.

​
💼 RevOps Use Cases

ScenarioWhy Use CSV Read
SDR call logsBring in call outcomes and metadata for routing logic
Pipeline auditIngest CRM exports for deal review
Account planningImport segmented account lists
Attribution modelingAnalyze touchpoint exports in sequence

Start your RevOps plays the smart way — bring in your CSVs, select only what matters, and hit the ground running. 📊⚡