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 interacts with the Autotask REST API to update an existing Company Alert entity. It allows users to specify the ID of the company alert they want to update and map the fields they wish to modify. This is useful for automating updates to alerts related to companies, such as changing alert details or statuses based on workflow conditions.
Properties
| Name | Meaning |
|---|---|
| Company Alert ID | The unique identifier of the company alert to update. This is required to specify which alert record will be modified. |
| Fields | A resource mapper input that defines which fields of the company alert should be updated and their new values. It supports defining fields manually or using auto-mapping features. |
Output
JSON
id- The unique identifier of the updated company alert.fields- The updated fields and their new values for the company alert.status- The status of the update operation, indicating success or failure.message- Additional information or error messages related to the update operation.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the Company Alert ID is missing or invalid, the node will fail to locate the alert to update. Ensure the ID is correct and exists in Autotask.
- Incorrect field mappings or unsupported fields may cause the update to fail. Verify that the fields to update are valid for the Company Alert resource.
- Authentication errors may occur if the API key credential is invalid or expired. Check and update the Autotask API credentials as needed.
- Network or API rate limit issues can cause failures. Retry after some time or check API usage limits.