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
This node operation retrieves a specific Company Alert from the Autotask system using its unique ID. It is useful for workflows that need to fetch detailed information about a particular alert related to a company, such as monitoring alerts, notifications, or status updates. For example, it can be used to automate alert handling by fetching alert details and triggering subsequent actions based on the alert content.
Properties
| Name | Meaning |
|---|---|
| Company Alert ID | The unique identifier of the company alert to retrieve. This is required to specify which alert to get. |
| Add Picklist Labels | Determines whether to automatically add human-readable '_label' fields for picklist fields in the response. Labels are only added if the picklist fields have values. |
| Add Reference Labels | Determines whether to automatically add human-readable '_label' fields for reference fields in the response. Labels are only added if the reference fields have values. |
| Select Columns Names or IDs. | Specifies which fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Determines whether user-defined fields (UDFs) should be brought up to the top level of each object instead of being nested inside the 'userDefinedFields' array. |
Output
JSON
id- The unique identifier of the company alert.fields- The various fields of the company alert as requested or all fields if none selected._label - Human-readable labels for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' options are enabled.userDefinedFields- Array of user-defined fields if 'Flatten User-Defined Fields' is false.
- User-defined fields brought to top-level if 'Flatten User-Defined Fields' is true.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the Company Alert ID is invalid or not found, the node will throw an error indicating the alert does not exist. Verify the ID is correct.
- If API authentication fails, ensure the Autotask API credentials are correctly configured and have sufficient permissions.
- If no fields are returned or data seems incomplete, check the 'Select Columns' property to ensure desired fields are selected or leave empty to retrieve all fields.
- If labels for picklist or reference fields are missing, verify that 'Add Picklist Labels' and 'Add Reference Labels' options are enabled and that the fields have values.