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 automations and other resources. Specifically, the "Automation - Get" operation retrieves detailed information about a single automation by its unique identifier. This is useful when you want to fetch the configuration or status of a specific automation within your TexAu account.
Common scenarios include:
- Fetching details of an existing automation to display or process further.
- Validating that an automation exists before triggering or modifying it.
- Integrating automation metadata into workflows for reporting or decision-making.
Example: You have an automation ID from a previous step or external source, and you want to retrieve its full details to decide whether to run it or update its parameters.
Properties
| Name | Meaning |
|---|---|
| Automation ID | The unique identifier of the automation to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the retrieved automation object from TexAu. This typically includes all properties and metadata associated with the automation such as its name, configuration, triggers, actions, status, and timestamps.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for TexAu Cloud to authenticate requests.
- The node makes HTTP GET requests to the TexAu API endpoint
https://v2-prod-api.texau.com/api/v1/public/automations/{automationId}. - Proper network access to TexAu's API service is necessary.
Troubleshooting
- Invalid or missing Automation ID: If the Automation ID is empty or incorrect, the API will likely return a 404 Not Found or similar error. Ensure the ID is correct and corresponds to an existing automation.
- Authentication errors: If the API key credential is invalid or missing, authentication failures will occur. Verify that the API key is correctly configured in n8n credentials.
- Network issues: Connectivity problems to TexAu's API endpoint can cause request failures. Check network/firewall settings.
- API rate limits: Excessive requests may be throttled by TexAu. Implement retry logic or reduce request frequency if needed.
Links and References
- TexAu Official Website
- TexAu API Documentation (for detailed API endpoints and data structures)