TexAu icon

TexAu

Perform Opration on TexAu Cloud

Actions36

Overview

This node interacts with the TexAu Cloud platform to perform operations related to executions of workflows or automations. Specifically, the "Get Many" operation under the "Execution" resource retrieves multiple execution records from TexAu based on specified parameters such as pagination start index, limit on number of results, and optionally filtering by a workflow ID.

Common scenarios for this node include:

  • Fetching a list of recent executions for monitoring or auditing purposes.
  • Retrieving execution data in batches for reporting or further processing.
  • Filtering executions by a specific workflow to analyze its run history.

For example, a user might configure this node to get the first 50 executions starting from the 0th record, optionally filtered by a particular workflow ID, to display recent runs in a dashboard.

Properties

Name Meaning
Start The starting index (offset) for fetching executions. Must be 0 or greater.
Limit Maximum number of execution records to return. Minimum is 1.
Workflow ID Optional filter to retrieve executions belonging to a specific workflow identified by ID.

Output

The node outputs JSON data representing an array of execution objects retrieved from TexAu. Each object contains details about a single execution instance, such as its status, timestamps, associated workflow, and other metadata defined by the TexAu API.

If the node supports binary data output (not evident from the provided code), it would typically represent any files or attachments related to executions, but no explicit binary output handling is shown here.

Dependencies

  • Requires an API key credential for authenticating requests to the TexAu Cloud API.
  • The base URL for API requests is https://v2-prod-api.texau.com.
  • The node depends on internal helper functions (texAuApiRequest) to make HTTP requests to TexAu endpoints.
  • No additional external services are required beyond TexAu's API.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing an invalid workflow ID may result in empty results or errors.
    • Exceeding rate limits imposed by TexAu API could lead to request throttling.
    • Incorrect pagination parameters (e.g., negative start or zero limit) will likely cause validation errors.

  • Error messages:

    • Authentication errors usually indicate problems with the API key; verify that the correct credential is configured.
    • Validation errors on query parameters suggest checking the "Start" and "Limit" values.
    • Network or timeout errors require checking connectivity and TexAu service status.

Links and References

Discussion