Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association 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
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Contract Exclusion Billing Code 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 Rate Actions
- Contract Role Costs Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Contract Service Bundle Adjustment → Get Many (Advanced)
AI-generatedOverview
This node operation retrieves multiple records of Contract Service Bundle Adjustments from the Autotask PSA system using advanced filtering criteria. It is useful for scenarios where users need to query and extract detailed data about contract service bundle adjustments based on complex conditions, such as filtering by specific fields or attributes. For example, a user might want to get all adjustments related to a particular contract or within a certain date range using a JSON-based advanced filter.
Use Case Examples
- Retrieve all contract service bundle adjustments for a specific contract using an advanced JSON filter.
- Get a limited number of contract service bundle adjustment records with specific fields selected for reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all results or only up to a given limit. |
| Max Records | Maximum number of records to return when 'Get All' is false, ranging from 1 to 500. |
| Advanced Filter | A JSON string containing a 'filter' array with Autotask API query criteria to specify complex filtering conditions for the data retrieval. |
| Add Picklist Labels | Whether to automatically add '_label' fields for picklist fields with human-readable values (labels are not added for empty values). |
| Add Reference Labels | Whether to automatically add '_label' fields for reference fields with human-readable values (labels are not added for empty values). |
| Select Columns Names or IDs. | Choose which fields to include in the response. If no fields are selected, all fields will be returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Whether to bring user-defined fields up to the top level of each object, making them accessible as top-level properties instead of nested in the userDefinedFields array. |
Output
JSON
id- Unique identifier of the contract service bundle adjustment record.fields- Selected fields of the contract service bundle adjustment record as per the query._label- Human-readable labels for picklist and reference fields if enabled.
Dependencies
- An API key credential for Autotask PSA REST API authentication.
Troubleshooting
- Common issues include invalid JSON in the advanced filter, which will cause query errors. Ensure the JSON string is correctly formatted and follows Autotask API query criteria.
- If the node returns no data, verify that the filter criteria match existing records and that the user has appropriate permissions.
- Errors related to authentication indicate issues with the provided API credentials; verify the API key and integration code are correct and active.
Links
- Autotask API Basic Query Calls - Official documentation for constructing advanced filter queries in Autotask API.
- n8n Autotask Node GitHub Repository - Source code and documentation for the Autotask node in n8n.