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 allows users to create a new Configuration Item Type in Autotask by mapping input fields to the corresponding properties of the Configuration Item Type resource. It is useful for automating the addition of configuration item types in IT service management workflows, such as defining new categories of assets or services tracked in Autotask.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the mapping of input data fields to the Configuration Item Type properties to be created. This mapping supports manual definition and automatic mapping of fields to ensure correct data structure for the API call. |
Output
JSON
id- The unique identifier of the newly created Configuration Item Type.name- The name of the created Configuration Item Type.description- Description or details of the Configuration Item Type.otherProperties- Additional properties returned by the Autotask API for the created Configuration Item Type.
Dependencies
- Requires an Autotask API credential for authentication to perform create operations on Configuration Item Types.
Troubleshooting
- Ensure that all required fields in the 'Fields' mapping are provided; missing mandatory fields will cause API errors.
- Verify that the Autotask API credentials are valid and have sufficient permissions to create Configuration Item Types.
- If the API returns validation errors, check the field mappings for correct data types and allowed values.
- Network or connectivity issues may cause request failures; ensure the node can reach the Autotask API endpoint.