Resources · Make integration

SolarWinds Service Desk Make integrationAutomate SolarWinds Service Desk with Make.

Tired of copying tickets and asset records by hand? The SolarWinds Service Desk Make integration gives you 55 modules, including 9 triggers, to move incidents, changes and assets without code. This guide connects your account and walks you through a first working scenario.

Try the SolarWinds Service Desk integration on MakeSee the 55 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SolarWinds Service Desk Make integration automate?

The SolarWinds Service Desk Make integration links your service desk to the other tools your team uses, so records get created, read, updated and removed without anyone retyping them. You build a scenario (the automation itself, a chain of modules) and Make runs it on a schedule. Each module is one brick: a trigger, an action or a search.

Tickets that open themselves. A request typed into a form or an email tool lands in SolarWinds Service Desk through Create an Incident, with the content of the request already mapped. Nobody on the support side copies anything.

A team that hears about problems early. Watch Problems and Watch Changes pick up new records and pass each one on as a bundle (one item flowing from module to module), which a chat or email module can turn into a message for the right people.

An asset register that stays in sync. Watch Hardwares and List Hardwares feed a spreadsheet or an inventory tool, and Update a Hardware writes corrections back the other way.

Two limits to know up front. All 9 triggers are scheduled, none is instant, so Make checks for news at intervals instead of being pinged. And the official documentation for this app is marked as limited, so what you get is the module list, without detailed guides. When a scenario fails, the Make troubleshooting guide helps you read the error.

If you are still choosing a platform, the n8n vs Make comparison lays out the criteria side by side. And to get comfortable with the editor before building for your service desk, Make training covers the basics step by step.

Connect

How do you connect SolarWinds Service Desk to Make?

  1. 01

    Add a SolarWinds Service Desk module

    In your scenario, click the + and search for SolarWinds Service Desk. Pick any of its modules, then click Create a connection. The connection is your service desk account linked to Make once, and every module of the app reuses it.

  2. 02

    Name it and authorize Make

    Give the connection a clear name if you like, such as the name of your instance. Then follow what the window asks: either approve Make on the SolarWinds Service Desk page, or paste the key the app provides.

  3. 03

    Save and check the module

    Click Save. Back in the module, Make can now read your service desk, so the lists you open inside the module should show your own data. If they stay empty, the connection is the first thing to check.

First scenario

Build your first scenario: form requests become incidents

GoalWhen someone submits a request in your form tool, Make opens a matching incident in SolarWinds Service Desk.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. That first module is where the flow starts.

  2. 02

    Start from your form tool

    Search for the app that collects requests, a form builder or an email tool, and pick its trigger for new entries. Create its connection so Make can read the submissions.

  3. 03

    Add Create an Incident

    Click the + on the right of the first module, search for SolarWinds Service Desk and choose Create an Incident. Select the connection you set up earlier.

  4. 04

    Map the request into the incident

    Fill the module by clicking into each box and choosing the matching values from the form entry, box by box. Make shows the data of the previous module as clickable items.

  5. 05

    Test with Run once

    Submit a test entry in your form, then click Run once. Open the bubbles above each module to read the bundles they received, and check the new incident in your service desk.

  6. 06

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which you can change under Scheduling. Then switch the scenario on and let it work.

Triggers

What starts a SolarWinds Service Desk scenario

9 modules start a scenario when something happens in SolarWinds Service Desk. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SolarWinds Service Desk as soon as it happens.

SolarWinds Service Desk1Watch Changes

Watch Changes

Scheduled trigger

In Make“Triggers when a new change is created.”

Each newly created change in SolarWinds Service Desk arrives in your scenario as its own bundle, which means the people affected by a planned change can hear about it without watching the queue themselves.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a change appears in the scenario at the next check, every 15 minutes by default on a new scenario.
When to use it
when the owners of a system should hear about each new change logged against it, through a chat or email module placed right after.
Watch out
the module is described as reacting to new changes; do not rely on it to catch edits made to an existing one.
SolarWinds Service Desk2Watch Contracts

Watch Contracts

Scheduled trigger

In Make“Triggers when a new contract is created.”

New contracts recorded in SolarWinds Service Desk become the starting point of your scenario, so purchasing or finance can receive them without anyone forwarding the details by hand.

How it fires
scheduled. Make checks the app on the scenario's schedule and collects the contracts created since its previous check.
When to use it
to copy each new contract into the spreadsheet or finance tool where renewals are followed, or to tell the budget owner a contract was added.
Watch out
on the Free plan a scheduled scenario cannot run more often than every 15 minutes, which is plenty for contracts but worth knowing before you promise anyone an instant alert.
SolarWinds Service Desk3Watch Hardwares

Watch Hardwares

Scheduled trigger

In Make“Triggers when a new hardware is created.”

This trigger hands every newly registered hardware item to your scenario, giving you a clean hook to keep an inventory sheet or an asset tool aligned with what the service desk knows.

How it fires
scheduled. Make checks the app on the scenario's schedule instead of being notified, and brings back the hardware created since the last check.
When to use it
when new laptops, screens or servers are logged in the service desk and another system has to receive them too.
Watch out
each hardware item that comes in is a bundle, and every module after the trigger spends one operation per bundle, which counts on your plan when a large batch of equipment is registered at once.
SolarWinds Service Desk4Watch Incidents

Watch Incidents

Scheduled trigger

In Make“Triggers when a new incident is created.”

With this trigger, every new incident becomes a bundle your scenario can route somewhere useful: a team channel, an on-call tool, a tracking sheet. It is the most natural entry point of the app.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and on paid plans the interval can go down to 1 minute.
When to use it
when incidents should reach people who do not live in the service desk, like a manager who follows outages from a chat app.
Watch out
scheduled means not instant; for urgent incidents, set the shortest interval your plan allows rather than expecting a push.
SolarWinds Service Desk5Watch Other Assets

Watch Other Assets

Scheduled trigger

In Make“Triggers when a new other asset is created.”

Anything logged as an other asset, the items that are neither hardware nor contracts, can start a scenario the moment Make spots it, so those odd pieces of equipment stop falling through the cracks.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns the other assets created since its last pass.
When to use it
when your team records furniture, licences or accessories as other assets and wants them mirrored in a separate register.
Watch out
hardware has its own trigger, Watch Hardwares, so pick the one that matches how the item is filed in SolarWinds Service Desk or the scenario will stay silent.
SolarWinds Service Desk6Watch Problems

Watch Problems

Scheduled trigger

In Make“Triggers when a new problem is created.”

A problem usually means a root cause behind several incidents, and this trigger lets your scenario react to each new one, for instance by alerting the engineers who investigate recurring issues.

How it fires
scheduled. Make checks the app on the scenario's schedule and brings in the problems created since the previous run.
When to use it
when problem management happens in a separate board or chat channel and new problems should appear there without manual copying.
Watch out
every problem that comes in spends one operation in each module that follows, so keep the flow short if your team logs problems in bulk after a major outage.
SolarWinds Service Desk7Watch Releases

Watch Releases

Scheduled trigger

In Make“Triggers when a new release is created.”

Newly created releases flow into your scenario one by one, which gives you an easy way to announce what is about to ship to the support agents who will field the questions.

How it fires
scheduled. Make checks the app on the scenario's schedule and lists the releases added since the last check, one bundle each.
When to use it
when a release note or a heads-up message has to reach support or product people outside the service desk.
Watch out
the scenario sees a release when it is created, not when it goes live; if timing matters, add a Get a Release step later in the flow to read its current state.
SolarWinds Service Desk8Watch Solutions

Watch Solutions

Scheduled trigger

In Make“Triggers when a new solution is created.”

When someone writes a new solution in SolarWinds Service Desk, this trigger picks it up so you can share the fix beyond the service desk, into a wiki, a help center or a team channel.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns each solution created since the previous check as a separate bundle.
When to use it
when your knowledge base lives in another tool and new solutions should be copied there instead of rewritten.
Watch out
a solution drafted and then corrected will only be caught once, at creation, so review before publishing to a public page.
SolarWinds Service Desk9Watch Users

Watch Users

Scheduled trigger

In Make“Triggers when a new user is created.”

Each new user added to SolarWinds Service Desk can kick off an onboarding flow in Make: a welcome message, an account in another tool, a line in the staff register.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a newcomer shows up in the scenario at the next check rather than the second the account is created.
When to use it
when adding someone to the service desk should also set them up elsewhere, without the admin repeating the work in each tool.
Watch out
the Free plan allows 2 active scenarios, so an onboarding flow like this one can use half of your quota on its own.
Modules

What the SolarWinds Service Desk modules do

SolarWinds Service Desk gives you 46 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SolarWinds Service Desk1

Create a Change

Action

In Make“Creates a new change.”

Logs a new change in SolarWinds Service Desk from data another app already holds, so a planned intervention is recorded formally without anyone filling the form twice.

When to use it
when a deployment tool or a project board decides a change is needed and the service desk must keep the official trace.
Watch out
run the scenario once with test data first, since each run creates a real change.
SolarWinds Service Desk2

Create a Contract

Action

In Make“Creates a new contract.”

Adds a contract record to the service desk straight from a signed deal or a purchase form, which keeps vendor agreements in one place without a separate data entry step.

When to use it
when a contract is approved in your e-signature or purchasing tool and the IT team needs it on file.
Watch out
the module name in Make says Contract even though its internal key mentions a contractor; it is the same module.
SolarWinds Service Desk3

Create a Hardware

Action

In Make“Creates a new hardware.”

Registers a piece of equipment in SolarWinds Service Desk as soon as it exists somewhere else, so your asset inventory grows with each purchase instead of lagging behind.

When to use it
when an order confirmation or a procurement sheet lists new machines that should be tracked by the service desk.
Watch out
if the same order passes through the scenario twice, you get two records; a List Hardwares step before it helps you skip duplicates.
SolarWinds Service Desk4

Create an Incident

Action

In Make“Creates a new incident.”

Opens a new incident in your service desk from any request Make can read: a form entry, an email, a chat message. The ticket appears in the queue with the details already filled.

When to use it
when requests arrive through channels your agents do not watch and should become proper tickets automatically.
Watch out
a scenario that also listens with Watch Incidents and creates incidents can feed itself; keep those two roles in separate flows.
SolarWinds Service Desk5

Create an Other Asset

Action

In Make“Creates a new other asset.”

Records an item that does not fit the hardware category, a licence, a badge, a piece of furniture, as an other asset in the service desk, straight from the tool where it was first noted.

When to use it
when your office or purchasing team logs these items in a sheet and IT wants them in the same asset register.
Watch out
for computers and devices, Create a Hardware is the module that matches.
SolarWinds Service Desk6

Create a Problem

Action

In Make“Creates a new problem.”

Opens a problem record so the root cause behind repeated incidents gets its own follow-up, created from a monitoring alert, a review board or a form your engineers use.

When to use it
when a monitoring tool or an analysis sheet flags a recurring issue that deserves formal investigation in the service desk.
Watch out
if every alert reaches this module, the problem list fills with noise; send only the alerts your team has confirmed.
SolarWinds Service Desk7

Create a Release

Action

In Make“Creates a new release.”

Creates a release in SolarWinds Service Desk from the tool where your team plans versions, which gives support a record of what is coming without a manual handover.

When to use it
when a milestone or a version is set in your project tool and the service desk should track the matching release.
Watch out
test it with Run once on a dummy version first, because every execution adds a real release to your instance.
SolarWinds Service Desk8

Create a Solution

Action

In Make“Creates a new solution.”

Turns a fix written somewhere else, in a wiki page, a shared document or a chat thread, into a solution inside the service desk, where agents can reuse it on the next similar ticket.

When to use it
when your team documents answers outside SolarWinds Service Desk and wants them searchable where tickets are handled.
Watch out
each run adds a real solution your agents will see, so do a Run once on test text before connecting your source.
SolarWinds Service Desk9

Create a User

Action

In Make“Creates a new user.”

Adds a person to SolarWinds Service Desk as soon as they appear in your HR tool or staff directory, so new hires can open tickets from their very first day.

When to use it
when onboarding starts in another system and the service desk account is one of the steps people forget.
Watch out
check whether the person already exists with List Users before this step, otherwise a rerun can try to create the same user twice.
SolarWinds Service Desk10

Delete a Change

Action

In Make“Deletes a change.”

Removes a change record from the service desk, handy for cleaning up changes that were logged by mistake or cancelled in the tool that created them.

When to use it
when a change is withdrawn upstream, in a project or deployment tool, and should not stay in the service desk as if it were still planned.
Watch out
a deletion cannot be undone from Make; only send this module the changes your upstream tool marks as cancelled.
SolarWinds Service Desk11

Delete a Contract

Action

In Make“Deletes a contract.”

Erases a contract from SolarWinds Service Desk, which keeps the list of agreements free of drafts and duplicates that never went anywhere.

When to use it
when a contract created through a scenario turns out to be a test or a duplicate and you want the record gone.
Watch out
an expired contract is often still useful history; delete only what should never have existed, and nothing Make removes can be recovered from the scenario.
SolarWinds Service Desk12

Delete a Hardware

Action

In Make“Deletes a hardware.”

Takes a hardware item out of the service desk inventory, for example the machines that were registered twice or entered with the wrong details.

When to use it
when a cleanup sheet lists equipment records to remove and you would rather not click through each one in the service desk.
Watch out
run it first on a single test item; a mapping error applied to a whole list deletes the wrong machines, with no undo.
SolarWinds Service Desk13

Delete an Incident

Action

In Make“Deletes an incident.”

Deletes an incident outright, which is mostly useful for spam tickets or duplicates that a scenario opened from a noisy inbox or form.

When to use it
when a spam filter or a duplicate check upstream marks a ticket as junk and it should leave the queue entirely.
Watch out
for genuine tickets, Update an Incident is usually the better choice, because a deletion cannot be undone from Make.
SolarWinds Service Desk14

Delete an Other Asset

Action

In Make“Deletes an other asset.”

Removes an other asset from the register, so items that were sold, lost or logged by error stop showing up in your counts.

When to use it
when the office or purchasing sheet that feeds your assets marks an item as gone and the service desk should follow.
Watch out
the deletion is final from Make's side; make sure an empty value from the sheet never reaches this module.
SolarWinds Service Desk15

Delete a Problem

Action

In Make“Deletes a problem.”

Clears a problem record from SolarWinds Service Desk, useful when a scenario created problems too eagerly from alerts that turned out to be noise.

When to use it
when you are cleaning up after testing a problem-creation flow, or when a review confirms a record is a pure duplicate.
Watch out
incidents may already point to that problem; check before deleting, because Make cannot restore it.
SolarWinds Service Desk16

Delete a Release

Action

In Make“Deletes a release.”

Removes a release from the service desk, so a version that was cancelled in your planning tool does not linger as if it were still coming.

When to use it
when a version is dropped upstream and the matching release in SolarWinds Service Desk should disappear with it.
Watch out
a mistaken deletion stays deleted; test with Run once on a fake release before connecting this step to real planning data.
SolarWinds Service Desk17

Delete a Solution

Action

In Make“Deletes a solution.”

Deletes a solution from the knowledge kept in the service desk, which helps retire answers that no longer apply once a system or a process has changed.

When to use it
when the source page of a solution is archived in your wiki and the copy in the service desk should go too.
Watch out
agents lose that answer immediately; if you are unsure, update the solution to mark it outdated rather than removing it.
SolarWinds Service Desk18

Delete a User

Action

In Make“Deletes a user.”

Removes a person from SolarWinds Service Desk, closing the loop when someone leaves the company and their account should not remain open.

When to use it
when offboarding is recorded in your HR tool and the service desk is one of the systems to clean up.
Watch out
tickets and assets may still reference that user; check what depends on the account first, since Make offers no undo.
SolarWinds Service Desk19

Get a Change

Action

In Make“Gets the datails of the change.”

Reads the full details of one change, so the next modules in your scenario can use its current information rather than whatever was known when the flow started.

When to use it
after a trigger or a list returns a change and you need its latest details before posting an update or making a decision.
Watch out
it reads one change at a time; to pull many, List Changes is the module that returns several bundles.
SolarWinds Service Desk20

Get a Contract

Action

In Make“Gets the details of the contract.”

Fetches everything the service desk holds about a single contract, which is what you need to fill a renewal reminder or a finance report with accurate values.

When to use it
when a scenario knows which contract it is dealing with, from a trigger or a previous step, and needs its complete record.
Watch out
map the contract from an earlier module rather than typing it, otherwise the scenario always reads the same record.
SolarWinds Service Desk21

Get a Hardware

Action

In Make“Gets the details of the hardware.”

Pulls the complete record of one hardware item, a real help when a ticket or a spreadsheet only mentions a machine and you need the rest of its details.

When to use it
when an incident refers to a device and your scenario should attach the device information before notifying a technician.
Watch out
a Get reads one item; when a ticket mentions several devices, List Hardwares returns them as separate bundles instead.
SolarWinds Service Desk22

Get an Incident

Action

In Make“Gets the datails of the incident.”

Gives your scenario the current state of one incident, which matters because a ticket can change a lot between the moment it is created and the moment you act on it.

When to use it
right before sending a summary to a client or a manager, so the message reflects the incident as it stands now.
Watch out
the bundle from Watch Incidents is a snapshot taken at the check; add this step when freshness counts.
SolarWinds Service Desk23

Get an Other Asset

Action

In Make“Gets the details of the other asset.”

Returns all the stored details of one other asset, so a scenario handling a licence, a badge or an accessory can work with the full picture instead of a name.

When to use it
when another tool mentions the item and you want to enrich a report or a message with what the service desk knows about it.
Watch out
the module expects to know which asset to read; map it from a previous step so each run targets the right one.
SolarWinds Service Desk24

Get a Problem

Action

In Make“Gets the details of the problem.”

Loads the full record of one problem, useful for building a status update on an investigation or checking where it stands before closing linked work elsewhere.

When to use it
when a scenario reacts to an incident linked to a problem and needs the problem's own details to decide what happens next.
Watch out
each Get costs one operation per bundle; inside a loop over many incidents, that adds up on your plan.
SolarWinds Service Desk25

Get a Release

Action

In Make“Gets the details of the release.”

Reads one release in full, so an announcement or a checklist sent from Make carries the release information as it stands in the service desk right now.

When to use it
when a release was picked up at creation by Watch Releases and you want its updated details before telling support it is ready.
Watch out
Get a Release only reads; to move the release forward, follow it with Update a Release.
SolarWinds Service Desk26

Get a Solution

Action

In Make“Gets the details of the solution.”

Fetches a single solution with its full content, which lets you publish or share the exact fix your agents wrote, not a shortened version.

When to use it
when a scenario copies solutions into a wiki or a help center and needs the complete text for each one.
Watch out
the documentation for this app is limited, so run it once and read the returned bundle to see which details come back before mapping them.
SolarWinds Service Desk27

Get a User

Action

In Make“Gets the details of the user.”

Retrieves the profile of one service desk user, handy to add a name or contact details to a message when the ticket only carries a reference to the person.

When to use it
when a scenario must notify the requester or their manager and first needs to know who that user actually is.
Watch out
to find someone without knowing their record in advance, start with List Users instead.
SolarWinds Service Desk28

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the SolarWinds Service Desk API with the connection you already set up, the way to reach what the listed modules do not cover.

When to use it
when you need an operation or an object that none of the 55 ready-made modules offers.
Watch out
Make's documentation for this app is limited and gives no endpoint list, so you work from the API reference SolarWinds provides.
SolarWinds Service Desk29

Update a Change

Action

In Make“Updates an existing change.”

Writes new information onto an existing change, keeping the service desk record in step with what happens in the tool where the work is actually done.

When to use it
when a deployment or a task moves forward in your project tool and the matching change should reflect it without an agent editing it.
Watch out
it writes to a real change record, so do a Run once on a test change to see what the module writes before connecting live data.
SolarWinds Service Desk30

Update a Contract

Action

In Make“Updates an existing contract.”

Changes the details of a contract already in the service desk, so a renewal or an amendment signed elsewhere shows up on the record your IT team consults.

When to use it
when an e-signature or finance tool records a renewed contract and the service desk entry should be brought up to date.
Watch out
make sure the scenario targets the right contract, mapped from a Get or a List step, and not a hard-typed one.
SolarWinds Service Desk31

Update a Hardware

Action

In Make“Updates an existing hardware.”

Corrects or completes a hardware record, the way to push changes made in an inventory sheet or an asset tool back into SolarWinds Service Desk.

When to use it
when a device changes hands, location or status in another system and your service desk should agree with it.
Watch out
if the same scenario also watches that source, test carefully so an update does not bounce between the two tools.
SolarWinds Service Desk32

Update an Incident

Action

In Make“Updates an existing incident.”

Edits an existing incident from outside the service desk, for example when a customer answers by email or a monitoring alert clears on its own.

When to use it
when progress happens in another tool and the ticket should record it without an agent copying the news across.
Watch out
every run writes to a live ticket your team may be working on, so check the mapping with Run once on a test incident.
SolarWinds Service Desk33

Update an Other Asset

Action

In Make“Updates an existing other asset.”

Changes the stored details of an other asset, keeping licences, badges and accessories accurate in the service desk as they move between people or places.

When to use it
when the sheet or tool where these items are tracked records a change and the register in SolarWinds Service Desk should follow.
Watch out
hardware items are updated with Update a Hardware; this module covers only the other asset category.
SolarWinds Service Desk34

Update a Problem

Action

In Make“Updates an existing problem.”

Brings a problem record up to date from wherever the investigation is happening, so the service desk shows the latest findings without extra typing.

When to use it
when engineers track their root cause analysis in another board and the problem should reflect each step they close.
Watch out
each update spends an operation, so fire it on real milestones of the investigation, not on every comment.
SolarWinds Service Desk35

Update a Release

Action

In Make“Updates an existing release.”

Updates a release already in the service desk, so dates or status set in your planning tool land on the record support looks at.

When to use it
when a version is postponed or confirmed upstream and the release in SolarWinds Service Desk should match without a second edit.
Watch out
run once on a test release to see how the module treats the values you leave blank before touching real ones.
SolarWinds Service Desk36

Update a Solution

Action

In Make“Updates an existing solution.”

Rewrites an existing solution with the latest version of a fix, keeping the service desk knowledge aligned with the wiki or document your team maintains.

When to use it
when the source article of a solution is edited and agents should see the corrected answer on their next ticket.
Watch out
pair it with a Get a Solution or List Solutions step so the scenario edits the solution you mean.
SolarWinds Service Desk37

Update a User

Action

In Make“Updates an existing user.”

Updates the profile of a service desk user, so a new title, department or contact detail entered in your HR tool reaches SolarWinds Service Desk too.

When to use it
when people move teams or change roles and the service desk should route their tickets based on current information.
Watch out
use Get a User or List Users first to target the right person, especially in a company with shared names.
SolarWinds Service Desk38

List Changes

Search

In Make“Lists all changes.”

Returns the changes stored in the service desk, one bundle per change, which is the starting material for a report, a calendar export or a bulk update.

When to use it
when a scenario needs a batch of changes at once, for a report sheet or a cleanup pass.
Watch out
a search can return zero, one or many results, and each module after it runs once per bundle, spending operations accordingly.
SolarWinds Service Desk39

List Contracts

Search

In Make“Lists all contracts.”

Pulls the contracts kept in SolarWinds Service Desk into your scenario, one bundle each, ready to feed a spreadsheet where finance follows renewals.

When to use it
when you want a full export of contracts in another tool, or need to scan them before creating a new one to avoid duplicates.
Watch out
if the list comes back empty, the modules after it do not run; that is expected behavior, not an error.
SolarWinds Service Desk40

List Hardwares

Search

In Make“Lists all hardwares.”

Brings back the hardware records of your service desk as separate bundles, a straightforward way to rebuild an inventory sheet or compare it with another source.

When to use it
when an audit or an asset reconciliation needs every device in one place, or before Create a Hardware to check the machine is not there already.
Watch out
a large inventory means many bundles, and every module that follows spends one operation for each.
SolarWinds Service Desk41

List Incidents

Search

In Make“Lists all incidents.”

Pulls the incidents already sitting in SolarWinds Service Desk into your scenario, each one arriving as its own bundle (one item passed to the next module). The next modules can then sort, copy or report on them.

When to use it
pick it to process the incidents that exist today; Watch Incidents only catches the new ones created after the scenario starts.
Watch out
the search can return zero, one or many bundles, and every later module spends one operation per bundle, so check the count after Run once.
SolarWinds Service Desk42

List Other Assets

Search

In Make“Lists all other assets.”

Hands your scenario the full set of other assets recorded in the service desk, the items that are neither hardware nor contracts. That gives an inventory feed you can push into a sheet, a report or a second tool without exporting anything by hand.

When to use it
choose it when you need many assets at once; Get an Other Asset fits better when you already hold one ID.
Watch out
an empty result simply stops the chain, so run the scenario once and read the bundles before adding the next modules.
SolarWinds Service Desk43

List Problems

Search

In Make“Lists all problems.”

Brings back the problem records your team has logged, so a scenario can review root causes in bulk rather than one ticket at a time. Each problem lands as a separate bundle ready to be mapped into a summary or another app.

When to use it
reach for it when a team review or a dashboard needs every open problem, not just the latest one caught by Watch Problems.
Watch out
Make documents little about this app, so open the bundles after Run once to see which details really come back.
SolarWinds Service Desk44

List Releases

Search

In Make“Lists all releases.”

Collects the releases planned or shipped in SolarWinds Service Desk and feeds them into the scenario one bundle at a time. Release managers get a single place to build a changelog, a status page update or a notification per release.

When to use it
use it to act on existing releases; for a single release you already know, Get a Release costs fewer operations.
Watch out
each returned release triggers one operation in every module that follows, which adds up fast on the Free plan.
SolarWinds Service Desk45

List Solutions

Search

In Make“Lists all solutions.”

Retrieves the knowledge base solutions stored in the service desk, so you can reuse proven fixes outside the tool. Each solution becomes a bundle you can copy into a wiki, a chatbot source or a shared document.

When to use it
choose it to sync or audit the whole solution library; Watch Solutions suits a flow that only reacts to newly written articles.
Watch out
Make documents this app only partly, so test with Run once and check how many bundles arrive before mapping them.
SolarWinds Service Desk46

List Users

Search

In Make“Lists all users.”

Returns the people registered in SolarWinds Service Desk as a stream of bundles, one per user. IT and HR teams can use it to compare the service desk roster with the company directory and spot accounts that should not be there.

When to use it
run it for a bulk check of accounts; Get a User is the right module once you know exactly which person to look up.
Watch out
feeding this list straight into Delete a User removes every returned account, so place a filter between the two modules.
Need help

Need help automating SolarWinds Service Desk with Make?

A person reads every message.

FAQ

SolarWinds Service Desk and Make: common questions

01Is the SolarWinds Service Desk Make integration free?
Yes, the app is a standard app, available from the Make Free plan. The Free plan has limits you will feel quickly on a service desk: 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the minimum interval down to 1 minute, remove the cap on active scenarios and count usage in operations per month. Your SolarWinds Service Desk subscription is a separate matter.
02What do you need to connect SolarWinds Service Desk to Make?
You need a SolarWinds Service Desk account and a Make account. The official documentation gives no specific prerequisites for this app, so the generic Make flow applies: add one of its modules, click Create a connection, name the connection if you want, then either authorize Make on the SolarWinds Service Desk page or paste the key the app gives you, and save. Every SolarWinds Service Desk module in your scenarios then reuses that same connection.
03Do SolarWinds Service Desk triggers in Make work in real time?
No. All 9 SolarWinds Service Desk triggers are scheduled, none is instant. Make checks the app on the scenario's schedule and picks up the new records created since the last check. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans let you go down to 1 minute, which gets close to immediate for most incident alerts without being a true push.
04What if a SolarWinds Service Desk module is missing in Make?
Use Make an API Call. It calls any endpoint of the SolarWinds Service Desk API with the connection you already have, so an operation missing from the 55 modules is still within reach. Keep in mind that Make's documentation for this app is marked as limited, with no detailed guides, so you will build that call from the API reference SolarWinds publishes. If that is too technical for your team, look for the same result with the existing create, get, update and list modules.
05Should you use Make or n8n for SolarWinds Service Desk?
It depends on your team rather than on the app. Make covers SolarWinds Service Desk with 55 ready-made modules, 9 scheduled triggers and a Make an API Call module for the rest, all built visually with a guided editor. n8n often has a node for the same app, so check whether it exists before choosing. If your team already runs its other automations in one of the two tools, staying there usually keeps things simpler to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations