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 provides an interface to update a Social Account resource on the TexAu platform via its API. It allows users to modify details of an existing social account such as its name, associated proxy, and credentials. This is useful in automation workflows where social account configurations need to be programmatically updated without manual intervention.
Typical use cases include:
- Changing the display name of a social media account linked to TexAu.
- Updating or assigning a proxy server to a social account for routing requests.
- Modifying authentication credentials or tokens associated with the social account.
For example, if you manage multiple social accounts and proxies, this node can automate updating their settings when proxies expire or credentials change.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the social account to update. Required for specifying which account to modify. |
| Name | The new name to assign to the social account. Optional; if provided, updates the account's display name. |
| Proxy ID | The identifier of the proxy to associate with the social account. Optional; used to route traffic through a specific proxy. |
| Credentials | JSON object containing updated credentials or authentication details for the social account. Optional; used to refresh or change login/authentication data. |
Output
The node outputs the JSON response from the TexAu API after performing the update operation on the social account. This typically includes the updated social account details such as its ID, name, proxy association, and credential metadata.
If the API supports binary data related to the social account (e.g., profile images), it would be included accordingly, but based on the static code analysis, the output primarily consists of JSON data representing the updated resource state.
Dependencies
- Requires an active API key credential for TexAu to authenticate requests.
- The node sends HTTP PUT requests to the endpoint
/api/v1/public/social-accounts/{{Account ID}}on the TexAu API base URLhttps://v2-prod-api.texau.com. - Proper network access to TexAu's API endpoints is necessary.
- No additional external dependencies beyond the TexAu API and n8n's HTTP request capabilities.
Troubleshooting
- Invalid Account ID: If the provided Account ID does not exist or is malformed, the API will likely return a 404 or validation error. Verify the Account ID is correct and exists.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is configured correctly in n8n.
- Invalid JSON in Credentials: If the Credentials property contains malformed JSON, the API may reject the request. Validate JSON formatting before sending.
- Proxy ID Issues: Assigning a Proxy ID that does not exist or is not authorized may result in errors. Confirm the proxy exists and is accessible.
- Empty Required Fields: The Account ID is required; omitting it will prevent the request from being sent properly.
Common error messages will come from the TexAu API and should be interpreted according to their documentation, usually indicating issues with authorization, resource existence, or data validation.
Links and References
- TexAu API Documentation (general reference for API endpoints and payloads)
- n8n HTTP Request Node documentation for understanding how routing and request defaults work
- TexAu official website: https://texau.com