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 new Contract in the Autotask system by mapping user-defined input fields to the contract resource's properties. It is useful for automating contract creation workflows, such as generating contracts from form submissions or integrating contract data from other systems.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the specific contract fields and their values to be set when creating the contract. This uses a resource mapper to allow flexible field mapping and supports automatic mapping of fields. |
Output
JSON
id- The unique identifier of the created contract in Autotask.contractNumber- The contract number assigned to the newly created contract.name- The name of the created contract.status- The current status of the created contract.startDate- The start date of the contract.endDate- The end date of the contract.otherProperties- Additional contract properties as returned by the Autotask API.
Dependencies
- Requires an Autotask API credential for authentication to the Autotask REST API.
Troubleshooting
- Ensure that all required contract fields are provided in the 'Fields' mapping; missing mandatory fields may cause API errors.
- Verify that the Autotask API credentials are valid and have sufficient permissions to create contracts.
- If the API returns validation errors, check the field formats and values against Autotask's contract resource requirements.
- Network or connectivity issues may cause request failures; ensure the node can reach the Autotask API endpoint.