Actions8
- Execution Orchestrator Actions
- Datapool Actions
Overview
This node integrates with the BotCity orchestrator API, allowing users to manage executions of automation bots. Specifically, the "Stop Running Execution" operation under the "Execution Orchestrator" resource enables users to stop a currently running bot execution by specifying its execution ID. This is useful in scenarios where an automation process needs to be halted due to errors, changes in conditions, or manual intervention.
Practical examples include:
- Stopping a bot execution that is stuck or behaving unexpectedly.
- Canceling scheduled or triggered executions before they complete.
- Managing and controlling bot workflows dynamically from within n8n.
Properties
| Name | Meaning |
|---|---|
| Execution ID | ID of the execution to stop |
The "Execution ID" property is a required string input that identifies which running execution should be stopped.
Output
The node outputs JSON data representing the response from the BotCity orchestrator API after attempting to stop the specified execution. The exact structure depends on the API's response but typically includes status information about the cancellation request.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the BotCity orchestrator API.
- The node expects the base URL of the BotCity API to be configured in the credentials.
- Network access to the BotCity orchestrator endpoint is necessary.
Troubleshooting
- Invalid Execution ID: If the provided execution ID does not exist or is malformed, the API may return an error indicating the execution was not found. Verify the execution ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up.
- Network Issues: Connectivity problems to the BotCity API endpoint can cause timeouts or connection errors.
- Execution Already Stopped: Attempting to stop an execution that is not running may result in an error or no-op response.
To resolve these issues:
- Double-check the execution ID value.
- Confirm API credentials are valid and have sufficient permissions.
- Verify network connectivity.
- Check the current status of the execution before attempting to stop it.
Links and References
- BotCity Orchestrator API Documentation (example link; replace with actual if available)
- n8n documentation on Creating Custom Nodes