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 Service Bundle in the Autotask system via its REST API. It is useful for automating the management of contract service bundles, which group multiple contract services together for billing or organizational purposes. For example, a user can create a new service bundle by mapping input fields to the bundle's properties, facilitating integration with other systems or workflows.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the fields and their values to map when creating the Contract Service Bundle. This property uses a resource mapper to specify which fields to include and how to populate them. |
Output
JSON
id- The unique identifier of the created Contract Service Bundle.name- The name of the Contract Service Bundle.description- Description or details about the Contract Service Bundle.fields- Additional properties of the Contract Service Bundle as returned by the Autotask API.
Dependencies
- Requires an Autotask API credential for authentication to access the Autotask REST API.
Troubleshooting
- If the node throws an error about unsupported resource, ensure the resource parameter is set to 'contractServiceBundle'.
- Errors related to field mapping usually indicate missing or invalid field values; verify the fields mapped in the 'Fields' property.
- Authentication errors suggest issues with the Autotask API credentials; verify that the API key or token is valid and has 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.