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 manage Contract Billing Rules. Specifically, the 'Create' operation allows users to create new contract billing rules by mapping input fields to the corresponding API fields. This is useful for automating contract billing configurations within Autotask, such as setting up billing rules for contracts programmatically. For example, a user can create billing rules that define how contract charges are applied based on specific criteria, streamlining contract management workflows.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the mapping of input data fields to the Contract Billing Rule fields in Autotask. Users specify which fields to include and how to map them when creating or updating contract billing rules. |
Output
JSON
id- The unique identifier of the created Contract Billing Rule.fields- The details of the Contract Billing Rule as returned by the Autotask API, reflecting the created resource's properties.
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 indicating unsupported resource or operation, verify that the resource is set to 'contractBillingRule' and the operation to 'create'.
- Errors related to field mapping usually occur if required fields are missing or incorrectly mapped; ensure all mandatory fields for creating a contract billing rule are provided.
- Authentication errors suggest issues with the Autotask API credentials; verify that the credentials are valid and have sufficient permissions.
- Network or API errors may occur if the Autotask service is unreachable or if rate limits are exceeded; check network connectivity and API usage limits.