Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

The node retrieves multiple records from the Notification History resource in Autotask. It is useful for workflows that need to fetch and process batches of notification history entries, such as auditing notification events, generating reports, or integrating notification data with other systems. For example, a user can fetch the latest 100 notification history records to analyze notification trends or trigger alerts based on specific notification types.

Properties

Name Meaning
Fields Defines which fields from the Notification History records to retrieve and map in the output. Supports custom mapping and auto-mapping of fields.
Get All Determines whether to return all available notification history records or limit the number of records returned.
Max Records Specifies the maximum number of notification history records to return when 'Get All' is false. The value must be between 1 and 500.
Add Picklist Labels If enabled, adds additional fields with human-readable labels for picklist fields in the output, improving readability.
Add Reference Labels If enabled, adds additional fields with human-readable labels for reference fields in the output.
Select Columns Names or IDs. Allows selection of specific fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included.
Flatten User-Defined Fields If enabled, user-defined fields (UDFs) are promoted to top-level properties in each record instead of being nested inside a userDefinedFields array.

Output

JSON

  • id - Unique identifier of the notification history record.
  • fieldName
    • _label - Human-readable label for picklist or reference fields if Add Picklist Labels or Add Reference Labels is enabled.
  • userDefinedFields
    • udfName - User-defined fields nested or flattened depending on the Flatten User-Defined Fields property.

Dependencies

  • Requires an Autotask API key credential for authentication to access the Autotask REST API.

Troubleshooting

  • If the node returns no data, verify that the Notification History resource contains records and that the selected fields are valid.
  • If authentication errors occur, ensure the Autotask API key credential is correctly configured and has sufficient permissions.
  • If the node times out or returns partial data, consider enabling 'Get All' carefully or increasing the Max Records limit within allowed bounds.
  • Errors related to invalid field names may occur if the selected fields do not exist; verify field names using the resource's field list.

Links

Discussion