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 updates an existing company record in the Autotask system by specifying the company ID and the fields to update. It is useful for automating updates to company information such as contact details, status, or custom fields within Autotask. For example, it can be used to update a company's address or phone number based on external data or workflow triggers.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company to update. This is required to specify which company record will be modified. |
| Fields | A resource mapper input that defines which fields of the company record to update and their new values. It supports defining fields manually or using auto-mapping features to map input data to company fields. |
Output
JSON
id- The unique identifier of the updated company record.fields- The updated fields and their new values for the company.success- Indicates whether the update operation was successful.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- Ensure the Company ID provided exists in Autotask; otherwise, the update will fail with a not found error.
- Verify that the fields to update are valid and allowed to be modified; invalid fields may cause errors.
- Check API authentication credentials if the node fails to connect or returns authorization errors.
- If the update does not reflect, confirm that the input data mapping is correct and that the node is configured to send the updated values properly.