Actions8
- Execution Orchestrator Actions
- Datapool Actions
Overview
This node integrates with the BotCity orchestrator API, specifically managing Datapools. The "List Datapool Items" operation retrieves items from a specified Datapool. This is useful for workflows that need to fetch and process data stored in BotCity Datapools, such as automating tasks based on dynamic datasets or iterating over collections of input values.
Practical examples include:
- Fetching user credentials or configuration parameters stored in a Datapool to use in automation scripts.
- Retrieving lists of targets or inputs for batch processing in robotic process automation (RPA) scenarios.
Properties
| Name | Meaning |
|---|---|
| Datapool Name or ID | Select the Datapool by name from a dropdown list or specify its ID using an expression. This identifies which Datapool's items will be listed. |
Output
The node outputs JSON data representing the items retrieved from the specified Datapool. Each item corresponds to an entry within the Datapool, typically structured as key-value pairs or objects depending on how the Datapool is defined.
If the Datapool contains binary data, it would be included accordingly, but this node primarily focuses on JSON data output.
Dependencies
- Requires connection to the BotCity orchestrator API.
- Needs an API authentication credential configured in n8n to authorize requests.
- The base URL for the API is taken from the credential configuration.
- The node uses internal methods to load options dynamically, such as fetching available Datapools.
Troubleshooting
Common issues:
- Incorrect or missing API credentials can cause authentication failures.
- Specifying a non-existent Datapool name or ID will result in errors or empty results.
- Network connectivity problems may prevent communication with the BotCity API.
Error messages:
- Authentication errors usually indicate invalid or expired API tokens; verify and update credentials.
- "Datapool not found" errors suggest the provided Datapool identifier is incorrect; double-check the name or ID.
- Timeout or connection errors require checking network access and API endpoint availability.
Links and References
- BotCity Orchestrator API Documentation (example placeholder link)
- n8n Expressions Documentation – for using expressions to specify Datapool IDs dynamically