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 a specific notification history record from the Autotask system by its unique ID. It is useful for workflows that need to access detailed information about past notifications, such as auditing notification delivery, troubleshooting notification issues, or integrating notification data into other systems. For example, a user can fetch a notification history record to verify if a notification was sent successfully or to extract metadata about the notification event.
Properties
| Name | Meaning |
|---|---|
| Notification History ID | The unique identifier of the notification history record to retrieve. This is a required input to specify which notification history entry to fetch. |
| Add Picklist Labels | Determines whether to automatically add human-readable '_label' fields for picklist fields in the response. This helps interpret picklist values by providing their labels alongside raw values. |
| Add Reference Labels | Determines whether to automatically add human-readable '_label' fields for reference fields in the response. This provides more understandable information for reference-type fields. |
| 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 regardless of selection. |
| Flatten User-Defined Fields | Determines whether user-defined fields (UDFs) should be brought up to the top level of the returned object instead of being nested inside a 'userDefinedFields' array. This simplifies access to UDFs. |
Output
JSON
id- The unique identifier of the notification history record.fields*- Various fields of the notification history record as specified by the selected columns or all fields if none selected.
*_label- Optional human-readable labels for picklist and reference fields, added if enabled in the input properties.userDefinedFields- Array of user-defined fields associated with the notification history record, unless flattened to top-level properties.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If the specified Notification History ID does not exist or is invalid, the node will throw an error indicating the record was not found. Verify the ID is correct.
- If API authentication fails, ensure the API key credential is correctly configured and has sufficient permissions.
- Selecting fields that do not exist may result in incomplete data or errors; use the 'Select Columns' dropdown to choose valid fields.
- Enabling 'Add Picklist Labels' or 'Add Reference Labels' when the API response does not include label data may result in missing label fields.