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, specifically allowing users to retrieve multiple platform records ("Get Many" operation on the "Platform" resource). It is useful for scenarios where you want to list or filter platforms available in your TexAu account, such as when managing integrations or automations that depend on specific platforms.
For example, you might use this node to:
- Fetch a paginated list of platforms starting from a certain index.
- Limit the number of platforms returned per request.
- Filter platforms by type (e.g., Cookie, API Key, OAuth2).
- Search platforms by text query.
This enables efficient management and selection of platforms within workflows.
Properties
Name | Meaning |
---|---|
Start | The starting index number for pagination. Must be 0 or greater. |
Limit | Maximum number of platform results to return. Must be at least 1. |
Options | Additional optional filters: |
Type | Filter platforms by authentication type. Options: Cookie, Api Key, OAuth2. |
Filters | Nested filter options: |
Search Text (q) | Text string to filter platforms by search keyword. |
Output
The node outputs JSON data containing an array of platform objects matching the query parameters. Each platform object typically includes details such as platform name, ID, and type. This output can be used downstream in workflows to reference or manipulate specific platforms.
No binary data output is indicated.
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/platforms
. - No additional environment variables are explicitly required beyond the API credential.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing invalid values for
start
orlimit
(e.g., negative numbers) may result in errors or empty responses. - Filtering by unsupported types or malformed search queries could yield no results.
Error messages:
- Authentication errors typically indicate problems with the provided API key; ensure it is valid and has necessary permissions.
- Request parameter validation errors suggest checking the
start
,limit
, and filter values for correctness. - Network or API downtime errors require verifying connectivity and TexAu service status.
Links and References
- TexAu API Documentation (general reference for API endpoints and authentication)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics