Actions36
- Automation Actions
- Execution Actions
- Notification Actions
- Platform Actions
- Prompt Actions
- Proxy Actions
- Result Actions
- Run Automation Actions
- Social Account Actions
- Workflow Actions
- Workspace Actions
Overview
This node interacts with the TexAu Cloud platform to retrieve specific result data based on an execution ID. The "Get Result" operation under the "Result" resource fetches detailed information about a particular execution result from TexAu's API. This is useful when you want to programmatically access the output or status of an automation run or workflow execution managed by TexAu.
Practical examples include:
- Fetching the outcome of a previously triggered automation to analyze or process its results.
- Integrating TexAu execution results into other workflows or systems for reporting or further action.
- Monitoring and logging execution outputs for auditing or debugging purposes.
Properties
| Name | Meaning |
|---|---|
| Execution ID | The unique identifier of the execution whose result you want to retrieve. This is required and must be provided as a string. |
Output
The node outputs JSON data representing the detailed result of the specified execution. The structure corresponds to the response returned by the TexAu API endpoint /api/v1/public/results/{ExecutionID}. This typically includes all relevant information about the execution's output, status, and metadata.
No binary data output is indicated in the source code or properties.
Dependencies
- Requires an active connection to the TexAu Cloud API.
- Needs an API authentication token credential configured in n8n to authorize requests to TexAu.
- The base URL for API requests is
https://v2-prod-api.texau.com. - The node uses HTTP GET requests to fetch data from TexAu's public results endpoint.
Troubleshooting
- Invalid or missing Execution ID: If the Execution ID is not provided or incorrect, the API will likely return an error indicating that the resource was not found. Ensure the Execution ID is correct and exists.
- Authentication errors: If the API key or authentication token is invalid or missing, the request will fail with an authorization error. Verify that the API credentials are correctly set up in n8n.
- Network issues: Connectivity problems can cause timeouts or failed requests. Check network access to
v2-prod-api.texau.com. - API rate limits: Excessive requests may lead to rate limiting by TexAu. Implement retry logic or reduce request frequency if needed.
Links and References
- TexAu Official Website
- TexAu API Documentation (general reference) (Note: exact API docs URL not provided in source)