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 "Run Automation" operation in this node allows users to trigger a specific automation on the TexAu platform. This is useful for automating workflows that involve social media accounts, platforms, or other connected services managed within TexAu. For example, you might use this node to start an automation that scrapes data from a social media platform, sends messages, or performs scheduled tasks.
Typical scenarios include:
- Running a predefined automation workflow on a selected platform.
- Triggering automations with custom inputs and parameters.
- Integrating TexAu automations into larger n8n workflows for enhanced automation capabilities.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the automation run instance (string). |
| Description | A description for the automation run (string), defaulting to "From N8N". |
| Platform Name or ID | Select or specify the platform where the automation will run (e.g., Twitter, LinkedIn). |
| Automation Name or ID | Select or specify the exact automation to run on the chosen platform. |
| Social Account Name or ID | Optionally select or specify the connected social account to use for running the automation. |
| Time Zone | Specify the time zone context for the automation run (string). |
| Inputs | JSON object containing input parameters to pass to the automation when it runs. |
Output
The node outputs JSON data representing the result of the automation run request. This typically includes details such as the status of the triggered automation, any identifiers returned by the TexAu API, and possibly metadata about the execution.
If the node supports binary data output, it would represent files or media related to the automation run, but based on the provided code and properties, the primary output is JSON structured data describing the automation run response.
Dependencies
- Requires an active TexAu API key credential configured in n8n to authenticate requests.
- Depends on TexAu's REST API endpoints, specifically those for platforms, automations, social accounts, and running automations.
- The node uses dynamic loading methods to populate options for platforms, automations, and social accounts via API calls.
- Network connectivity to
https://v2-prod-api.texau.comis necessary.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Selecting a platform without available automations may result in empty dropdowns.
- Providing malformed JSON in the "Inputs" property can cause request errors.
- Specifying incorrect IDs for platform, automation, or social account will lead to API errors.
Error Messages:
- Authentication errors usually indicate invalid or expired API keys; reconfigure credentials.
- "Not Found" errors suggest the specified automation or platform ID does not exist or is inaccessible.
- Validation errors may occur if required fields like "Automation Name or ID" are missing.
Resolutions:
- Verify API credentials and permissions.
- Use the dropdown selectors to ensure valid platform, automation, and account IDs.
- Validate JSON syntax before inputting into the "Inputs" field.
- Check network connectivity and API endpoint availability.