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 'Company Alert - Get Many' operation in this node retrieves multiple company alert records from the Autotask REST API. It allows users to fetch a list of alerts related to companies, which can be useful for monitoring, reporting, or triggering workflows based on alert data. For example, a user might retrieve all recent company alerts to analyze trends or to notify a team about critical issues.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the company alert records to map and include in the output. Supports defining fields manually or using resource mapping features. |
| Get All | Determines whether to return all available company alert records or limit the number of records returned. |
| Max Records | Specifies the maximum number of company alert records to return when 'Get All' is false. The value can range from 1 to 500. |
| Add Picklist Labels | If enabled, adds human-readable '_label' fields for picklist fields in the output, making it easier to understand picklist values. |
| Add Reference Labels | If enabled, adds human-readable '_label' fields for reference fields in the output, improving readability of referenced data. |
| Select Columns Names or IDs. | Allows selection of specific fields (columns) to include in the response. 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 brought to the top level of each object instead of being nested, simplifying access to these fields. |
Output
JSON
id- Unique identifier of the company alert record.fields- Values of the selected fields for each company alert record._label - Human-readable labels for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' is enabled.userDefinedFields- User-defined fields nested inside the userDefinedFields array, unless 'Flatten User-Defined Fields' is enabled.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If no records are returned, verify that the company alerts exist and that the API credentials have sufficient permissions.
- If the node returns an error about unsupported resource or operation, ensure that the resource is set to 'companyAlert' and operation to 'getMany'.
- If the maximum records limit is exceeded, reduce the 'Max Records' value or enable 'Get All' to fetch all records.
- If picklist or reference labels are missing, check that 'Add Picklist Labels' and 'Add Reference Labels' options are enabled.
- If user-defined fields are not accessible as expected, verify the 'Flatten User-Defined Fields' setting.