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 Configuration Item Notes from the Autotask system using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter the notes, control the number of records returned, and customize the output by including human-readable labels for picklist and reference fields. This is useful for scenarios where detailed and specific Configuration Item Notes data is needed, such as generating reports, syncing data with other systems, or performing bulk data analysis.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching Configuration Item Notes or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of Configuration Item Notes to return when 'Get All' is set to false. The value must be between 1 and 500. |
| Advanced Filter | A required JSON string containing a 'filter' array that defines the query criteria according to the Autotask API specification. This allows for complex and precise filtering of Configuration Item Notes. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields in the output. Empty values do not get labels. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the output. Empty values do not get labels. |
| 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 | If enabled, user-defined fields (UDFs) are moved to the top level of each returned object instead of being nested inside a userDefinedFields array, simplifying access. |
Output
JSON
id- Unique identifier of the Configuration Item Note.note- The content or text of the Configuration Item Note.createdDate- Date and time when the note was created.createdBy- Identifier or reference to the user who created the note.configurationItemId- Identifier of the related Configuration Item.picklistField_label- Human-readable label for a picklist field, if 'Add Picklist Labels' is enabled.referenceField_label- Human-readable label for a reference field, if 'Add Reference Labels' is enabled.userDefinedFields- User-defined custom fields, either nested or flattened to top-level depending on 'Flatten User-Defined Fields' setting.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in 'Advanced Filter' property can cause query failures. Ensure the JSON string is well-formed and follows Autotask API filter syntax.
- Requesting more than 500 records when 'Get All' is false and 'Max Records' exceeds limits will result in errors. Keep 'Max Records' between 1 and 500.
- If no records are returned, verify that the filter criteria in 'Advanced Filter' correctly match existing Configuration Item Notes.
- Enabling 'Add Picklist Labels' or 'Add Reference Labels' may increase response size; disable if performance is a concern.
- Flattening user-defined fields may cause naming conflicts if UDF names overlap with standard fields; use with caution.
Links
- Autotask API Basic Query Calls - Official Autotask documentation describing how to construct advanced filter queries for API calls.