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, enabling users to perform various operations on different resources managed by TexAu. Specifically, for the Proxy resource and the Add a Proxy operation, the node allows users to create a new proxy entry in their TexAu account by specifying the proxy's name and credentials.
Common scenarios where this node is beneficial include automating the management of proxies used in web scraping, automation workflows, or social media account management where rotating or adding proxies dynamically is required. For example, a user might add a new proxy to their TexAu setup before running an automation that requires IP rotation to avoid rate limits or bans.
Properties
| Name | Meaning |
|---|---|
| The Proxy Name | The display name for the new proxy being added. This identifies the proxy within TexAu. |
| Credentials | The authentication details or configuration for the proxy, provided as JSON data. |
Output
The node outputs JSON data representing the response from the TexAu API after attempting to add the proxy. This typically includes details about the newly created proxy such as its ID, name, status, and any other metadata returned by the API.
If the node supports binary data output (not indicated in the provided code), it would represent associated files or certificates related to the proxy, but no such indication is present here.
Dependencies
- Requires an active connection to the TexAu Cloud API.
- Users must provide valid API authentication credentials (an API key or token) configured in n8n to authorize requests.
- The node uses the base URL
https://v2-prod-api.texau.comfor all API calls. - No additional external dependencies are indicated.
Troubleshooting
- Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrectly formatted proxy credentials JSON may result in API errors.
- Network connectivity issues can prevent communication with the TexAu API.
- Error Messages:
- Authentication errors typically indicate invalid or expired API tokens; reconfigure credentials.
- Validation errors from the API may indicate missing required fields like the proxy name or malformed credentials.
- Timeout or network errors suggest checking internet connectivity or TexAu service status.
Links and References
- TexAu Official Website
- TexAu API Documentation (for detailed API usage and proxy management)
- n8n Documentation on Creating Custom Nodes