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 interacts with the TexAu Cloud platform to retrieve multiple automation records. Specifically, the "Get Many" operation under the "Automation" resource fetches a list of automations available on a specified platform. This is useful for users who want to programmatically access and manage their automations in bulk, such as listing all automations for review, reporting, or further processing within an n8n workflow.
Practical examples include:
- Fetching all automations from a particular social media platform integrated with TexAu.
- Retrieving a paginated list of automations to display in a dashboard or trigger conditional logic based on automation properties.
- Integrating TexAu automations data into other systems by exporting the list via n8n.
Properties
| Name | Meaning |
|---|---|
| Start | The starting index number for the results to return. Must be 0 or greater. |
| Limit | The maximum number of automation records to return. Must be at least 1. |
| Platform Name or ID | Select the platform from which to retrieve automations. Options are loaded dynamically from TexAu platforms. |
Output
The node outputs JSON data containing an array of automation objects retrieved from the TexAu API. Each object represents an automation with its associated details (such as name, ID, and other metadata). The exact structure depends on the TexAu API response but typically includes identifiers and descriptive fields for each automation.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the TexAu Cloud API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node uses the TexAu API base URL:
https://v2-prod-api.texau.com. - The "Platform Name or ID" property relies on dynamically loaded options fetched from the TexAu platforms endpoint.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Specifying a non-existent platform ID may result in empty results or errors.
- Requesting too large a limit might lead to API rate limiting or timeouts.
Error Messages:
- Authentication errors typically indicate invalid or expired API tokens; reconfigure credentials.
- "Resource not found" or similar errors suggest incorrect platform IDs or unavailable resources.
- Network or timeout errors may require checking connectivity or reducing the requested limit.
Links and References
- TexAu API Documentation (for detailed API endpoints and data structures)
- n8n Expressions Documentation (for using expressions in property values)