Overview
This node integrates with the Automation Anywhere API, specifically focusing on managing executions within the Execution Orchestrator resource. The "Pause" operation allows users to pause a running execution by specifying its execution ID. This is useful in scenarios where an automation process needs to be temporarily halted without terminating it, such as waiting for external input or system readiness before continuing.
Practical examples include:
- Pausing a robotic process automation (RPA) task when a dependent system is down.
- Temporarily halting workflows during maintenance windows.
- Controlling execution flow dynamically based on business logic.
Properties
| Name | Meaning |
|---|---|
| Execution ID | ID of the execution to be paused. This must be provided as a string identifying the specific execution instance. |
Output
The node outputs JSON data representing the response from the Automation Anywhere API after attempting to pause the specified execution. The exact structure depends on the API's response but typically includes status information about the pause request.
If the node supports binary data output, it is not indicated in the provided code and thus can be assumed absent for this operation.
Dependencies
- Requires an active connection to the Automation Anywhere API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for the API is taken from the credential configuration and sanitized to remove trailing slashes.
- Uses internal helper functions to send HTTP POST requests to the Automation Anywhere endpoints.
Troubleshooting
- Invalid Execution ID: If the provided execution ID does not exist or is malformed, the API will likely return an error. Verify the execution ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up in n8n.
- Network Issues: Connectivity problems to the Automation Anywhere API endpoint will prevent the pause operation from succeeding.
- API Rate Limits: Excessive requests may trigger rate limiting; handle retries accordingly.
- Operation Not Allowed: Attempting to pause an execution that is already completed or stopped might result in an error.
Common error messages will originate from the Automation Anywhere API and should be interpreted according to their documentation.