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
The node integrates with the TexAu Cloud platform, enabling users to perform various operations on multiple resources such as accounts, automations, proxies, workflows, and more. Specifically, for the Proxy resource and the Buy Proxy operation, this node allows users to purchase a proxy by specifying a connected account ID. This is useful in scenarios where automated workflows require fresh or dedicated proxies for tasks like web scraping, social media automation, or managing multiple accounts without IP bans.
Practical example: A user wants to automate social media account management and needs to buy a proxy linked to a specific connected account to ensure anonymity and avoid rate limits. Using this node, they can programmatically buy the required proxy during their workflow execution.
Properties
| Name | Meaning |
|---|---|
| Connected Account ID | The identifier of the connected account for which the proxy will be purchased. Required. |
Output
The node outputs JSON data representing the result of the "Buy Proxy" operation. This typically includes details about the purchased proxy such as its IP address, port, authentication credentials, expiration time, and any other metadata returned by the TexAu API.
If the node supports binary data output (not explicitly shown in the provided code), it would likely represent proxy configuration files or certificates, but based on the static analysis, only JSON output is evident.
Dependencies
- Requires an active connection to the TexAu Cloud API.
- Needs an API key credential configured in n8n for authenticating requests to TexAu.
- The base URL for API requests is
https://v2-prod-api.texau.com. - The node depends on internal helper functions (
texAuApiRequest) to handle HTTP requests to the TexAu API.
Troubleshooting
Common issues:
- Invalid or missing Connected Account ID: Ensure the Connected Account ID is correctly provided and corresponds to an existing account in TexAu.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Check connectivity to the TexAu API endpoint.
Error messages:
- Authorization failures usually indicate invalid or expired API credentials.
- Validation errors may occur if required parameters are missing or malformed.
- Rate limiting errors from the API suggest too many requests in a short period; implement retry logic or delays.
Links and References
- TexAu Official Website
- TexAu API Documentation (for detailed API endpoints and parameters)