Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association 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
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Contract Exclusion Billing Code 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 Rate Actions
- Contract Role Costs Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Configuration Item → Create If Not Exists
AI-generatedOverview
This node operation for the 'Configuration Item' resource with the 'Create If Not Exists' operation allows users to create a configuration item in the Autotask system only if it does not already exist based on specified deduplication fields. It is useful in scenarios where you want to avoid creating duplicate configuration items by checking existing records against certain fields. If a duplicate is found, the node can either update the existing item with specified fields or throw an error, depending on the user's configuration.
Use Case Examples
- Automatically add new configuration items from an external system only if they don't already exist in Autotask, using fields like serial number or asset tag for deduplication.
- Update existing configuration items with new information if duplicates are found based on specified fields, ensuring data consistency without creating duplicates.
Properties
| Name | Meaning |
|---|---|
| Dedup Fields Names or IDs | Fields used for duplicate detection. If empty, deduplication is skipped and the item is always created. |
| Update Fields Names or IDs | Fields to compare against the duplicate. If values differ, the duplicate will be updated. This is ignored when 'Error on Duplicate' is enabled. |
| Error On Duplicate | Whether to throw an error when a duplicate is found instead of returning it. |
| Fields | Fields to map for the configuration item creation or update. This is required and supports auto-mapping and multi-key matching. |
Output
JSON
id- The unique identifier of the created or found configuration item.status- The status of the operation, e.g., created, updated, or found duplicate.data- The detailed data of the configuration item after the operation.
Dependencies
- An API key credential for Autotask API authentication is required.
Troubleshooting
- If the node throws an error about duplicates, check if 'Error On Duplicate' is enabled and adjust accordingly.
- Ensure that the deduplication fields are correctly specified and exist in the Autotask configuration item schema.
- If updates are not applied on duplicates, verify that 'Update Fields' are correctly set and that 'Error On Duplicate' is disabled.
Links
- Autotask REST API Documentation - Official documentation for Autotask REST API which this node interacts with.