Solarwinds (N Able) N-Central Integration

Integrate your PSA to your Powerful RMM



Please Note: This integration is part of the MSP Add-On. Head here to learn more: MSP Add-On  

Our integration maps your N-Central devices and alerts into Customers, Tickets, and RMM Alerts, allowing you to reduce double data entry in the systems you already use.

What the Integration Does

  • Map N-Central "Customers" to RepairShopr "Customers"
  • Map N-Central "Devices" to RepairShopr "Assets"
  • Feeds alerts/checks into RepairShopr for one-click Ticket creation or clearing
  • Automatically creates Assets when you add Devices
  • Continually updates assets with machine names, serial numbers, etc
  • Creates RepairShopr "Customers" if one does not already exist for the N-Central Customer. 

What the Integration Doesn't Do

  • Create RMM alerts in RepairShopr for tickets generated manually within N-Central.

Setup Walkthrough

Step 1


Go to your N-Central account and head to "Administration" -> "PSA Integration".

Here, you should find 3 sections.  You will want to start with "Configure PSA Integration".

The "PSA Configuration Settings" should be set to "Custom PSA", the "Delivery Mechanism for Tickets" should be set to "Generate Tickets via Email", and the "Ticketing Errors" should be set to your email address".  Once you have this setup, you can turn on the PSA Integration in N-Central. 


Once you do that, you can head back to the Solarwinds MSP/N-Central app card in RepairShopr.  Here, you will want to copy/paste your N-Central host formatted like this: "https://nce123.n-able.com". 

For the Username and Password, you will want to use your admin's Solarwinds/N-Central login credentials.  Do NOT use the "API CREDENTIALS FOR COMMUNICATING WITH MSP N-CENTRAL" found in the settings mentioned above.  They will not work. 


On the "Customer Settings" page of the PSA Integration area, you can easily "Enable All" of your customers to send data over to RepairShopr if you want.


Next page, "Ticketing". You need to enter your inbound email alias here because they are technically sending the tickets over as emails that we will read and process.

Be sure you put your inbound alias in there properly, it's safe to use "SUBDOMAIN@reply.repairshopr.com" here even if you use mailboxes/etc. 


Step 2


Ok, now that you have the N-Central side done, you can import and map your customers. 

Click the Import button, give it a second, and then head to the Mapping link.



Step 3


Map your N-Central Customers to RepairShopr Customers by clicking this blue icon for each that we didn't automatically detect. This will make it so the assets and alerts are attached to the right customer. (We'll automatically try to match on some fields, but you might need to fix some of them)



Step 4


Now you will start getting alerts using the Notification Center in RepairShopr. You can adjust how and when you are alerted, head to Admin -> Notification Center to find the new rule that we created.



Clicking edit there will show you the new rules that will be working for you



Now that you are all configured, you can take a moment to check out the new button on the Tickets page

Tickets -> "N-Central Alerts"

Clicking that takes you to the "RMM Alerts" page where you will see alerts rolling in

Next to alerts you'll be able to map them to a customer if they are connected to a N-Central Customer that isn't mapped, you can view the details of the alert, and also convert the alert to a "Ticket"



And, last but not least, on the Customers -> Assets page you'll see all the devices from N-Central populated with serial numbers and much of the important data from N-Central. 


Troubleshooting


Let us know if you find any issues!



Feedback and Knowledge Base