Actions8
- Execution Orchestrator Actions
- Datapool Actions
Overview
The node integrates with the BotCity orchestrator API, specifically focusing on managing executions within the orchestration system. The "Get Many" operation under the "Execution Orchestrator" resource fetches multiple execution records from the orchestrator based on a relative number of days. This is useful for retrieving recent execution data to monitor, analyze, or report on automated processes managed by BotCity.
Practical examples include:
- Fetching all executions from the past week to review success and failure rates.
- Gathering execution logs for a specific timeframe to diagnose issues or optimize workflows.
- Integrating execution data into dashboards or other monitoring tools.
Properties
| Name | Meaning |
|---|---|
| Days | Relative number of days to fetch execution data for. For example, setting this to 7 retrieves executions from the last 7 days. |
Output
The node outputs JSON data representing a list of execution records retrieved from the BotCity orchestrator. Each item in the output corresponds to an execution instance with details such as status, timestamps, and possibly other metadata related to the execution lifecycle.
If the node supports binary data output (not evident from the provided code), it would typically represent files or logs associated with executions, but no explicit binary output handling is shown here.
Dependencies
- Requires an API key credential for authenticating with the BotCity orchestrator API.
- The base URL for the API is configured via credentials and sanitized to remove trailing slashes.
- The node depends on the BotCity orchestrator service being accessible and properly configured.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing an invalid number for "Days" (e.g., negative numbers) might result in errors or empty responses.
- Network connectivity issues to the BotCity orchestrator endpoint can prevent data retrieval.
Error Messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- HTTP errors like 404 or 500 suggest issues with the API endpoint or server; check the base URL and service status.
- Empty results may mean no executions exist for the specified timeframe; try increasing the "Days" value.
Links and References
- BotCity Orchestrator API Documentation (example placeholder link)
- n8n documentation on Creating Custom Nodes