- or
No existing idea results
- ~ No ideas found ~
4802 results found
-
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 -
Print MULTIPLE Tickets
I would like Atera to have the ability of print multiple tickets.
In the past, I see that someone suggested the Idea and It got moved to production and it's live now.
However...
In my organization, we are ask in a monthly base, to describe and summarize our 'highlights'.
What I have been doing it, it's I go through 20~ tickets manually, select the print option, and save it as a PDF...
Then I use AI to give it formatting base on the ticket in that PDF.
I would like, and I think it will be useful-- to allow multiple tickets to be selected, so you can 'print' all of that selection, so it generates a PDF containing all those tickets merged into a single PDF, instead of various documents.
I would like Atera to have the ability of print multiple tickets.
In the past, I see that someone suggested the Idea and It got moved to production and it's live now.
However...
In my organization, we are ask in a monthly base, to describe and summarize our 'highlights'.
What I have been doing it, it's I go through 20~ tickets manually, select the print option, and save it as a PDF...
Then I use AI to give it formatting base on the ticket in that PDF.
I would like, and I think it will be useful-- to allow multiple…
2 votes -
Emails to other than the requester
I would like to be able to start a "side conversation" on a ticket for when I need to communicate with a third party related to the issue at hand.
70 votes -
Include snippet for Contact First Comment
Crate a snippet for Contact First Comment so that it can be added to an email template used for resolution.
3 votes -
Need to be able to tie assets to a user
At this time we are using Atera for several things it was not initially designed for. We are using it as an asset management solution as well as the main development and design for what Atera is made for. We are able to add assets and assign them to a user however when we search the user nothing in your current set up lets us see all the assets we have associated to that user.
13 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
-
Kill Splashtop SOS sessions
Terminate Splashtop SOS sessions directly from Atera when the session limit message appears, instead of waiting one hour for them to expire automatically
2 votes -
Ticket tabs "more"
When there are more than (on my screen) 13 ticket tabs open, you get a "x more" (x being a number) stack to the right.
I cannot find an option to close open tabs in that list.
Please add an "x"-Button next to ticket title in that list.2 votes -
Make all custom fields available in scripts
Currently only agent custom fields are available to use in scripts. All custom field should be available (where sensible). For example, customer wide custom field containing data we want to access in a script.
5 votes -
Webhooks
Webhooks triggers on Alerts
We are exploring the possibilities of using Webhooks to integrate Atera with Freshservice for the Alert system.
Currently, your Webhooks system only allows actions to be triggered against tickets, meaning within ticket automations. We have already confirmed with your support team that a ticket created by an alert does not automatically close when the alert is resolved, which leaves the Freshservice alert disconnected if it is resolved from Atera, making the integration less functional.
We have found that in Zapier, you do have triggers available for both alert creation and resolution. Therefore, we understand that the system should be capable of doing the following:
We would like to be able to trigger Webhook calls on alert creation and resolution events. We do not want to use Zapier as Freshservice has a listener element where the Atera hook can be launched, and using Zapier would unnecessarily increase steps and operational costs.
This functionality (attaching Webhook calls to alert creation and resolution events) would be the cleanest and most effective way to keep alerts connected between the two systems and ensure we don’t miss anything.
Webhooks triggers on Alerts
We are exploring the possibilities of using Webhooks to integrate Atera with Freshservice for the Alert system.
Currently, your Webhooks system only allows actions to be triggered against tickets, meaning within ticket automations. We have already confirmed with your support team that a ticket created by an alert does not automatically close when the alert is resolved, which leaves the Freshservice alert disconnected if it is resolved from Atera, making the integration less functional.
We have found that in Zapier, you do have triggers available for both alert creation and resolution. Therefore, we understand that the…
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
- Don't see your idea?