ArcGIS Connectors for Power Automate Blog

We are pleased to announce a new set of updates in the 2025.3 release. For a quick read see What's new in ArcGIS Connectors for Power Automate Documentation. This release focuses on the enhancements in the "Get Data from Feature Layer" action as well as the Query functionality in our webhooks. Building upon the significant improvements introduced in the last release, these new features address key requests from our user community.

Note:  At the time of writing this article ArcGIS Online and PaaS connectors are rolled out by Microsoft and we are yet to receive these changes in ArcGIS Enterprise Connector

NEW ACTION: Perform Geometry operations

Available in all three connectors, this new action will include several operations coming from Geometry service starting with following two operations. See additional details on inputs and outputs here https://developers.arcgis.com/rest/services-reference/enterprise/geometry-service/ 

Areas and lengths

This operation calculates areas and perimeter lengths for each polygon specified in the input array. The result is an output array of areas and lengths which should be in the same order as the input. At this time we only offer select units in our action. If this is not sufficient for your use please contact us. See Areas and Lengths for more details

Buffer

The buffer operation is performed on a geometry service resource. The result of this operation is buffered polygons at the specified distances for the input geometry array.

NEW to ArcGIS PaaS Connector

We are committed to improving the ArcGIS PaaS connector going forward, so you can let your users use ArcGIS Operations without having have their own ArcGIS Accounts. Through API keys you can let your clients access some of these actions. See how to create API Keys here.

• Enhance ArcGIS PaaS connector to support Get data from feature layer operation
• PaaS connector can now run Perform Geometry Operation action.

New capabilities in "Get data from feature layer" action

Update available in ArcGIS, ArcGIS Enterprise and ArcGIS PaaS connector. We are excited to see all of you use these capabilities in variety of ways. Building on the previous release we now added following functionality in this action. For more details on these operation please read up on Query (Feature Service/Layer) | ArcGIS REST APIs | Esri Developer

Select Output Fields

Users can now specify exactly which fields are returned in their query results. This improvement streamlines outputs, reduces unnecessary data, and enhances overall performance by reducing amount of data returned from the feature service. 

Output Summary Statistics

Users can now perform advanced operations by output summary statistics for any chosen fields within a feature layer. Furthermore, it is possible to select group-by-fields for these statistics, allowing for aggregation and the highlighting of key metrics. This enhancement simplifies the process of notifying stakeholders or updating dashboards with essential summary data, such as totals, averages, and counts, all without the need for external data processing. You will first need to select Yes to dropdown under Show statistics to run this operation. Choosing this will ignore some of the settings in other dropdowns. See the Query operation details mentioned in the URL above.

Here is an example: 

Order by fields

You can now order the fields ascending or descending in your query output from this action. 

Restrict triggers by Layer Queries

When a record is created/updated in feature layer triggers in ArcGIS and ArcGIS Enterprise now offer enhanced control data that is returned. When configuring webhooks in fetching updates, changes, or deletions action, you can now apply a layer query by filling Fields to compare section. As a result, only features matching the specified criteria will be returned. ensuring that notifications and responses are both timely and relevant. You can use this in addition to Esri geometry filter. For more details see Extract Changes (Feature Service) parameters.

Find address candidate (top candidate) is deprecated

Find address candidate is deprecated from ArcGIS and ArcGIS Enterprise connectors but this will still be available in ArcGIS PaaS connector. Flow currently still using this action will continue to work. This action will not appear in the list of available actions. It is recommended to use Find address candidates action and the "Top candidate match address" instead.

Other Enhancements

• Find address candidate can receive now have single line address input.
• Administrators can now create webhooks on any feature services.
• Correct errors will be returned if webhook creation fails when the layer is not editable

Documentation

Actions and triggers documentation has been updated to include relevant links to the API for most of the actions. Added and cleaned up documentation.

Discover the Latest Features and Enhancements Released on July 22, 2025

• Get data from feature layer action updates
  • Supports combining multiple parameters
  • Added support for Spatial query, Spatial relationship, Buffer etc
  • Clear parameter names and guidance in Placeholder
• Restrict ArcGIS Triggers (Webhooks) by geometry
• ArcGIS Enterprise Map Services with data referenced from enterprise database now supports webhooks.
• New Action: Get item information.

Introduction

ArcGIS for Power Automate is a powerful tool that enables you to automate workflows by integrating ArcGIS with various services. One significant functionality is the ability to add data to feature layers. However, as your data processing needs grow, you might find that migrating to batch operations becomes essential to improve efficiency and manage larger datasets effectively.

What are the new batch actions?

In 2024.2 release we introduced Batch actions that allow us to add or update multiple features in a single request. The following actions are added to the list

• Add records to a feature layer (batch)
• Update records in a feature layer (batch)

These actions will take Array of Features as their input. Notice the difference between Update a record in a feature layer Inputs vs Update records in a feature layer (batch)

Appropriate JSON structure for the Array of features can be found here.

To extract the schema of your Feature layer, access the REST endpoint of your ArcGIS server service and query the features at "/server/rest/services/FeatureService/<layer>/query". For ArcGIS Online, open Item details for the layer you are trying to query under item details and view the URL.

Once at the query endpoint form, under Where, use 1=1 (or an OBJECTID you know) with Out Fields set to * and Format set to JSON.

If your data originates from sources other than a feature layer, such as Excel or a database where geometry information is stored in a text column, you must rename the column to "geometry" for the Batch actions to recognize it in Power Automate. Alternatively, you can create the required JSON structure using Power Automate built-in actions like Select, Compose, and Parse JSON from Data Operations, which will be useful.

Here is a sample JSON structure.

[{
    "geometry": {"x": 1234,"y": 1234},
    "attributes": {"name1": "value1", "name2": "value2"}
  },
  {
    "geometry": {"x": 1234, "y": 1234},
    "attributes": {"name1": "value1", "name2": "value2"}
}]

Are batch actions right for you?

When working with single feature operations such as `Create/Update a record in a feature layer` you typically add one or a few features at a time to your feature layer. This method is straightforward and can be sufficient for small-scale data additions or updates. There is no need to change the existing workflow as there are no performance gains.

Using these actions within a "For Each" loop becomes less efficient when handling a large number of records that need to be created or updated. It is advisable to consider migrating to batch actions in the following scenarios:

• Updating dozens or thousands of records.
• The flow is set to run frequently with numerous features.
• Working with feature arrays can be a better alternative to configuring each field in a form for single record actions, particularly when dealing with feature services that contain many fields.
• Performing copy operations.

We are pleased to announce the latest updates and enhancements to the ArcGIS for Power Automate connectors, released in the first week of April, 2025. The released version is 2025.1. This release introduces a comprehensive array of enhancements and bug fixes. ArcGIS Online and Enterprise connectors were released and following updates doesn't apply the ArcGIS PaaS connector.

Key Update

BUG-000169725: Authentication to ArcGIS Online through ArcGIS Connectors for Power Automate workflows frequently fails and returns the error message, "Authentication failed. Your session has expired." This issue, which affected a significant number of Esri users, has been successfully resolved along with updates to token exchange mechanism the error messaging. This should provide relief for ArcGIS Enterprise 11.3 and 11.4 users who were affected by this. No further actions are required by users.

Important Bugs Fixes

• An issue with the "Update a Record in a Feature Layer" action has been resolved. Previously, a "STRING" Unique ID was incorrectly treated as a "NUMBER," resulting in an error:

No item was found that matches the query <fieldname> = <value> …

• Action name was corrected from “Update records to a feature layer (Batch)” to “Update records in a feature layer (Batch)”
• BUG-000173694 An error message returns when using the 'Delete a record from feature layer' action with a referenced feature service in the ArcGIS Enterprise connector for Power Automate was resolved.
  • Using the 'Delete a record from feature layer' action with a referenced feature service from ArcGIS Enterprise resulted in the error below, however, the record was deleted from the feature layer.

  • "ResponseSwaggerSchemaValidationFailure. The API 'arcgisenterprise' returned an invalid response for workflow operation 'Delete_a_record_from_feature_layer' of type 'OpenApiConnection'. Error details: 'The API operation 'DeleteItemInFeatureLayer''.

• BUG-000170950: The problem where leading or trailing zeros were trimmed when inserting a number into a string field while using the 'Create a record in a feature layer' action in ArcGIS Connectors for Power Automate has been addressed.

These updates underscore our commitment to enhancing the functionality of ArcGIS for Power Automate connectors, ensuring that users experience a seamless and efficient workflow. We look forward to bringing you more exciting updates and features in the future. Please feel free to reach out and comment

We are pleased to announce that we have fixed issue BUG-000174431 where Power Automate was throwing an error code 1000 with the message "Conversion failed when converting date and/or time from character string."

Power Automate is now resolved and should be available in production. This fix affects the following actions:

• Create a record in a feature layer
• Update a record in a feature layer

Even though the input field is text, the epoch entered should be without quotes, e.g., 1740433032729. Other text inputs are possible in the format of MM/DD/YYYY, etc. For specifications, please refer to the Add Features  and Feature Object. When the input date is not in the epoch time, it is recommended to use the "Convert date and time format" action.

Thank you for your patience and understanding

Are your Power Automate flows not running as expected? Discover how to troubleshoot and identify issues using Webhook.site. This powerful tool allows you to generate unique URL listeners to verify if your webhooks are firing correctly. In our latest blog post, we provide a step-by-step guide to setting up and using Webhook.site for effective debugging.

Consolidated information for multiple reports of webhooks not running properly in Power Automate.

Quick tip to help keep the ArcGIS Connectors for Power Automate connection valid when your flow runs on an infrequent basis.

An update on one of two issues associated with the 'Fetch updates, changes, or deletions from feature layer' action in the ArcGIS Connector. I use a food analogy to describe what's happening. 

Information regarding a bug that was reported in multiple areas on the forums: 

- Unable to retrieve data from 'My Content'