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 allows updating an existing contact in the Autotask system by specifying the contact's unique ID and the fields to update. It is useful for automating contact information management, such as updating phone numbers, email addresses, or other contact details in bulk or as part of a workflow. For example, when a customer's information changes in a CRM, this node can update the corresponding contact record in Autotask automatically.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to update in Autotask. |
| Fields | The set of contact fields and their new values to update. This uses a resource mapper to define which fields to modify and their corresponding values. |
Output
JSON
id- The unique identifier of the updated contact.fields- The updated fields and their values for the contact.rawResponse- The full raw response from the Autotask API after updating the contact.
Dependencies
- Requires an Autotask API credential (API key or token) to authenticate requests.
- Relies on the Autotask REST API to perform contact update operations.
Troubleshooting
- Error 'Contact ID is required': Ensure the Contact ID parameter is provided and valid.
- API authentication errors: Verify that the Autotask API credentials are correctly configured and have sufficient permissions.
- Field mapping errors: Confirm that the fields specified in the 'Fields' property exist and are valid for the contact resource.
- Network or API errors: Check network connectivity and Autotask API status if requests fail.