Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association 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
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Contract Exclusion Billing Code 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 Rate Actions
- Contract Role Costs Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Ticket Category → Update
AI-generatedOverview
This node operation updates an existing Ticket Category in the Autotask PSA system. It is useful for scenarios where you need to modify details of a ticket category, such as changing its name, description, or other attributes. For example, you might update a ticket category to reflect new service offerings or organizational changes.
Use Case Examples
- Updating the name and description of a ticket category to better categorize support tickets.
- Modifying custom fields of a ticket category to align with updated business processes.
Properties
| Name | Meaning |
|---|---|
| Ticket Category ID | The ID of the ticket category to operate on, used to identify which ticket category to update. |
| Dry Run | Whether to return a request preview instead of executing the operation. Useful for testing and validation without making actual changes. |
| Fields | The fields of the ticket category to update, allowing mapping of specific properties to be changed. |
Output
JSON
id- The unique identifier of the updated ticket category.name- The name of the updated ticket category.description- The description of the updated ticket category.otherFields- Other updated properties of the ticket category as specified in the input fields.
Dependencies
- Autotask PSA REST API
- An API key credential for authentication
Troubleshooting
- Ensure the Ticket Category ID is valid and exists in the Autotask system to avoid errors.
- If Dry Run is enabled, no changes will be made; disable it to perform the update.
- Check API credentials and permissions if the update operation fails with authentication errors.
- Validate the fields to update are correctly mapped and supported by the API to prevent request errors.
Links
- Autotask PSA REST API Documentation - Official documentation for the Autotask REST API used by this node.