All integrationsDevice Management

Atera

Run your Atera help desk and monitoring: open, update and comment on tickets and log time, manage customers and contacts, raise and resolve alerts, and read your devices, with triggers for new and changed tickets, replies, alerts, customers, contacts and devices going offline.

actions
25
triggers
13

Triggers

Start a workflow when something happens in Atera.

  • New ticketRuns for each new Atera ticket, with its title, what was first written, the end user and customer, status, priority and assigned technician. It can run only for one customer or one priority. What was already there when the workflow is turned on doesn't start it. How often it checks follows your workspace plan.
  • Ticket updatedRuns each time an Atera ticket changes: its title, status, priority, impact, type, end user or technician, or a new comment. It can run only for one customer's tickets. New tickets start 'New ticket' instead. How often it checks follows your workspace plan.
  • Ticket status changedRuns when an Atera ticket moves to another status, such as from Open to Resolved, with the status before and after. It can run only when tickets move to one status, or only for one customer. How often it checks follows your workspace plan.
  • New end user replyRuns when the end user adds a comment to an Atera ticket, such as replying to a technician's email, with what they wrote and the ticket's details. It can run only for one customer's tickets. How often it checks follows your workspace plan.
  • New technician commentRuns when a technician adds a comment to an Atera ticket, with what they wrote and the ticket's details. It can run only for one customer's tickets. How often it checks follows your workspace plan.
  • New alertRuns for each new Atera monitoring alert, such as low disk space or a device offline, with its severity, message, device and customer. It can run only for one severity or one customer. What was already there when the workflow is turned on doesn't start it. How often it checks follows your workspace plan.
  • Alert resolvedRuns when an open Atera alert is resolved, by a technician or because the problem cleared, with the alert's details and when it was resolved. Deleted alerts don't start it. How often it checks follows your workspace plan.
  • New customerRuns for each customer added in Atera, with their details. What was already there when the workflow is turned on doesn't start it. How often it checks follows your workspace plan.
  • Customer updatedRuns each time a customer's details change in Atera, with the details as they are now. How often it checks follows your workspace plan.
  • New contactRuns for each contact added in Atera, with their name, email address, phone numbers and customer. It can run only for one customer. What was already there when the workflow is turned on doesn't start it. How often it checks follows your workspace plan.
  • Contact updatedRuns each time a contact's details change in Atera, with the details as they are now. It can run only for one customer. How often it checks follows your workspace plan.
  • New deviceRuns when the Atera agent is installed on a new computer or server, with its name, customer, operating system and hardware. It can run only for one customer. What was already there when the workflow is turned on doesn't start it. How often it checks follows your workspace plan.
  • Device went offline or onlineRuns when a device running the Atera agent goes offline or comes back online, with its name, customer and when Atera last heard from it. It can run only for one of the two, or only for one customer. How often it checks follows your workspace plan.

Actions

Steps a workflow can run in Atera.

  • List ticketsList help-desk tickets, optionally only those with one status or for one customer. Gets one page; to see more, run it again with the next page.
  • Get ticketGet one ticket with its status, priority, end user, customer, assigned technician, first and latest comments and time spent.
  • Create ticketOpen a help-desk ticket for a contact, or for someone new by their email address and name (Atera adds them as a contact).
  • Update ticketChange a ticket's title, status, priority, impact or type, or assign it to a technician. Fields left empty stay as they are.
  • Delete ticketDelete a ticket for good, with its comments and time.
  • List ticket commentsList a ticket's comments with who wrote each, when, and whether it is an internal note. Gets one page; to see more, run it again with the next page.
  • Add ticket commentAdd a comment to a ticket from a technician, optionally as an internal note the end user doesn't see, or from the end user.
  • Log work hoursRecord time spent on a ticket, from when to when, whether it is billable and whether it was on the customer's site.
  • List customersList the companies you support, optionally only those changed since a day. Gets one page; to see more, run it again with the next page.
  • Get customerGet one customer with their address, phone, domain and notes.
  • Create customerAdd a company you support, with its contact details.
  • Update customerChange a customer's name or details. Fields left empty stay as they are.
  • Delete customerDelete a customer for good.
  • List contactsList the people at your customers, optionally finding them by part of an email address or phone number, or only those changed since a day. Gets one page; to see more, run it again with the next page.
  • Get contactGet one contact with their customer, email and phone numbers.
  • Create contactAdd a person at one of your customers.
  • Update contactChange a contact's name, job title, phone numbers or customer. Fields left empty stay as they are; the email address can't be changed.
  • Delete contactDelete a contact for good.
  • List alertsList monitoring alerts, such as low disk space or a device offline, optionally only open, resolved or snoozed ones. Gets one page; to see more, run it again with the next page.
  • Get alertGet one alert with its severity, message, device and customer.
  • Create alertRaise an alert on a device, such as a problem another system found, so it shows in Atera with the device's other alerts.
  • Resolve alertMark an alert resolved, so it leaves the open alerts.
  • Delete alertDelete an alert for good.
  • List devicesList the computers and servers running the Atera agent, with whether each is online, who is signed in, its operating system and hardware. Optionally only one customer's, or those with a machine name. Gets one page; to see more, run it again with the next page.
  • Get deviceGet one device running the Atera agent: whether it is online, when it was last seen, who is signed in, its operating system, hardware, disks and addresses.

Automate Atera with Lodol.

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

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