Overview
The List Dataset Nodes endpoint allows you to retrieve information about dataset nodes within a flow. Dataset nodes are components that connect document sources to your flow pipeline, containing configuration details about which files are included and how they’re processed.- Method:
GET - URL:
https://{flow_name}.flows.graphorlm.com/datasets - Authentication: Required (API Token)
Authentication
All requests must include a valid API token in the Authorization header:Learn how to generate API tokens in the API Tokens guide.
Request Format
Headers
| Header | Value | Required |
|---|---|---|
Authorization | Bearer YOUR_API_TOKEN | Yes |
Parameters
No query parameters are required for this endpoint.Example Request
Response Format
Success Response (200 OK)
The response contains an array of dataset node objects:Response Structure
Each dataset node in the array contains:| Field | Type | Description |
|---|---|---|
id | string | Unique identifier for the dataset node |
type | string | Node type (always “dataset” for dataset nodes) |
position | object | Position coordinates in the flow canvas |
style | object | Visual styling properties (height, width) |
data | object | Dataset node configuration and results |
Position Object
| Field | Type | Description |
|---|---|---|
x | number | X coordinate position in the flow canvas |
y | number | Y coordinate position in the flow canvas |
Style Object
| Field | Type | Description |
|---|---|---|
height | integer | Height of the node in pixels |
width | integer | Width of the node in pixels |
Data Object
| Field | Type | Description |
|---|---|---|
name | string | Display name of the dataset node |
config | object | Node configuration including file list |
result | object | Processing results and metadata (optional) |
Config Object
| Field | Type | Description |
|---|---|---|
files | array | List of file names included in this dataset node |
Result Object (Optional)
| Field | Type | Description |
|---|---|---|
updated | boolean | Whether the node has been processed with current configuration |
total_documents | integer | Number of documents processed (if available) |
total_chunks | integer | Number of text chunks generated (if available) |
Code Examples
JavaScript/Node.js
Python
cURL
Error Responses
Common Error Codes
| Status Code | Description | Example Response |
|---|---|---|
| 401 | Unauthorized - Invalid or missing API token | {"detail": "Invalid authentication credentials"} |
| 404 | Not Found - Flow not found | {"detail": "Flow not found"} |
| 500 | Internal Server Error - Server error | {"detail": "Failed to retrieve dataset nodes"} |
Error Response Format
Example Error Responses
Invalid API Token
Flow Not Found
Server Error
Use Cases
Dataset Node Management
Use this endpoint to:- Configuration Overview: See which files are configured in each dataset node
- Status Monitoring: Check if dataset nodes need updates after file changes
- Flow Analysis: Understand the data sources used in your flow
- Debugging: Identify configuration issues in dataset nodes
Integration Examples
Dataset Health Checker
Configuration Audit Tool
Best Practices
Monitoring and Management
- Regular Health Checks: Monitor dataset nodes to ensure they’re configured properly
- Configuration Validation: Verify that all referenced files exist in your sources
- Update Tracking: Keep track of which nodes need updates after configuration changes
- Documentation: Maintain clear naming conventions for dataset nodes
Performance Optimization
- Efficient Polling: Don’t poll this endpoint too frequently; cache results when possible
- Batch Operations: Group multiple dataset node operations together
- Resource Monitoring: Monitor the impact of dataset size on flow performance
Error Handling
- Network Resilience: Implement retry logic for network failures
- Graceful Degradation: Handle cases where flows have no dataset nodes
- Detailed Logging: Log dataset node configurations for debugging
Troubleshooting
Flow Not Found Error
Flow Not Found Error
Solution: Verify that:
- The flow name in the URL is correct and matches exactly
- The flow exists in your project
- Your API token has access to the correct project
- The flow has been created and saved properly
Empty Dataset Nodes Array
Empty Dataset Nodes Array
Solution: If no dataset nodes are returned:
- Verify the flow contains dataset components
- Check that dataset nodes have been added to the flow
- Ensure the flow has been saved after adding dataset nodes
- Confirm you’re checking the correct flow
Missing Files in Configuration
Missing Files in Configuration
Solution: If dataset nodes reference non-existent files:
- Use the List Sources endpoint to verify file availability
- Upload missing files using the Upload Source endpoint
- Update dataset node configuration to remove references to deleted files
Outdated Node Status
Outdated Node Status
Solution: If nodes show
"updated": false:- The node configuration has changed since last processing
- Use the Update Dataset endpoint to apply changes
- Re-run the flow after updating configurations
- This is normal after adding/removing files from the dataset
Connection Issues
Connection Issues
Solution: For connectivity problems:
- Check your internet connection
- Verify the flow URL is accessible
- Ensure your firewall allows HTTPS traffic to *.flows.graphorlm.com
- Try accessing the endpoint from a different network
Next Steps
After retrieving dataset node information, you might want to:Update Dataset
Modify dataset node configurations and file selections
List Sources
View all available source files for configuration
Run Flow
Execute your flow with the configured dataset nodes
Flow Overview
Learn about all available flow management endpoints

