Syncro RMM icon

Syncro RMM

Work with the Syncro RMM API
Join our community

Actions19

Overview

This node integrates with the Syncro RMM API to create a new support ticket within the system. It is useful for automating ticket creation workflows, such as when an issue is detected in monitoring or when customer requests come from other platforms. For example, you could use this node to automatically open a ticket for a customer when an alert triggers or when a service request is received via email.

Properties

Name Meaning
Customer ID The unique identifier of the customer for whom the ticket is being created. (Required)
Subject The subject or title of the ticket describing the issue or request. (Required)
Additional Fields Optional extra details to specify on the ticket:
- Asset ID Identifier of the asset related to the ticket.
- Assign to Contact The ID of the contact person to assign the ticket to.
- Issue Type Name or ID The type/category of the issue, selectable from predefined options or specified by ID.
- Status Name or ID The current status of the ticket, selectable from predefined options or specified by ID.
- Comment A comment or note to add to the ticket.

Output

The node outputs JSON data representing the newly created ticket object as returned by the Syncro RMM API. This typically includes fields such as ticket ID, subject, status, assigned contact, timestamps, and any other metadata provided by the API. The output does not include binary data.

Dependencies

  • Requires an active Syncro RMM account.
  • Needs an API key credential configured in n8n for authentication.
  • The node uses the Syncro RMM API endpoint based on the user's subdomain.
  • Network access to the Syncro RMM API is necessary.

Troubleshooting

  • Invalid API Key: If the API key is incorrect or expired, the node will fail authentication. Ensure the API key is valid and has sufficient permissions.
  • Missing Required Fields: The node requires Customer ID and Subject. Omitting these will cause errors.
  • Incorrect IDs for Additional Fields: Providing invalid asset, contact, issue type, or status IDs may result in API errors. Use the load options or verify IDs beforehand.
  • API Rate Limits or Downtime: Temporary failures might occur due to API limits or service outages; retry after some time.
  • Error Messages: Authentication errors typically mention invalid credentials; validation errors indicate missing or malformed input fields.

Links and References

Discussion