Actions389
- Contract Actions
- Ticket History Actions
- Ticket Note Webhook Actions
- Ticket Note Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Role Actions
- Resource Role Actions
- Search Filter Actions
- Service Actions
- Skill Actions
- Service Call Actions
- Survey Results Actions
- Survey Actions
- Ticket Actions
- Opportunity Actions
- Notification History Actions
- Invoice Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Phase Actions
- Project Task Actions
- Project Note Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Service Bundle Adjustment Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Rate Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Role Costs Actions
- Contact Groups Actions
- Contact Actions
- Contact Webhook Actions
- Contact Group Contacts Actions
- Contract Block Hour Factor Actions
- Contract Block Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Company Alert Actions
- Company Actions
- Billing Code Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Overview
This node operation retrieves multiple notification history records from the Autotask system using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter the notification history data precisely. This is useful for auditing, monitoring, or reporting on notification events within Autotask, such as tracking system alerts or user notifications over time.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching notification history records or limit the results to a specified maximum number. |
| 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. |
| Advanced Filter | A required JSON string containing a 'filter' array that defines the Autotask API query criteria to filter notification history records. This allows for complex and precise queries based on Autotask's REST API filtering capabilities. |
| Add Picklist Labels | If enabled, the node automatically adds additional fields with '_label' suffix for picklist fields, providing human-readable values for those fields. |
| Add Reference Labels | If enabled, the node automatically adds additional fields with '_label' suffix for reference fields, providing human-readable values for those references. |
| Select Columns Names or IDs. | Allows selection of specific fields (columns) to include in the response. If no fields are selected, all fields are returned by default. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are brought up to the top level of each returned object instead of being nested inside a 'userDefinedFields' array, simplifying access to these fields. |
Output
JSON
id- Unique identifier of the notification history record.notificationHistory*- Properties of the notification history record as returned by the Autotask API, including fields such as notification type, status, timestamps, and related entity references.
*_label- Human-readable labels for picklist and reference fields, added automatically if enabled in the input properties.userDefinedFields*- User-defined fields associated with the notification history record, either nested or flattened to top-level properties depending on the 'Flatten User-Defined Fields' setting.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in the 'Advanced Filter' property will cause the node to fail. Ensure the JSON string is correctly formatted and contains a valid 'filter' array as per Autotask API documentation.
- Requesting too many records without pagination or 'Get All' enabled may lead to timeouts or API rate limiting. Use 'Max Records' to limit the number of returned records or enable 'Get All' cautiously.
- Selecting fields that do not exist or are misspelled in 'Select Columns' may result in incomplete data or errors. Use the 'Get Field Info' feature to verify field names.
- If picklist or reference labels are not appearing as expected, verify that the corresponding 'Add Picklist Labels' and 'Add Reference Labels' options are enabled.
- API authentication errors may occur if the Autotask API key credential is missing, expired, or invalid. Verify credentials in the node settings.
Links
- Autotask API Basic Query Calls - Official Autotask documentation describing how to construct filter queries for API calls.