- or
No existing idea results
- ~ No ideas found ~
4810 results found
-
It would be great to be able to assign multiple devices a particular software or other automation by agent, not folder or site.
It would be great to be able to assign multiple devices a particular software or other automation by agent, not folder or site. Or, be able to assign multiple folders per device. Even better, would be able to assign by user from EntraID.
2 votes -
Ticket Times
If a user raises a ticket, and has a device linked to that user. When you connect to that device via Atera, it should automatically add the time you were connected to the ticket. Other tools such as Autotask have this feature and it is extremely useful
1 vote -
ticket time
If a user raises a ticket, and has a device linked to that user. When you connect to that device via Atera, it should automatically add the time you were connected to the ticket. Other tools such as Autotask have this feature and it is extremely useful
1 vote -
1 vote
-
Feature Request: Allow running / re-running ticket playbooks on existing tickets.
Feature Request: Allow running / re-running ticket playbooks on existing tickets (or in a ‘simulation’ mode) so we can iterate and debug complex automations faster without generating new test emails/tickets each time.”
3 votes -
[API] SearchOption
When searching contacts by phone number through the API, the searchOptions.phone filter only matches the Phone field of a contact. It does not match MobilePhone, even though both fields are part of the same
contact record and both are valid phone numbers for that contact.Use case
We are building an automation that needs to identify the calling end-user from their phone number and resolve them to an Atera contact in order to retrieve their tickets,
post comments on their behalf, etc. In real customer data, the mobile number is stored in MobilePhone for the majority of contacts (landline goes to Phone when present). With the current behavior, those
contacts cannot be found via the API search and we have to fall back to listing all contacts and filtering client-side, which is slow and does not scale.Steps to reproduce
- Create or pick a contact whose MobilePhone = 600101010 and whose Phone is empty (or different).
- Call: GET /api/v3/contacts?searchOptions.phone=600101010
- Expected: the contact is returned.
- Actual: empty result. The same call works only if you put the number in Phone.
We have tried number variants (600101010, 34600101010, +34600101010) and combinations of EnableContactsSearch/EnablePartialSearch flags — none of them make the search look at MobilePhone.
Suggested fix
searchOptions.phone should match against Phone and MobilePhone (logical OR), the same way the in-app contact search does. Alternatively, expose searchOptions.mobilePhone as a separate filter so callers can
choose.Current workaround
We list contacts page by page and filter client-side on Phone || MobilePhone. This means N requests per identification and we hit rate limits on tenants with many contacts.
Environment
- Atera REST API v3 (https://app.atera.com/api/v3)
- Tested 2026-04-16
Thanks!
When searching contacts by phone number through the API, the searchOptions.phone filter only matches the Phone field of a contact. It does not match MobilePhone, even though both fields are part of the same
contact record and both are valid phone numbers for that contact.Use case
We are building an automation that needs to identify the calling end-user from their phone number and resolve them to an Atera contact in order to retrieve their tickets,
post comments on their behalf, etc. In real customer data, the mobile number is stored in MobilePhone for the majority of contacts (landline goes…2 votes -
Patch management
To be able to schedule Patch management tasks, this would be useful for Mac devices that require Upgrade patches to be run via Patch management instead of IT Automation profiles.
This workaround is useful for Mac devices that are offline, in order to help automate pushing Upgrade patches
86 votes -
Software Bundle Deployment Very Slow
Software Deployment is incredibly slow, and lacks any meaningful feedback during and after the process completes. No matter how many softwares are included in the list, it seems to take nearly an hour to deploy. Meanwhile, when we use a script to deploy a series of Ninite packages, they are done in 20 minutes...
At this point we only install two things from our default software bundle, and it STILL TAKES FOREVER. We don't even know when it really finishes without pulling event logs.
The whole point behind automation is to do it faster than a person... right now the slowest person on our team can get it done in 15 minutes. We expect this to take less than 10 and as much as 15 if we are also installing something big like Microsoft Office.
Software Deployment is incredibly slow, and lacks any meaningful feedback during and after the process completes. No matter how many softwares are included in the list, it seems to take nearly an hour to deploy. Meanwhile, when we use a script to deploy a series of Ninite packages, they are done in 20 minutes...
At this point we only install two things from our default software bundle, and it STILL TAKES FOREVER. We don't even know when it really finishes without pulling event logs.
The whole point behind automation is to do it faster than a person... right now the…
2 votes -
Dynamic field mapping for Cloud Actions via Custom Fields
Summary
Cloud Actions should be able to pull values for API calls dynamically from user-defined Custom Fields, instead of only supporting static input or full list retrieval. This would enable targeted update/write operations against the Atera API (and external APIs) without having to manually identify the relevant record.
Current behavior
When I set up a Cloud Action against the Atera API (e.g. "Update Customer"), I can essentially only retrieve all entries via the API. There is no way to dynamically bind a call's parameter to a specific record or an existing Custom Field. As a result, targeted updates are cumbersome or not possible at all.
Desired behavior
When creating a Cloud Action, I want to define per API parameter where the value comes from - in particular, from a user-created Custom Field. Example:Cloud Action: "Update Customer" (Atera API)
Parameter CustomerID → Source: Custom Field customerid
The action reads the value from the field, matches the corresponding entry, and performs the update specifically for that record.Specifically, this would require:
Selecting the value source per parameter (static value, variable, Custom Field).
Mapping Custom Fields to API parameters directly in the action editor.
Validating/matching the entry before the write operation, so the correct object gets updated.Use case / benefit
This would make it possible to build real automated update workflows (maintaining customer data, keeping fields in sync, reconciling external systems) instead of only reading and "dumping everything." For MSP scenarios with individual Custom Fields, this is a significant improvement in efficiency and data quality.Summary
Cloud Actions should be able to pull values for API calls dynamically from user-defined Custom Fields, instead of only supporting static input or full list retrieval. This would enable targeted update/write operations against the Atera API (and external APIs) without having to manually identify the relevant record.
Current behavior
When I set up a Cloud Action against the Atera API (e.g. "Update Customer"), I can essentially only retrieve all entries via the API. There is no way to dynamically bind a call's parameter to a specific record or an existing Custom Field. As a result, targeted updates are cumbersome…1 vote -
Copilot window obscures device function buttons
On a device page, the AI Copilot windows obscures the Connect, Manage, Copilot, and Create ticket buttons along the top. Similar issue on the Ticket page, etc.
3 votes -
API integration with Sangoma PBX to reset voicemail password
Link with Sangoma PBX to pull call recordings and reset voicemail passwords
2 votes -
no details of the queued devices that did not get updated when IT automation profile
How do we know if the offline devices got updated when an IT automation profile is set to queue devices for a week or a month .
The report should mention if any of the device got updated when they came online. This will confirm if queuing devices even works.2 votes -
Signature ios
Add signature options to mobile apps for technicians. Currently it doesn’t pull them through from profile so responses done on mobile app don’t include a signature
4 votes -
I would love to have more columns in the device search, for example looking for device serial number would be great
Having more options to quick search would be helpful minimizing the time to look into each device detail.
for example I would love to see columns such as, Device serial number, Processor, Memory, MAC addresses ...12 votesHi,
We wanted to let you know that your idea is currently under review by our product team. We are evaluating its alignment with our product roadmap and its potential benefits to our users.
We appreciate your patience during this process and will update you and the public status of this suggestion once a decision has been made.
Best regards,
The Atera Team
-
Time Since Last Activity Condition
I would like to see a trigger or condition based on the Time Since Last Activity of a ticket.
I am wanting to create an automation rule that sends an email to a technician after 72 hours since last activity on an open or pending ticket as a reminder to follow up on the ticket.
1 vote -
Limit bearer token to ipv6 address
Allow IPv6 as well as IPv4 on bearer token.
When creating a new API Token I have to allow all Any since our production servers use IPv6 and the input form will not allow that.
1 vote -
Device Page Title Arrangement
On the Device page you should improve navigation by organizing the title line in this format:
Back arrow, Device OS Type, Favorite Star, Customer Name, Folder, Device name
Also in the sub title you could list the currently logged in or last active user next to the contact to see them at a glance instead of navigating to the tabs below.
This would prevent the need to look at the Overview tab to identify the relationship of the device. it is exspecially helpfull if multiple organizations have similar or exact device names (ie:server). Also providing a refresh button or auto refresh option for when devices are rebooted for tech to know when the agent comes back online.
On the Device page you should improve navigation by organizing the title line in this format:
Back arrow, Device OS Type, Favorite Star, Customer Name, Folder, Device name
Also in the sub title you could list the currently logged in or last active user next to the contact to see them at a glance instead of navigating to the tabs below.
This would prevent the need to look at the Overview tab to identify the relationship of the device. it is exspecially helpfull if multiple organizations have similar or exact device names (ie:server). Also providing a refresh button or auto…
1 vote -
Implement domain-based restrictions for automatic contact creation from incoming ticket emails.
Implement domain-based restrictions for automatic contact creation from incoming ticket emails.
Currently, the setting applies to either all or none.For example:
- Do not create contacts for emails originating from public domains (e.g., Gmail).
- Automatically create contacts for emails from recognized company domains.Ideas for configuation either:
- Maintaining an allow list of approved domains, or
- Maintaining a block list of domains to exclude from contact creation.
Thank you for your consideration
1 vote -
Ability to copy a ticket
Sometimes I have to create several tickets that have all the same information - it would be helpful if we could "copy" a ticket as a starting point and have it bring over all the info (categories etc.)
2 votes -
Use multiple monitors at the same time with AnyDesk.
Use multiple monitors at the same time with AnyDesk.
3 votes
- Don't see your idea?