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 to perform operations related to social accounts. Specifically, the "Reset Proxy Location" operation allows users to reset the proxy location associated with a given social account by its Account ID. This can be useful in scenarios where the proxy settings for a social media or other online account need to be refreshed or changed to avoid IP bans, improve connection speed, or comply with regional restrictions.
Practical examples include:
- Resetting the proxy location of a social media account before running automation tasks to ensure requests come from a new IP.
- Managing multiple social accounts and programmatically resetting their proxies to maintain anonymity or bypass geo-blocks.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the social account whose proxy location you want to reset. This is a required string input. |
Output
The node outputs JSON data representing the response from the TexAu API after attempting to reset the proxy location for the specified social account. The exact structure depends on the API response but typically includes status information about the reset operation.
No binary data output is indicated.
Dependencies
- Requires an active TexAu Cloud API key credential configured in n8n to authenticate API requests.
- The node makes HTTP GET requests to the TexAu API endpoint:
https://v2-prod-api.texau.com/api/v1/public/social-accounts/{AccountID}/reset-proxy. - No additional external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid or missing Account ID: Ensure the Account ID provided corresponds to an existing social account in TexAu.
- Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
- Network or API downtime: Check connectivity and TexAu service status if requests fail.
Error messages:
- Unauthorized or 401 errors indicate invalid or expired API credentials.
- 404 errors may mean the specified Account ID does not exist.
- Rate limiting or 429 errors suggest too many requests; consider adding delays or retries.
Resolving these usually involves verifying inputs, credentials, and network conditions.
Links and References
- TexAu Official Website
- TexAu API Documentation (for detailed API endpoints and responses)