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 integrates with the TexAu Cloud platform, allowing users to perform various operations on multiple resources such as accounts, automations, workflows, and more. Specifically, for the Workflow resource with the Get Many operation, it retrieves a list of workflows from the TexAu service.
Typical use cases include:
- Fetching multiple workflows to display or process them in bulk.
- Automating workflow management by retrieving workflows programmatically.
- Integrating TexAu workflows into larger automation pipelines within n8n.
For example, a user might want to get all workflows starting from a certain index with a limit on how many to retrieve, enabling pagination through large sets of workflows.
Properties
Name | Meaning |
---|---|
Start | The starting index number from which to begin fetching workflows (minimum 0). |
Limit | The maximum number of workflow results to return (minimum 1). |
These properties correspond to query parameters sent to the TexAu API to control pagination of the workflows list.
Output
The node outputs JSON data representing the retrieved workflows. Each item in the output corresponds to a workflow object returned by the TexAu API. The exact structure depends on the API response but typically includes details like workflow ID, name, status, and other metadata.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating with the TexAu Cloud API.
- The base URL for requests is
https://v2-prod-api.texau.com
. - The node uses internal helper functions to make authenticated HTTP requests to TexAu endpoints.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing invalid values for
Start
orLimit
(e.g., negative numbers) may result in errors or no data returned. - Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate incorrect or expired API keys; verify and update credentials.
- Validation errors on input parameters suggest checking that
Start
is ≥ 0 andLimit
is ≥ 1. - API rate limits or server errors from TexAu should be handled by retrying after some delay.
Links and References
- TexAu Official Website
- TexAu API Documentation (for detailed API endpoint info)
- n8n documentation on creating custom nodes