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 Contract Charge in the Autotask system via its REST API. It is useful for automating the addition of charges related to contracts, such as fees or billable items, directly from workflows. For example, when a new service is rendered under a contract, this node can create the corresponding charge entry automatically.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the specific fields and their values to map when creating the Contract Charge. This allows users to specify which data points to include in the new Contract Charge record. |
Output
JSON
id- The unique identifier of the created Contract Charge.fields- The data fields of the created Contract Charge 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
- If the node throws an error about unsupported resource or operation, verify that the resource is set to 'contractCharge' and operation to 'create'.
- Errors related to missing or invalid fields in the 'Fields' property may occur if required Contract Charge fields are not provided or incorrectly mapped.
- Authentication errors indicate issues with the Autotask API credentials; ensure the credentials are valid and have sufficient permissions.
- Network or API errors may occur if the Autotask service is unreachable or returns an error; check API status and request payload.