TexAu icon

TexAu

Perform Opration on TexAu Cloud

Actions36

Overview

This node interacts with the TexAu Cloud platform to perform various operations on different resources. Specifically, for the Notification resource with the Get Many operation, it retrieves multiple notification records from the TexAu service. This is useful when you want to fetch a list of notifications, for example, to monitor alerts, track system messages, or audit events generated by TexAu automations or workflows.

Typical use cases include:

  • Fetching recent notifications to display in a dashboard.
  • Retrieving notifications for further processing or filtering within an automation workflow.
  • Archiving or logging notification data externally.

Properties

Name Meaning
Start The starting index (offset) from which to begin fetching notifications. Must be 0 or higher.
Limit The maximum number of notification results to return. Must be at least 1.

These properties control pagination of the notifications retrieved.

Output

The node outputs JSON data containing an array of notification objects fetched from TexAu. Each object represents a notification with its associated details as provided by the TexAu API.

If the node supports binary data output (not indicated here), it would typically represent attachments or media related to notifications, but this is not evident from the provided code.

Dependencies

  • Requires an active connection to the TexAu Cloud API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for API requests is https://v2-prod-api.texau.com.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Requesting a start value beyond the available range may result in empty responses.
    • Setting limit too high might lead to performance issues or API rate limiting.

  • Error messages:

    • Authentication errors typically indicate invalid or expired API tokens; reconfigure credentials.
    • HTTP 4xx or 5xx errors suggest issues with request parameters or server availability; verify property values and network connectivity.

Links and References

Discussion