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.
Andy Merkes
shared this idea