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, allowing users to perform various operations on different TexAu resources. Specifically, for the Workflow - Get operation, it retrieves detailed information about a specific workflow by its unique identifier. This is useful when you want to fetch and use workflow details within an automation, such as inspecting workflow configurations or statuses before proceeding with further steps.
Practical examples include:
- Fetching a workflow's metadata to display or log it.
- Using workflow details to conditionally trigger other automations.
- Integrating TexAu workflows into larger automation pipelines in n8n.
Properties
| Name | Meaning |
|---|---|
| Workflow ID | The unique identifier of the workflow to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the retrieved workflow object from TexAu Cloud. This JSON typically contains all relevant details about the workflow, such as its configuration, status, triggers, and other metadata.
If the workflow includes any binary data (not indicated in the provided code), it would be included in the binary output field; however, based on the static analysis, this node primarily returns JSON data.
Dependencies
- Requires an API key credential for authenticating with the TexAu Cloud API.
- The node makes HTTP GET requests to the TexAu API endpoint
https://v2-prod-api.texau.com/api/v1/public/workflows/{workflowId}, where{workflowId}is URL-encoded. - No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Invalid or missing Workflow ID will cause the API request to fail.
- Authentication errors if the API key credential is not set up correctly.
- Network connectivity issues preventing access to the TexAu API endpoint.
Error messages:
- "404 Not Found" likely means the specified Workflow ID does not exist.
- "401 Unauthorized" indicates invalid or missing API credentials.
- Timeout or network errors suggest connectivity problems.
Resolutions:
- Verify the Workflow ID is correct and exists in your TexAu account.
- Ensure the API key credential is properly configured in n8n.
- Check network settings and firewall rules to allow outbound HTTPS requests to TexAu.
Links and References
- TexAu Official Website
- TexAu API Documentation (for detailed API endpoints and usage)