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 Block → Get Many
AI-generatedOverview
This node operation retrieves multiple Contract Block records from the Autotask PSA system. It supports fetching all records or limiting the number of records returned, with options to customize the output fields and formatting. This operation is useful for scenarios where users need to list or analyze multiple contract blocks, such as generating reports or syncing contract block data with other systems.
Use Case Examples
- Fetch all contract blocks to synchronize with an external database.
- Retrieve a limited number of contract blocks for display in a dashboard.
- Get contract blocks with specific fields selected to optimize data transfer and processing.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all results or only up to a given limit. |
| Max Records | Maximum number of contract block records to return when not returning all. |
| Add Picklist Labels | Whether to automatically add human-readable labels for picklist fields in the output. |
| Add Reference Labels | Whether to automatically add human-readable labels for reference fields in the output. |
| Select Columns Names or IDs. | Choose which fields to include in the response; if none selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | Whether to bring user-defined fields up to the top level of each object instead of nested in an array. |
| Fields | Mapping configuration for fields to define how data is structured or transformed. |
Output
JSON
id- Unique identifier of the contract block record.name- Name or title of the contract block.description- Description or details about the contract block.startDate- Start date of the contract block.endDate- End date of the contract block.hourFactor- Hour factor associated with the contract block.billingCode- Billing code linked to the contract block.userDefinedFields- User-defined fields related to the contract block, optionally flattened to top-level properties._label- Additional human-readable labels for picklist or reference fields if enabled.
Dependencies
- An API key credential for Autotask PSA REST API
Troubleshooting
- Ensure the API credentials are correctly configured and have sufficient permissions to access contract block data.
- If the node returns no data, verify that contract blocks exist in the Autotask system and that any filters or limits are set appropriately.
- Errors related to rate limits may occur; ensure the API rate tracker is properly initialized or handle rate limiting in your workflow.
- If picklist or reference labels are not appearing, check that the corresponding options are enabled and that the fields support labels.
Links
- Autotask PSA REST API Documentation - Official API documentation for interacting with Autotask PSA resources including contract blocks.