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
Contract → Create If Not Exists
AI-generatedOverview
This node operation for the 'Contract' resource with the 'Create If Not Exists' operation allows users to create a new contract in the Autotask PSA system only if a duplicate contract does not already exist based on specified deduplication fields. It is useful for avoiding duplicate contract entries while ensuring new contracts are added when necessary. For example, it can be used in automated workflows to add contracts from external systems without creating duplicates.
Use Case Examples
- Automatically create a contract in Autotask only if it doesn't already exist based on contract number or client ID.
- Update existing contract details if a duplicate is found and the update fields differ, or throw an error if duplicates are not allowed.
Properties
| Name | Meaning |
|---|---|
| Dedup Fields Names or IDs | Fields used for duplicate detection. If empty, deduplication is skipped and a new contract is always created. |
| Update Fields Names or IDs | Fields to compare against the duplicate contract. If values differ, the duplicate contract will be updated. Ignored if 'Error on Duplicate' is enabled. |
| Error On Duplicate | Boolean flag to determine whether to throw an error when a duplicate contract is found instead of returning it. |
| Fields | Mapping of contract fields to be created or updated in the operation. |
Output
JSON
id- The unique identifier of the created or found contract.fields- The contract fields data that were created or updated.duplicateFound- Boolean indicating if a duplicate contract was found during the operation.
Dependencies
- Requires an API key credential for Autotask PSA REST API authentication.
Troubleshooting
- If the node throws an error about duplicate contracts, check the 'Error On Duplicate' setting and the deduplication fields configuration.
- Ensure the API credentials are valid and have sufficient permissions to create or update contracts.
- If no contracts are created or updated, verify that the deduplication fields and update fields are correctly specified and match the data structure in Autotask.
Links
- Autotask PSA REST API Documentation - Official API documentation for Autotask PSA, useful for understanding contract resource operations.