Create ticket for duplicate devices in Syncro
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs on a schedule (every 2 weeks). Along the way it connects Syncrormm (community).
How it runs
Trigger: On a schedule (every 2 weeks).
- Get all assets (Syncro Rmm): work with asset
- Exclude VMs (Filter): keeps only the items that match a condition
- Create labeled link field (Edit Fields (Set)): sets 1 field: link_label
- Count by serial number (Summarize): summarizes / groups the items
- Get only duplicate serials (Filter): keeps only the items that match a condition
- Format ticket comment (Code): runs custom JavaScript code
- Create a ticket (Syncro Rmm): create (ticket)
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-syncrormm is verified or supports 3.0 (used in Get all assets, Create a ticket).
Nodes used (6)
- Syncro Rmm
n8n-nodes-syncrormm.syncroRmm - Filter
n8n-nodes-base.filter - Summarize
n8n-nodes-base.summarize - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code
From the author
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Using the serial number for assets, this workflow will create a ticket with the subject "Found duplicate Serial Numbers" with a list of all of the duplicate…