Actions104
- Custom Field Actions
- Custom Field Block Actions
- Custom Field Type Actions
- Customer Actions
- Deal Actions
- Lead Actions
- Meeting Actions
- Meeting Room Actions
- Meeting Type Actions
- Organization Actions
- Pipeline Actions
- Prospect Actions
- Staff Actions
- Task Actions
- Ticket Actions
- Treatment Actions
- Treatment Type Actions
- Workspace Actions
Ticket → Update
AI-generatedOverview
This node updates an existing ticket in the Magnet Customer system. It is useful for scenarios where you need to modify ticket details such as subject, description, priority, workspace receiver ID, or contact ID. For example, you can update the priority of a support ticket or change its description based on new information.
Use Case Examples
- Updating the subject and priority of a customer support ticket.
- Changing the contact associated with a ticket after receiving new customer details.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the authentication method to use for the API request (API Token or OAuth2). |
| Ticket ID | The unique identifier of the ticket to update. This is required. |
| Subject | The new subject/title of the ticket. |
| Description | The new description or details of the ticket. |
| Priority | The priority level of the ticket (Low, Medium, High). |
| Workspace Receiver ID | The ID of the workspace receiver associated with the ticket. |
| Contact ID | The ID of the contact associated with the ticket. |
Output
JSON
_id- The unique identifier of the updated ticket.subject- The updated subject of the ticket.description- The updated description of the ticket.priority- The updated priority level of the ticket.workspaceReceiver- The updated workspace receiver ID associated with the ticket.contact- The updated contact ID associated with the ticket.
Dependencies
- Magnet Customer API with either API Token or OAuth2 authentication
Troubleshooting
- Ensure the Ticket ID is valid and exists in the system; otherwise, the update will fail.
- Verify that the authentication credentials (API Token or OAuth2) are correctly configured and have sufficient permissions.
- If the node throws an error about missing required fields, check that all mandatory properties like Ticket ID are provided.
- Network or API errors may occur; check connectivity and API status if requests fail.