Usage Billing icon

Usage Billing

Process pricing and usage data to generate billing records

Actions3

Overview

This node is designed to import and process pricing data from CSV input within an n8n workflow. It is particularly useful when you have pricing information stored in CSV format that needs to be parsed, filtered, and transformed into structured JSON data for further automation or integration tasks.

Common scenarios include:

  • Importing product price lists from external systems delivered as CSV files.
  • Preparing pricing data for use in billing calculations or usage matching workflows.
  • Filtering specific columns from large CSV datasets to focus on relevant pricing fields.

For example, a user might upload a CSV file containing multiple columns of pricing details and want to extract only certain columns while automatically detecting the delimiter used in the CSV. This node facilitates that by parsing the CSV and outputting the filtered data as JSON objects.

Properties

Name Meaning
CSV Parsing Configuration Configuration related to how the CSV data should be parsed. Includes:
- Input Data Property Name: The name of the input field containing the raw CSV data (e.g., "csvdata", "data", or "rawCsv").
- Delimiter: Character used to separate values in the CSV. Options are: Auto-detect, Comma (,), Semicolon (;), Tab, Pipe (
Column Filtering Options Options to control which columns from the CSV are included in the output. Includes:
- Include All Columns: Boolean flag to include all columns from the CSV.
- Columns to Include: If not including all columns, a comma-separated list of column names to include.

Output

The node outputs an array of JSON objects representing the rows of the parsed CSV data after applying any column filtering specified. Each object corresponds to one row, with keys as column names and values as the respective cell content.

If binary data were involved, it would typically represent file contents or attachments, but this operation focuses solely on CSV text data parsing and JSON output.

Dependencies

  • No external API services or credentials are required for this operation.
  • The node relies on internal CSV parsing utilities provided by the bundled processing module.
  • No special environment variables or n8n configurations are necessary beyond standard node setup.

Troubleshooting

  • Incorrect Delimiter Detection: If the CSV delimiter is not correctly auto-detected, try explicitly setting the delimiter option to match your CSV format (e.g., comma, semicolon).
  • Missing or Incorrect Input Field: Ensure the input data property name matches exactly the field containing the CSV string; otherwise, the node will fail to find the data to parse.
  • Column Filtering Issues: When specifying columns to include, ensure the column names exactly match those in the CSV header row, including case sensitivity and whitespace.
  • Malformed CSV Data: If the CSV data is malformed or contains inconsistent rows, parsing errors may occur. Validate the CSV format before importing.

Common error messages will likely relate to missing input data or parsing failures, which can be resolved by verifying the input field name and CSV format.

Links and References

Discussion