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 perform operations related to running automations. Specifically, the "Get Workflow Inputs" operation retrieves the input parameters for a given workflow by its ID. This is useful when you want to programmatically fetch what inputs a particular automation workflow requires before executing it or for documentation and validation purposes.
Practical examples include:
- Fetching required inputs of an automation workflow to dynamically generate forms or UI elements.
- Validating that all necessary inputs are provided before triggering a workflow run.
- Auditing or documenting workflows by extracting their input definitions.
Properties
| Name | Meaning |
|---|---|
| Workflow ID | The unique identifier of the workflow whose input parameters you want to retrieve. |
Output
The node outputs JSON data representing the inputs of the specified workflow. This typically includes details about each input parameter such as name, type, default values, and possibly descriptions depending on the API response.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the TexAu Cloud API.
- The node makes HTTP GET requests to the TexAu public API endpoint
/api/v1/public/inputs/{{workflowId}}. - The base URL for API requests is
https://v2-prod-api.texau.com.
Troubleshooting
- Invalid Workflow ID: If the provided Workflow ID does not exist or is malformed, the API may return an error or empty result. Verify the ID is correct.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- Network Issues: Connectivity problems can cause request failures; check network access to the TexAu API endpoint.
- API Rate Limits: Excessive requests might be throttled; consider adding delays or retries if needed.
Common error messages will generally come from the TexAu API and should be interpreted accordingly (e.g., 404 Not Found for invalid workflow, 401 Unauthorized for auth issues).
Links and References
- TexAu API Documentation (for detailed API endpoints and authentication)
- TexAu Official Website