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 interacts with the TexAu Cloud platform, specifically allowing users to retrieve details about a Proxy resource by its unique identifier. The "Get" operation under the "Proxy" resource fetches information about a specific proxy configured or available in the TexAu system.
Common scenarios where this node is beneficial include:
- Retrieving configuration details of a particular proxy for auditing or validation.
- Using proxy details dynamically within an automation workflow to route requests through specific proxies.
- Monitoring or managing proxies programmatically as part of larger automation tasks.
For example, a user might input a Proxy ID to get its IP address, port, and status, then use that data to configure subsequent HTTP requests in their workflow.
Properties
| Name | Meaning |
|---|---|
| Proxy ID | The unique identifier of the proxy to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the details of the requested proxy. The structure corresponds to the proxy's properties as returned by the TexAu API endpoint /api/v1/public/proxies/{{Proxy ID}}. Typical fields may include proxy IP, port, type, authentication details (if any), and status.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the TexAu Cloud API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for API requests is
https://v2-prod-api.texau.com. - The node uses the GET HTTP method to fetch proxy details from the endpoint
/api/v1/public/proxies/{encoded Proxy ID}.
Troubleshooting
- Invalid Proxy ID: If the provided Proxy ID does not exist or is malformed, the API will likely return a 404 error or similar. Verify the Proxy ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up in n8n credentials.
- Network Issues: Connectivity problems to the TexAu API endpoint can cause timeouts or request failures. Check network access and proxy settings if applicable.
- Encoding Issues: The Proxy ID is URL-encoded before sending; ensure it does not contain unsupported characters or whitespace.
Links and References
- TexAu API Documentation (for detailed API endpoints and proxy resource schema)
- n8n Documentation (for general usage of HTTP request nodes and credential setup)