Actions11
Overview
This node interacts with the PerfexCRM API to update an existing support ticket. It allows users to modify various ticket attributes such as subject, department, priority, status, message content, and assigned staff member. This is useful in scenarios where ticket details need to be changed after creation, for example, reassigning a ticket to a different department or updating its priority based on new information.
Practical examples include:
- Changing the priority of a ticket from "Medium" to "High" when an issue becomes urgent.
- Updating the ticket status to "In Progress" when work begins.
- Assigning the ticket to a specific staff member for resolution.
- Modifying the subject or adding additional messages to clarify the issue.
Properties
| Name | Meaning |
|---|---|
| Ticket ID | The unique identifier of the ticket to update. |
| Update Fields | A collection of fields to update on the ticket. Options include: |
| - Subject: The ticket's subject/title. | |
| - Department: The ID of the department responsible for the ticket. | |
| - Priority: The urgency level of the ticket. Possible values: Low, Medium, High, Urgent. | |
| - Status: The current state of the ticket. Possible values: Open, In Progress, Answered, On Hold, Closed. | |
| - Message: Text content or update message related to the ticket. | |
| - Assigned: Staff ID to whom the ticket is assigned. |
Output
The node outputs the updated ticket data as JSON. The structure corresponds to the response returned by the PerfexCRM API after successfully updating the ticket. It typically includes all ticket properties such as ID, subject, department, priority, status, messages, assigned staff, timestamps, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the PerfexCRM API.
- The node configuration must include the base URL and API version of the PerfexCRM instance.
- Network access to the PerfexCRM API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Ticket ID will cause the update request to fail.
- Providing invalid values for fields like priority or status may result in API errors.
- Network connectivity problems can prevent successful API calls.
- Insufficient permissions associated with the API key may block updates.
Error messages and resolutions:
- "Ticket not found": Verify that the Ticket ID is correct and exists in the system.
- "Unauthorized" or "Authentication failed": Check that the API key credential is valid and has proper permissions.
- "Invalid field value": Ensure that all update fields conform to expected types and allowed options.
- Timeout or network errors: Confirm network connectivity and API endpoint availability.
Links and References
- PerfexCRM API Documentation (official API docs for reference)
- n8n Documentation (for general node usage and credential setup)