Syncro + Zendesk: catch duplicate assets before billing

Your asset list looks fine. Until it doesn’t. Duplicate serial numbers creep in, counts get inflated, and the next invoice turns into a “why are we paying for this?” email thread.

This Syncro Zendesk automation hits MSP owners and ops leads first, but the helpdesk team and finance feel the fallout too. When duplicates are caught early, you keep billing clean, tech time focused, and customer trust intact.

This workflow scans Syncro assets on a schedule, spots duplicate serials, and creates a review ticket so a technician can merge or clean up the records before billing happens.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Syncro + Zendesk: catch duplicate assets before billing

Click to explore

flowchart LR

    subgraph sg0["Schedule Flow"]
        direction LR
        n0@{ icon: "mdi:cog", form: "rounded", label: "Get all assets", pos: "b", h: 48 }
        n1@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Get only duplicate serials", pos: "b", h: 48 }
        n2@{ icon: "mdi:cog", form: "rounded", label: "Count by serial number", pos: "b", h: 48 }
        n3@{ icon: "mdi:cog", form: "rounded", label: "Create a ticket", pos: "b", h: 48 }
        n4@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
        n5@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Exclude VMs", pos: "b", h: 48 }
        n6@{ icon: "mdi:swap-vertical", form: "rounded", label: "Create labeled link field", pos: "b", h: 48 }
        n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Format ticket comment"]
        n5 --> n6
        n0 --> n5
        n4 --> n0
        n7 --> n3
        n2 --> n1
        n6 --> n2
        n1 --> n7
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n4 trigger
    class n1,n5 decision
    class n7 code
    classDef customIcon fill:none,stroke:none
    class n7 customIcon

The Problem: Duplicate serials quietly break billing

Duplicate assets aren’t loud. They’re subtle, and honestly that’s why they’re so expensive. A tech adds an asset during onboarding, another tech adds the “same” device during a later ticket, and suddenly one physical item exists twice in Syncro. If you bill based on asset count, you can overbill without realizing it. If you don’t bill on count, it still hurts because the device history is split across multiple records, which makes troubleshooting slower and audits messy.

The friction compounds. Not because one duplicate exists, but because nobody notices until the worst moment.

Invoice reviews turn into manual detective work across customers, asset types, and serial fields.
Techs waste about 10 minutes per ticket jumping between duplicate asset histories.
Customers dispute charges, and your team has to “prove” what’s real with screenshots and exports.
Even a small pile of duplicates makes reporting unreliable, so you stop trusting your own numbers.

The Solution: Scheduled duplicate detection with a review ticket

This workflow runs on a schedule and pulls your full asset list from Syncro. It filters out assets you don’t want included (like VMs), then rebuilds each record into a consistent “label” that’s easy to scan in a ticket. After that, it groups assets by key fields (customer ID, asset type, and serial number) and flags any serial numbers that appear more than once. Finally, it composes a clean, technician-friendly comment listing the duplicates and creates a support ticket for review so someone can merge or fix the records before billing gets touched.

The workflow starts with a scheduled trigger. Syncro assets are retrieved, filtered, and summarized so duplicates pop out immediately. Then a ticket is generated with the subject “Found duplicate Serial Numbers” and the full list included for fast cleanup.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Pulls all Syncro asset records on a set schedule.
Filters out non-relevant asset categories (like VM assets) so your list stays meaningful.
Groups assets by customer, type, and serial to detect duplicates automatically.
Creates a ticket with a readable list of duplicates for technician review.

Save about 2 hours per billing cycle that usually goes to exports and spot checks.
Fewer billing disputes because duplicate-count inflation gets caught early.
Cleaner asset history, so techs spend less time guessing which record is “the real one.”
More reliable asset reporting when you’re planning renewals, audits, or QBRs.
A repeatable weekly or monthly quality check that doesn’t depend on one careful person.

Example: What This Looks Like

Say you manage 600 assets across a few dozen customers and you run a billing review once a month. Manually, it’s common to export assets, sort by serial, then double-check customer and type when something looks odd. That’s easily about 2 hours, plus context switching. With this workflow, you spend maybe 5 minutes skimming the ticket and assigning cleanup, because the duplicates are already grouped and listed. You still do the merge by hand (Syncro API limitation), but the hunting is gone.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Syncro RMM community node to retrieve assets and create tickets.
Syncro account to access asset records and customers.
Syncro API key (get it from Syncro’s API settings, with asset permissions)

Skill level: Intermediate. You’ll connect Syncro credentials and adjust one ticket field (customer ID) safely.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A scheduled run kicks it off. You decide the cadence (weekly is common, monthly also works if you only bill monthly). n8n starts the workflow automatically so this doesn’t rely on someone remembering.

Assets are pulled from Syncro and cleaned up. The workflow retrieves asset records, then filters out items you don’t want to include in the check (for example, VM assets that can legitimately share patterns that look like duplicates).

The duplicates are detected in plain logic. A “link label” is built so each asset is easy to identify, then assets are summarized by customer ID, asset type, and serial number. Anything with a serial count above one is kept.

A support ticket is generated for review. n8n composes a comment that lists the duplicate assets and creates a ticket with the subject “Found duplicate Serial Numbers,” which gives your technician a single place to work from.

You can easily modify the schedule and the filtering rules to match how you track assets. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Trigger

Set up the workflow to run automatically on a defined schedule.

Add and open Scheduled Run Trigger.
Set the schedule rule to run every 2 weeks by configuring Rule → Interval with Field set to weeks and Weeks Interval set to 2.
Ensure Scheduled Run Trigger connects to Retrieve Asset Records.

Step 2: Connect Syncro RMM

Pull all asset records from Syncro RMM as the workflow’s data source.

Add and open Retrieve Asset Records.
Credential Required: Connect your syncroRmmApi credentials.
Set Resource to asset.
Enable Return All by setting it to true.
Confirm Retrieve Asset Records outputs to Filter Non-VM Assets.

Step 3: Set Up Asset Filtering and Label Building

Exclude virtual devices and prepare link labels used in duplicate detection.

Open Filter Non-VM Assets and set the following conditions:
Condition 1: Left Value {{ $json.properties.form_factor }} notEquals Virtual Server.
Condition 2: Left Value {{ $json.properties.form_factor }} notEquals Virtual Desktop.
Condition 3: Left Value {{ $json.asset_serial }} notEmpty null.
Open Build Link Label and set Include to selected.
Set Include Fields to id, customer_id, asset_serial, asset_type, properties. and enable Include Other Fields.
Add an assignment with Name link_label, Type object, and Value {{ { name: $json.name, link: $json.external_rmm_link } }}.

If your asset records don’t include external_rmm_link, update the Syncro API fields or adjust the link_label mapping in Build Link Label.

Step 4: Set Up Duplicate Detection and Comment Composition

Group assets by serial number and build a detailed ticket comment for duplicates.

Open Group by Serial Count and set Fields to Split By to customer_id, asset_type, asset_serial.
In Fields to Summarize, add id and link_label with Aggregation set to append.
Open Keep Duplicate Serials and set the condition to Left Value {{ $json.count_id }} gt 1.
Open Compose Ticket Comment and paste the provided JavaScript in JS Code to generate the formatted comment.

⚠️ Common Pitfall: The comment builder expects an appended_link_label array from Group by Serial Count. If your summarized field name differs, update the code in Compose Ticket Comment.

Step 5: Configure Output Ticket Creation

Create a Syncro support ticket that contains the duplicate asset report.

Open Generate Support Ticket.
Credential Required: Connect your syncroRmmApi credentials.
Set Resource to ticket and Operation to create.
Set Subject to Found duplicate Serial Numbers.
Set Additional Fields → Status to New and Issue Type to Maintenance.
Set Additional Fields → Comment to {{ $json.comment }} followed by Ticket created automatically by n8n.
Leave Customer ID empty if Syncro should auto-assign; otherwise provide a valid ID.

Step 6: Test and Activate Your Workflow

Verify the workflow output and then activate it for scheduled runs.

Click Execute Workflow to run the process manually.
Confirm that Generate Support Ticket creates a ticket with a formatted duplicate serial list.
If no duplicates exist, expect no ticket creation or an empty result from Keep Duplicate Serials.
Enable the workflow by toggling Active to run every two weeks as defined in Scheduled Run Trigger.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Syncro RMM API credentials can expire or lack the right permissions. If the workflow suddenly pulls zero assets, check your Syncro API key permissions in Syncro first.
If you add a Wait node or your Syncro tenant is slow during peak hours, processing times vary. Bump the wait duration if downstream steps run before the asset list is fully returned.
The ticket comment format matters more than you’d think. If your “Compose Ticket Comment” logic is too dense, techs will ignore it, so keep the output scannable and include links/labels early.

Frequently Asked Questions

How long does it take to set up this Syncro Zendesk automation?

About 30 minutes once your Syncro API key is ready.

Do I need coding skills to automate duplicate asset detection?

No. You’ll mostly connect Syncro and adjust a couple of fields. The only “code” piece is already written inside the workflow.

Is n8n free to use for this Syncro Zendesk automation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Syncro API access and the Syncro RMM community node requirement (self-hosted for compatibility).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this Syncro Zendesk automation workflow for different asset rules?

Yes, but you’ll do it by changing the filtering and grouping logic, not by “auto-merging.” Common tweaks include updating the “Filter Non-VM Assets” node to match your asset types, changing the “Group by Serial Count” fields if your serials live in a custom field, and rewriting the “Compose Ticket Comment” output so techs get a cleaner checklist.

Why is my Syncro connection failing in this workflow?

Usually it’s an API key issue. Regenerate your Syncro API key, confirm it has permissions to read assets and create tickets, then update the credentials in n8n. If it fails only on large pulls, it can also be rate limiting or timeouts, so try running it off-hours or add a small delay between requests.

How many assets can this Syncro Zendesk automation handle?

Thousands, as long as your n8n host has enough memory and the Syncro API responds reliably.

Is this Syncro Zendesk automation better than using Zapier or Make?

Often, yes, for one reason: the Syncro RMM community node requirement means you’ll typically run this self-hosted, which Zapier and Make won’t help with. n8n also handles grouping and filtering in a way that’s easier to audit when billing is involved. That said, if you only need a basic “send me an alert” flow, Zapier or Make can be quicker to spin up. This workflow is about repeatable data hygiene, not a one-off notification. Talk to an automation expert if you want help picking the cleanest approach for your stack.

Duplicate assets are a small data problem with big consequences. Set this up once, keep your asset history clean, and walk into billing week with fewer surprises.

Syncro + Zendesk: catch duplicate assets before billing

How This Automation Works

n8n Workflow Template: Syncro + Zendesk: catch duplicate assets before billing

The Problem: Duplicate serials quietly break billing