SyncroMSP n8n integrationAutomate SyncroMSP with n8n.

Adds a new contact record in SyncroMSP and attaches it to an existing customer account.

• Customer ID: the only required field, the SyncroMSP identifier of the account the contact belongs to, an ID rather than a company name. Coming from an earlier node it takes the expression form {{ $json.field }}.
• Email: optional, filled in the name@email.com shape shown in the field.
• Additional Fields: an optional collection holding Address, Name, Notes and Phone, added one by one.

Removes one contact from SyncroMSP, targeted by its identifier, and nothing else.

• Contact ID: required. The field is documented as deleting a specific contact by ID, so it wants the identifier, not a person's name or address.

Reads a single contact back from SyncroMSP so the rest of the workflow has something to work with.

• Contact ID: required, described as getting a specific contact by ID. One identifier in, one contact out.

Lists contacts from SyncroMSP as separate items, ready to loop over or dump somewhere.

• Return All: on, n8n keeps requesting pages until every contact has come through. Off, it stops early.
• Limit: the ceiling on how many contacts come back when Return All stays off.

Edits an existing contact, changing only the fields you add to the update collection.

• Contact ID: the contact to edit. Worth knowing that the node does not flag it as required, so an empty value will not stop the execution the way a required field would.
• Update Fields: an optional collection of 6 entries, Address, Customer ID, Email, Name, Notes and Phone.

Opens a new customer account in SyncroMSP, the record everything else hangs off.

• Email: sits outside the collection, optional, in the name@email.com shape.
• Additional Fields: 11 optional entries including Business Name, First Name, Last Name, Phone, Invoice Emails and Notification Email.
• Referred By: inside that collection, the source the customer came from, such as Linkedin, Google or another customer's name.

Deletes a customer account from SyncroMSP, addressed by identifier.

• Customer ID: required, documented as deleting a specific customer by ID.

Fetches one customer account and hands the record to the following node.

• Cutomer ID: required, and yes, that is how the label is spelled in the node. It is described as getting a specific customer by ID.

Returns the customer list, with filters that narrow it before anything leaves SyncroMSP.

• Return All: on, every page of customers is retrieved; off, Limit caps how many come back.
• Search Query: free text matched against customer data such as a name, in the John Doe shape.
• Sort: the customer field to order by, written like firstname ASC or city DESC.

Pushes changes onto an existing customer account, field by field.

• Customer ID: names the account to edit, and like the contact equivalent it is not marked required by the node.
• Update Fields: 12 optional entries, among them Business Name, Email, Phone, Notes, Get SMS and No Email.

Registers an RMM alert in SyncroMSP from something your monitoring noticed elsewhere.

• Asset ID, Customer ID and Description: three text fields, all optional on this operation, so nothing blocks the execution if one stays empty.
• Additional Fields: holds Resolved, a true or false switch.

Drops an RMM alert from SyncroMSP for good, one identifier at a time.

• RMM Alert ID: required, described as deleting the RMM alert by ID.

Reads one RMM alert back, so a decision downstream rests on the record itself.

• RMM Alert ID: required, documented as getting a specific RMM alert by ID.

Sweeps the RMM alert list, optionally narrowed to one state.

• Return All: on, n8n pages through every alert; off, Limit sets the maximum returned.
• Status: a filter with three choices, active, all and resolved.

Silences an RMM alert for a chosen stretch of time, without removing it.

• RMM Alert ID: required, described as muting the RMM alert by ID.
• Mute Period: how long the silence lasts, picked from 1-hour, 1-day, 2-days, 1-week, 2-weeks, 1-month or forever.

Files a new ticket in SyncroMSP against a customer account.

• Customer ID and Subject: both required, the account the ticket belongs to and the line that names the job.
• Additional Fields: optional, with Asset ID, Assign to Contact (the ID of the contact the ticket goes to), Issue Type and Status.
• Issue Type: chosen from Contract Work, Network Project, Other, Regular Maintenance or Remote Support.

Erases a ticket from SyncroMSP once you hand it the right identifier.

• Ticket ID: required, so an empty value stops the node before it calls SyncroMSP at all.

Pulls a single ticket out of SyncroMSP for whatever comes next in the workflow.

• Ticket ID: the ticket to read. Unlike the delete and update operations, the node does not mark it required here, which is easy to miss when a mapped expression silently resolves to nothing.

Scans the ticket queue and returns one item per ticket, filtered if you ask.

• Return All: on, every page of tickets comes back; off, Limit decides how many.
• Search Query: free text matched against ticket data such as a user, in the John Doe shape.
• Status: one of New, In Progress, Scheduled, Customer Reply, Waiting for Parts, Waiting on Customer or Resolved.

Moves a ticket along, rewriting only the fields you put in the update collection.

• Ticket ID: required, the ticket being changed.
• Update Fields: 7 optional entries, Asset ID, Assign to Contact, Customer ID, Due Date, Issue Type, Status and Subject.
• Due Date: a date and time value, so a calculated deadline maps cleanly into it.