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 to manage proxies. Specifically, the "Update a Proxy" operation allows users to modify an existing proxy's details by specifying its unique identifier and new configuration data. This is useful in scenarios where proxy settings need to be updated dynamically, such as rotating proxies for web scraping tasks or updating credentials for authentication.
Practical examples include:
- Updating the name of a proxy to better reflect its purpose.
- Changing the credentials associated with a proxy to maintain access.
- Automating proxy management workflows within larger automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Proxy ID | The unique identifier of the proxy to update. Required to specify which proxy to modify. |
| The Proxy Name | The new name to assign to the proxy. Helps identify the proxy in the system. |
| Credentials | The updated credentials for the proxy, provided as a JSON object. Used for authentication. |
Output
The node outputs JSON data representing the updated proxy resource as returned from the TexAu API after the update operation. This typically includes fields such as the proxy's ID, name, credentials (likely masked or omitted), status, and other metadata reflecting the current state of the proxy.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the TexAu Cloud API.
- Needs an API key credential configured in n8n to authenticate requests.
- The base URL for API requests is
https://v2-prod-api.texau.com. - The node uses HTTP PUT method to send updates to the endpoint
/api/v1/public/proxies/{{Proxy ID}}.
Troubleshooting
- Invalid Proxy ID: If the specified Proxy ID does not exist, the API will likely return a 404 error. Verify the Proxy ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up.
- Malformed Credentials JSON: The credentials property must be valid JSON. Invalid JSON syntax will cause request failures.
- Required Fields Missing: Both Proxy ID, Proxy Name, and Credentials are required. Omitting any will result in errors.
- API Rate Limits: Frequent updates may hit API rate limits; handle such errors by implementing retries or backoff strategies.
Links and References
- TexAu API Documentation (general reference for API endpoints and usage)
- n8n Documentation (for configuring credentials and using HTTP request nodes)