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 Adjustment in Autotask via its REST API. It allows users to define and map specific fields for the adjustment, facilitating automation of contract service bundle modifications. Typical use cases include adjusting service bundles within contracts for billing or service management purposes, such as applying discounts, corrections, or other adjustments to bundled services.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the specific fields and their values to map for creating the Contract Service Bundle Adjustment. This property supports detailed field mapping, including user-defined fields and picklists, allowing precise control over the adjustment data sent to Autotask. |
Output
JSON
id- Unique identifier of the created Contract Service Bundle Adjustment.fields- The data fields of the created Contract Service Bundle Adjustment as returned by the Autotask API.status- Status of the creation operation, indicating success or failure.
Dependencies
- Requires an Autotask API credential (API key or token) configured in n8n to authenticate requests.
- Relies on the Autotask REST API endpoint for Contract Service Bundle Adjustments.
Troubleshooting
- Error: 'Resource contractServiceBundleAdjustment is not supported' - Ensure the resource and operation names are correctly set to 'contractServiceBundleAdjustment' and 'create'.
- Authentication failures - Verify that the Autotask API credentials are valid and have sufficient permissions.
- Field mapping errors - Confirm that all required fields are mapped correctly and that field values conform to expected formats and picklist options.
- API rate limits - If requests fail due to rate limiting, consider adding delays or retries.