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
Company Alert → Get Many (Advanced)
AI-generatedOverview
The node interacts with Kaseya's Autotask PSA REST API to retrieve multiple company alert records based on advanced filtering criteria. It supports fetching all matching records or limiting the number of results, and allows customization of the returned fields and labels. This operation is useful for scenarios where users need to query company alerts with complex filters, such as retrieving alerts matching specific conditions or attributes.
Use Case Examples
- Retrieve all company alerts with a specific status or priority using an advanced JSON filter.
- Fetch a limited number of company alerts and include only selected fields for reporting or integration purposes.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all results or only up to a given limit. |
| Max Records | Maximum number of company alert records to return when not returning all. Range is 1 to 500. |
| Advanced Filter | A JSON string containing a "filter" array with Autotask API query criteria to filter company alerts. |
| Add Picklist Labels | Whether to automatically add "_label" fields for picklist fields with human-readable values in the response. |
| Add Reference Labels | Whether to automatically add "_label" fields for reference fields with human-readable values in the response. |
| 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 instead of being nested in the userDefinedFields array. |
Output
JSON
id- Unique identifier of the company alert record.fieldName_label- Human-readable labels for picklist or reference fields if enabled.
Dependencies
- Kaseya Autotask PSA REST API
- API authentication credentials (username, API integration code, and zone URL if custom)
Troubleshooting
- Ensure the API credentials are correctly configured and have sufficient permissions to access company alerts.
- Verify the JSON syntax and structure of the advanced filter to match Autotask API requirements.
- If no results are returned, check the filter criteria to ensure they match existing company alerts.
- If the node fails with rate limit errors, consider the API rate limits and retry logic.
Links
- Autotask REST API Documentation - Official documentation for Autotask REST API including query filters and endpoints.