Actions19
Overview
The node integrates with the Syncro RMM API to update an existing ticket by its ID. It allows users to modify various ticket attributes such as asset association, assigned contact, issue type, status, customer, and subject. This is useful in IT service management workflows where tickets need to be programmatically updated based on external triggers or automation rules.
Practical examples include:
- Automatically updating ticket status when a related monitoring alert changes.
- Assigning tickets to specific contacts based on incoming data.
- Changing the issue type or subject of a ticket after processing input from other systems.
Properties
| Name | Meaning |
|---|---|
| Ticket ID | The unique identifier of the ticket to update. |
| Additional Fields | A collection of optional fields to update on the ticket: |
| - Asset ID | The ID of the asset associated with the ticket. |
| - Assign to Contact | The ID of the contact to whom the ticket should be assigned. |
| - Issue Type Name or ID | The issue type for the ticket, selectable from a list or specified by ID/expression. |
| - Status Name or ID | The status of the ticket, selectable from a list or specified by ID/expression. |
| - Customer ID | The ID of the customer related to the ticket. |
| - Subject | The subject/title of the ticket. |
Output
The node outputs JSON data representing the updated ticket object returned by the Syncro RMM API. This typically includes all ticket details after the update operation, reflecting the new state of the ticket.
If the API supports binary data (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON ticket data.
Dependencies
- Requires an API key credential for authenticating with the Syncro RMM API.
- Needs the Syncro RMM subdomain configured in credentials to form the base URL.
- Relies on the Syncro RMM API endpoints for ticket updates.
- No additional external services are required beyond the Syncro RMM API.
Troubleshooting
- Invalid API Key: If the API key is incorrect or expired, the node will fail authentication. Ensure the API key credential is valid and has appropriate permissions.
- Ticket Not Found: Providing an invalid or non-existent Ticket ID will result in errors. Verify the Ticket ID before running the node.
- Invalid Field Values: Using unsupported or incorrectly formatted values for fields like status or issue type may cause API errors. Use the provided options lists or valid IDs.
- Network Issues: Connectivity problems to the Syncro RMM API endpoint can cause failures. Check network access and API availability.
Links and References
- Syncro RMM API Documentation (for detailed API usage)
- n8n Expressions Documentation (for using expressions in property values)