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 enables creating a Configuration Item Note in the Autotask system via its REST API. It is useful for users who want to programmatically add notes to configuration items within Autotask, such as documenting changes, updates, or important information related to a configuration item. For example, a user can automate adding notes when a configuration item is updated or when a support ticket references a configuration item.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the specific fields and their values to set when creating the Configuration Item Note. This uses a resource mapper to allow flexible mapping of input data to the note's fields. |
Output
JSON
id- The unique identifier of the created Configuration Item Note.configurationItemID- The ID of the configuration item to which the note is attached.note- The content text of the note.createdDate- Timestamp when the note was created.createdBy- Identifier or name of the user who created the note.
Dependencies
- Requires an Autotask API key credential for authentication to the Autotask REST API.
Troubleshooting
- If the node throws an error about unsupported resource, ensure the resource parameter is set to 'configurationItemNote'.
- Errors related to authentication usually indicate missing or invalid API credentials; verify the Autotask API key is correctly configured.
- If required fields are missing in the 'Fields' mapping, the API may reject the request; ensure all mandatory fields for creating a Configuration Item Note are provided.
- Network or API errors may occur if the Autotask service is unreachable; check network connectivity and Autotask service status.