All integrationsDevice Management

Kaseya VSA

Work with Kaseya VSA remote monitoring and management: find agents, assets, organizations and machine groups, read and close alarms, run or schedule agent procedures, check patches and audits, work Service Desk tickets, and start workflows on new alarms, offline or new agents, new or changed tickets and finished agent procedures.

actions
25
triggers
6

Triggers

Start a workflow when something happens in Kaseya VSA.

  • New alarmRuns when VSA raises an alarm, with its subject, the agent it is about and when it happened. Alarms already there when the workflow is turned on don't start it. How often it checks follows your workspace plan.
  • Agent went offlineRuns when an agent goes offline, with its machine, group and when it last checked in. Agents already offline when the workflow is turned on don't start it, and an agent starts it again each time it goes offline. How often it checks follows your workspace plan.
  • New agentRuns when a new agent checks in to VSA for the first time, with its machine, group and operating system. Agents already there when the workflow is turned on don't start it. How often it checks follows your workspace plan.
  • New ticketRuns when a ticket is opened in a Service Desk desk, with its summary, status, priority and submitter. Tickets already there when the workflow is turned on don't start it. How often it checks follows your workspace plan.
  • Ticket changedRuns when a ticket in a Service Desk desk changes, such as its status, priority or assignee, and when one is opened. Changes made before the workflow is turned on don't start it. How often it checks follows your workspace plan.
  • Agent procedure finishedRuns when an agent procedure finishes on an agent, with how it went and who ran it. Runs that finished before the workflow is turned on don't start it. How often it checks follows your workspace plan.

Actions

Steps a workflow can run in Kaseya VSA.

  • Get current userGet the VSA user the connection signs in as: name, email and when the account was created.
  • List usersList VSA's users (the technicians who sign in to VSA), with their names, emails, roles and scopes.
  • List organizationsList the organizations (your customers, and your own) the connected user's scope can see.
  • List machine groupsList machine groups, for every organization or for one.
  • List agentsList agents (managed machines) by organization, machine group, status or name, with their operating system, IP address, current user and last check-in.
  • Get agentGet one agent: its machine, operating system, network, who is signed in, whether it is online and when it last checked in.
  • List assetsList assets: machines with agents and devices VSA found on the network, with their alarm and ticket counts.
  • Get assetGet one asset's hardware details: BIOS, processors, memory, drives and network addresses.
  • List alarmsList alarms, open and closed, newest first, for every agent or one, optionally between two times.
  • Get alarmGet one alarm: what raised it, its message, the agent it is about, whether it is open and any ticket made from it.
  • Close alarmClose an alarm, as a technician does once it's dealt with, with a note saying why.
  • List agent proceduresList the agent procedures (VSA's scripts) the connected user can see, with their folders.
  • Run agent procedureRun an agent procedure on one agent's machine now. Use 'List agent procedure history' to see how it went.
  • Schedule agent procedureSchedule an agent procedure on one agent's machine, once or repeating, optionally skipping it or waking the machine if it is offline.
  • List agent procedure historyList when each agent procedure last ran on an agent, how it went (Success or Failed) and who ran it, latest first.
  • Get patch statusGet an agent's patch status: when it was last scanned, when the next scan and update run, and its reboot settings.
  • List missing patchesList the patches an agent's machine is missing, from its latest patch scan, with their KB articles.
  • Run patch scanScan an agent's machine for missing patches now. 'List missing patches' shows what it found once it finishes.
  • Get audit summaryGet an agent's latest audit: make, model and serial number, network, chassis, BIOS and check-in times.
  • List service desksList the Service Desk desks the connected user can see.
  • List ticketsList a service desk's tickets, newest first, by status, priority, summary or when they were opened or last changed.
  • Get ticketGet one Service Desk ticket with its status, priority, assignee, submitter, dates and every note.
  • Create ticketOpen a ticket in a service desk with a summary and description, optionally its priority, status, category and submitter.
  • Update ticketChange a ticket's status or priority, or assign it to a staff member. What you leave empty stays as it is.
  • Add ticket noteAdd a note to a ticket, shown to the submitter or hidden for technicians only.

Automate Kaseya VSA with Lodol.

Connect Kaseya VSA, then hand Lodol the job in Slack, Claude or ChatGPT.

We’re letting people in a few at a time.