Data Table Node Benchmark Workflow¶
This workflow provides a webhook endpoint for benchmarking n8n's Data Table node performance by accepting bulk data submissions and inserting them into a specified data table with structured column mapping.
Purpose¶
No business context provided yet — add a context.md to enrich this documentation.
How It Works¶
- Webhook receives data: A POST request is made to the
/data-table-node-benchmarkendpoint containing a data table ID and an array of items to insert - Data extraction: The workflow extracts the items array from the request body
- Item processing: Each item in the array is split into individual records for processing
- Data table insertion: Each record is inserted into the specified data table with mapped columns (firstName, age, birthDate, isActive)
- Response: All processed items are returned to the caller as confirmation
Workflow Diagram¶
graph TD
A[Webhook] --> B[Split Out]
B --> C[Insert row]
C --> D[Respond to Webhook]
Trigger¶
Webhook Trigger
- Method: POST
- Path: /data-table-node-benchmark
- Response Mode: Response Node (waits for workflow completion before responding)
Nodes Used¶
| Node Type | Node Name | Purpose |
|---|---|---|
| Webhook | Webhook | Receives HTTP POST requests with data table ID and items array |
| Split Out | Split Out | Splits the items array into individual records for processing |
| Data Table | Insert row | Inserts each record into the specified data table with column mapping |
| Respond to Webhook | Respond to Webhook | Returns all processed items as the HTTP response |
External Services & Credentials Required¶
n8n Data Table - Requires access to n8n's internal data table functionality - No external credentials needed (uses n8n's built-in data table system)
Environment Variables¶
No environment variables are required for this workflow.
Data Flow¶
Input (Webhook Body):
1 2 3 4 5 6 7 8 9 10 11 | |
Output (Response):
1 2 3 4 5 6 7 8 | |
Column Schema:
- firstName: String type
- age: Number type
- birthDate: DateTime type
- isActive: Boolean type
- empty: String type (defined but not mapped)
Error Handling¶
This workflow does not implement explicit error handling. Errors will bubble up from: - Invalid data table ID references - Data type conversion failures during insertion - Network connectivity issues with the data table service
Known Limitations¶
- The workflow processes items sequentially, which may impact performance with large datasets
- No validation is performed on input data before insertion
- The
emptycolumn is defined in the schema but not populated - No duplicate detection or conflict resolution
Related Workflows¶
No related workflows identified.
Setup Instructions¶
- Import the workflow into your n8n instance
- Activate the workflow to enable the webhook endpoint
- Create a data table in n8n with the following columns:
firstName(String)age(Number)birthDate(DateTime)isActive(Boolean)empty(String, optional)
- Test the endpoint by sending a POST request to:
With the required JSON payload structure
1https://your-n8n-instance.com/webhook/data-table-node-benchmark - Monitor execution through n8n's execution history to verify data insertion
Note: The workflow expects the data table to already exist. The dataTableId in the request payload should reference a valid, accessible data table in your n8n instance.