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, specifically providing operations on various resources including proxies. The "Get Many" operation under the "Proxy" resource allows users to retrieve a list of proxy entries from their TexAu account. This is useful for scenarios where you need to manage or audit multiple proxies, such as fetching available proxies for automation tasks or monitoring proxy usage.
Practical examples:
- Fetching a paginated list of proxies to display in a dashboard.
- Retrieving proxies to select one for use in subsequent automation workflows.
- Auditing proxy configurations by exporting proxy details.
Properties
| Name | Meaning |
|---|---|
| Start | The starting index number for the list of proxies to return. Must be 0 or greater. |
| Limit | The maximum number of proxy results to return. Must be at least 1. Default is 50. |
These properties control pagination of the proxy list returned by the node.
Output
The node outputs JSON data containing an array of proxy objects retrieved from the TexAu API. Each object represents a proxy with its associated details (such as IP address, port, and other metadata as defined by the TexAu Proxy resource schema).
If the node supports binary data output (not indicated here), it would typically represent files or attachments related to proxies, but this node focuses on JSON data.
Dependencies
- Requires an active TexAu API key credential configured in n8n to authenticate requests.
- Connects to the TexAu Cloud API endpoint at
https://v2-prod-api.texau.com. - Uses the internal helper function to make authenticated HTTP GET requests to the
/proxiesendpoint with query parameters for pagination.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing a negative number for "Start" or less than 1 for "Limit" will likely result in validation errors.
- Network connectivity issues can prevent access to the TexAu API.
Error messages:
- Authentication errors: Ensure your API key credential is correctly set up and has necessary permissions.
- Validation errors on input properties: Check that "Start" is zero or positive and "Limit" is at least 1.
- API rate limits or server errors: Retry after some time or check TexAu service status.
Links and References
- TexAu Official Website
- TexAu API Documentation (for detailed API endpoints and proxy resource schema)
