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 interacts with the TexAu Cloud platform, specifically allowing operations on various resources including Social Accounts. For the Social Account resource, the Set Limit operation updates the execution limit for a specified social account and operation ID. This is useful when you want to control or restrict how many times a particular automation or action can be executed on a social account.
Typical use cases include:
- Managing API usage limits per social account.
- Preventing overuse of certain automations by setting execution caps.
- Dynamically adjusting limits based on business rules or external triggers.
For example, if you have an automation that scrapes data from a social media account, you can set an execution limit to avoid hitting rate limits or violating terms of service.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the social account whose execution limit you want to set. |
| Operation ID | The identifier of the specific operation or automation for which the limit applies. |
| Execution Limit | A JSON object defining the new execution limit settings for the specified operation. |
Output
The node outputs the response from the TexAu API after setting the execution limit. The output is structured as JSON in the json field and typically contains confirmation details about the updated limit or any error messages returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the TexAu Cloud API.
- Needs an API key credential configured in n8n for authentication with TexAu.
- The base URL for requests is
https://v2-prod-api.texau.com. - The node uses HTTP PUT method to update the limit at endpoint
/api/v1/public/social-accounts/{AccountID}/limit.
Troubleshooting
- Invalid Account ID or Operation ID: If these identifiers are incorrect or do not exist, the API will likely return an error. Verify IDs before running the node.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- Malformed Execution Limit JSON: The execution limit must be a valid JSON object; otherwise, the request will fail.
- API Rate Limits: Setting limits too frequently or exceeding TexAu's API rate limits may cause temporary blocks.
- Network Issues: Connectivity problems can prevent successful API calls.
Common error messages might include:
- "Resource not found" – check the Account ID and Operation ID.
- "Unauthorized" – verify API credentials.
- "Bad Request" – ensure the execution limit JSON is correctly formatted.
Links and References
- TexAu API Documentation (general reference for API endpoints and usage)
- n8n Documentation (for configuring credentials and using HTTP request nodes)