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 integrates with the TexAu cloud platform to run automations, specifically allowing users to trigger workflows by their ID. It is useful in scenarios where you want to programmatically start a predefined automation workflow hosted on TexAu, such as data scraping, social media automation, or lead generation tasks.
For example, if you have a workflow set up in TexAu that scrapes LinkedIn profiles based on certain criteria, this node can be used within an n8n workflow to trigger that scraping process dynamically by specifying the workflow's unique identifier.
Properties
| Name | Meaning |
|---|---|
| Workflow ID | The unique identifier of the TexAu workflow (automation) you want to run. This is a required string input. |
Output
The node outputs JSON data representing the response from the TexAu API after attempting to run the specified workflow. This typically includes details about the execution status or any returned data from the triggered automation.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating with the TexAu cloud platform.
- The node makes HTTP POST requests to the TexAu public API endpoint
https://v2-prod-api.texau.com/api/v1/public/run/{workflowId}, where{workflowId}is URL-encoded. - Proper configuration of the TexAu API credentials in n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or missing Workflow ID: Ensure the Workflow ID is correctly provided and corresponds to an existing workflow in TexAu.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Check connectivity to the TexAu API endpoint.
Error messages:
- Unauthorized or 401 errors indicate invalid or missing API credentials.
- 404 errors may mean the specified workflow ID does not exist.
- 400 errors could result from malformed requests, such as an empty Workflow ID.
Resolving these usually involves verifying the input parameters, checking API credentials, and ensuring the TexAu service is operational.
Links and References
- TexAu Official Website
- TexAu API Documentation (for detailed API usage and workflow management)