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
The 'Contract Block - Get Many' operation in this node retrieves multiple contract block records from the Autotask system. It allows users to fetch a list of contract blocks with control over which fields to include, how many records to return, and whether to include human-readable labels for picklist and reference fields. This operation is useful for scenarios such as generating reports, synchronizing contract block data with other systems, or bulk processing contract block information.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the contract block records to retrieve and map in the output. Supports custom mapping and selection of specific fields. |
| Get All | Determines whether to return all matching contract block records or limit the number of records returned. |
| Max Records | Specifies the maximum number of contract block records to return when 'Get All' is false. Value range is 1 to 500. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields in the contract block records. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the contract block records. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response by choosing from a list or specifying field IDs via expressions. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are promoted to top-level properties in each contract block object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the contract block record.
- Standard or user-defined fields of the contract block as specified in the Fields property._label - Human-readable label for picklist or reference fields if Add Picklist Labels or Add Reference Labels is enabled.userDefinedFields- Array of user-defined fields if Flatten User-Defined Fields is false; otherwise, UDFs appear as top-level properties.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the contract blocks exist and that the selected fields and filters are correct.
- If the node throws an authentication error, ensure the Autotask API credentials are valid and have sufficient permissions.
- When selecting specific fields, ensure the field IDs or names are correct; otherwise, the response may omit expected data.
- If the maximum records limit is set too low, not all desired records will be retrieved; consider enabling 'Get All' to fetch all records.