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 integrates with the Autotask REST API to create a new Contract Note resource. It allows users to map and define the fields of the Contract Note to be created, enabling automation of contract note creation within workflows. This is useful for managing contract-related documentation and notes programmatically, such as adding comments or updates to contracts in Autotask without manual entry.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the fields and their values to map for the Contract Note resource when creating a new entry. Users can specify which fields to include and provide their values, supporting custom and standard fields. |
Output
JSON
id- The unique identifier of the created Contract Note.fields- The data fields of the created Contract Note as returned by the Autotask API.
Dependencies
- Requires an Autotask API credential (API key or token) to authenticate requests to the Autotask REST API.
Troubleshooting
- Error: 'Resource contractNote is not supported' - This indicates the resource parameter is incorrect or not implemented; ensure 'contractNote' is selected as the resource.
- Authentication failures - Verify that the Autotask API credentials are correctly configured and have sufficient permissions.
- Field mapping errors - Ensure that the fields mapped in the 'Fields' property match the expected field names and data types required by the Autotask API for Contract Notes.
- API rate limits - The Autotask API may enforce rate limits; if exceeded, requests may fail temporarily.
Links
- Autotask Contract Notes API Documentation - Official Autotask API documentation for Contract Notes resource, detailing fields and usage.