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 integrates with the Autotask REST API to create a new Company Alert. It allows users to define and map specific fields for the alert, enabling automated creation of alerts related to companies within Autotask. This is useful for workflows that need to trigger notifications or track issues associated with companies, such as alerting support teams or logging important company-related events.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the fields and their values to be mapped and sent when creating the Company Alert. This property uses a resource mapper to specify which alert fields to populate. |
Output
JSON
id- The unique identifier of the created Company Alert.name- The name or title of the Company Alert.description- Detailed description or content of the Company Alert.companyId- Identifier of the company associated with the alert.status- Current status of the alert (e.g., active, resolved).createdDate- Timestamp when the alert was created.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Error: 'Resource companyAlert is not supported' - Ensure the resource parameter is correctly set to 'companyAlert'.
- Authentication failures - Verify that the Autotask API credentials are correctly configured and have sufficient permissions.
- Field mapping errors - Confirm that the fields mapped in 'Fields' property match the expected fields for a Company Alert in Autotask.
- API rate limits - If requests fail due to rate limiting, consider adding delays or retries in the workflow.