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 updates an existing Service Call record in the Autotask system. It is useful for scenarios where you need to modify details of a service call, such as changing its status, updating assigned resources, or adjusting other service call attributes. For example, a support team can use this node to update the progress or resolution details of a customer service call automatically within a workflow.
Properties
| Name | Meaning |
|---|---|
| Service Call ID | The unique identifier of the service call record to update. This is required to specify which service call will be modified. |
| Fields | A resource mapper input that defines which fields of the service call should be updated and their new values. It supports defining fields manually or using auto-mapping features to map input data to service call fields. |
Output
JSON
id- The unique identifier of the updated service call.fields- An object containing the updated fields and their new values for the service call.status- The current status of the service call after the update.assignedResource- Information about the resource assigned to the service call, if updated.updatedAt- Timestamp indicating when the service call was last updated.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the Service Call ID is invalid or does not exist, the node will throw an error indicating the service call could not be found. Verify the ID is correct.
- If required fields for the update are missing or incorrectly mapped, the API may reject the request. Ensure all mandatory fields are provided and correctly formatted.
- Authentication errors may occur if the API key credential is missing or invalid. Confirm the credential is configured properly in n8n.
- Network or API rate limit issues can cause failures. Check connectivity and Autotask API usage limits.