ArcGIS QuickCapture

ArcGIS QuickCapture is Esri's single tap field data capture app where a button press lands a located record in a hosted feature layer. Agents manage projects, buttons, data sources and resources, read captured records, configure webhooks, and react when a crew captures data.

1 trigger 28 actions OAuth available

ArcGIS QuickCapture website Platform Documentation Capability data verified 2026-08-26

On Record Captured delivers a hazard a crew logged with one button press

Agent reads the severity and asset values the button stamped onto the record

List Record Attachments and Download Record Attachment fetch the photo the payload never carries

Agent confirms the captured location falls inside the maintained network

Query Captured Records looks for an earlier capture on the same asset this week

A prioritized work order opens with the location, the photo, and the crew member named

The area supervisor is sent the photo and the map reference

The supervisor decides whether a high severity hazard gets a crew rolled tonight

What This Integration Enables

ArcGIS QuickCapture is what you reach for when the person capturing data has one hand free. There is no form to fill in: a project is a grid of large buttons, and pressing one lands a record with the device's location already attached, usually with a photo. That design decision runs all the way through the API. A QuickCapture project is a single JSON document attached to a portal item, and the buttons, the layers they write to, the capture preferences, the location tracking settings, and the webhooks all live inside it. Every write is a read, a change, and a write back of the whole thing.

FlowRunner agents author and clone projects, wire and unwire the feature layers behind them, restyle and relabel buttons across a fleet, upload button images, build the deep links that open a project prefilled on a crew member's phone, read back what was captured, pull down the photos, and manage the project's webhooks. The record operations here are deliberately read only and project scoped, because writing into an arbitrary feature service is the sibling ArcGIS Field Maps connector's job rather than this one's. The point of putting agents on this surface is not that capture becomes faster. It is that a button press in the field can start real work, and the decisions that follow reach a supervisor with the photo already attached.

Without FlowRunner

Capture and dispatch are separate A crew logs a defect and somebody notices it in a dashboard the next working day

Photos stay in the layer The evidence sits in the feature service and never reaches the ticket or the report

Project changes are a designer session Relabeling buttons across a fleet of projects means opening each one by hand

With FlowRunner

Capture is the dispatch A button press opens the ticket, pulls the photo, and reaches the supervisor

Evidence travels with the job The attachment is pulled into storage and attached where the work is actually assigned

Projects are configured as a flow Buttons, data sources, sharing, and tracking are read and written across projects at once

Use Case Scenarios

A button press becomes a work order

A lineworker presses the Damaged Pole button while driving the route. On Record Captured fires with the feature, its attributes, and the feature service's reply. The payload names the attachments but never carries their bytes, so the agent calls List Record Attachments and Download Record Attachment to pull the photo into storage. It reads the severity value the button stamped, checks Query Captured Records for a duplicate report on the same asset this week, and opens a prioritized ticket in ServiceNow with the location, the photo, and the inspector's name. High severity captures also reach the on call supervisor as a call through Twilio rather than a notification that waits until morning.
The morning situation report

Each morning the agent calls Count Captured Records per project with a where clause on the capture date, which is cheap and answers whether anything arrived at all. Only the projects that captured something get read with Query Captured Records. Attachments are downloaded, the records are grouped by area, and the assembled report files to SharePoint with a summary posted to Slack. Nobody exports a layer, and the report is built from what was actually collected rather than from a dashboard screenshot.
Reconfiguring a fleet of projects for the season

A campaign changes and forty projects need new button labels, new colors, and different stamped field values. The agent uses Search QuickCapture Projects to find them, List Project Buttons to flatten each project's buttons out of their layout groups, and Update Project Button to apply the change. Upload Button Image swaps in new artwork. The same sweep audits governance: which projects Share Project has exposed publicly, which have location tracking enabled, and where each project's webhooks point. Crews pick the changes up the next time their device downloads the project, which is a fact the flow schedules around rather than ignores.

Human-in-Loop Highlight

Delete Project Webhook is not a stop button, and that is exactly the trap an agent asked to pause an integration for maintenance will fall into. A QuickCapture webhook is not a subscription held by the portal. It is an entry inside the project definition, and the mobile app is what posts it. Delete it and every device still holding the older copy of the project keeps posting for as long as it takes them to download again, so deliveries do not stop. Re-create it afterwards and nothing arrives from those same devices until they download again either, so the integration does not come back on cue. Meanwhile the definition write has no optimistic concurrency, so a second flow editing the same project at that moment can silently lose one of the two edits.

So the maintenance agent gathers the state and hands over the verb: "Project Storm Damage 2026 has one active webhook posting to the ingest endpoint. You asked to stop deliveries during the migration window. Delete Project Webhook is permanent and devices already holding the project will keep posting anyway. Update Project Webhook can disable it instead, which is reversible but also only lands on each device's next download. Disable, delete, or leave it running and drain at the receiver?" The integration owner picks. Finding the webhook, reading the project fleet, and warning about the write race is work the agent should do unprompted. Choosing which of those three states the field estate ends up in belongs to a person.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

28 actions

Projects

Search QuickCapture Projects Finds the projects the connected account can reach across its own content, its organization, and public sharing, narrowed by text, owner, or group.
Get Project Reads the portal item behind a project: title, summary, tags, owner, folder, sharing level, thumbnail, size, and timestamps. The item record only.
Get Project Definition Returns the complete project definition, the single JSON resource holding the capture buttons, their layout groups, the data sources, the preferences, the tracking settings, and the webhooks.
Replace Project Definition Overwrites the whole definition with the one supplied. The escape hatch for changes the named operations do not cover, and the operation to batch related edits into rather than racing.
Create Project Creates a project: a portal item of the right type, stamped with the keywords the mobile app looks for, with a definition attached.
Update Project Details Changes the item's title, summary, description, tags, and access information. It never touches the definition, so buttons, data sources, and webhooks are unaffected.
Delete Project Permanently removes the project item with its definition, button images, and thumbnails. The hosted feature layers survive, so records already captured are not lost.
Share Project Sets who can open a project, from owner only through the organization to everyone, and hands it to named groups. Sharing the project item is not enough on its own: the layers it captures into have to be shared at least as widely or a crew will open the project and then be unable to submit.
Get Project App Link Builds the deep links that open a project directly in the mobile app, prefilled, and confirms the item really is a QuickCapture project while doing it.

Project Configuration

List Project Data Sources Lists the feature layers a project is wired to, with each layer's URL, the item behind it, and whether the project captures into it, queries it, or both.
Add Project Data Source Wires an additional feature layer into a project so its buttons can capture into or query it.
Remove Project Data Source Unwires a layer from a project without touching the layer or the records in it. Refused while a capture button still points at it, and the refusal names the buttons.
Update Project Preferences Changes capture preferences: whether crews may nudge a location, the split screen map layout, the background color, and the accuracy thresholds that warn or block a capture.
Update Location Tracking Turns location tracking on or off for a project and sets how it behaves. When enabled the app records where the crew traveled, not only what they captured, which is a decision worth making deliberately.

Buttons

List Project Buttons Lists every capture button flattened out of the template groups that lay them out, with its label, group, color, shape, image, and the field values it stamps.
Update Project Button Changes how one button looks and what it records. Field values replaces the list of feature fields the button stamps onto every record it captures.

Project Resources

List Project Resources Lists the files attached to a project item: the definition itself, the button images, and the thumbnails.
Upload Button Image Streams an image from a URL into a project's images folder so a capture button can display it.
Delete Project Resource Permanently removes one file resource, such as a retired button image. It refuses the project definition itself, because removing that would make the project unopenable.

Webhooks

List Project Webhooks Lists the webhooks configured on a project with their payload URLs, enabled state, the layer whose submissions fire them, and which blocks of event data they carry.
Create Project Webhook Adds a webhook so every record a crew submits to the chosen layer is posted to an external URL, with the payload blocks you choose.
Update Project Webhook Changes a webhook already on a project, including disabling it. The reversible alternative to deleting one.
Delete Project Webhook Removes a webhook permanently. Devices still holding the older copy of the project keep posting to it until they download again, so this is not a clean stop. The operation this page's human gate exists for.

Captured Records

Query Captured Records Reads the records a project collected, straight out of the hosted feature layer. Name the project and data source and the layer is resolved for you.
Count Captured Records Counts what a project collected without returning any of it. The cheap gate on whether a reporting flow needs to run at all.
List Record Attachments Lists the photos, videos, and files attached to one captured record with their identifiers, names, types, and sizes.
Download Record Attachment Fetches the bytes of one attachment into file storage. This is how a photo taken in the field reaches an email, a report, or a vision model, because the webhook payload never carries the bytes.

Portal

Get Connected Account Reports the account this connection signed in as, with its role, user type, and privileges. Worth calling before authoring, since project authoring requires a specific ArcGIS user type.

Triggers

1 triggers

Event Triggers

On Record Captured Starts a flow whenever a field crew submits a record to the chosen project. FlowRunner writes a webhook into the project definition when the flow starts and removes it when the flow stops, so nothing is configured in the QuickCapture designer. The payload carries the captured feature with its attributes and geometry, the feature service's reply with the new object id, the project identifiers, and the submitting account. Two consequences follow from the device posting these rather than the portal. A device only starts firing after it downloads the project again, so allow for that when switching a flow on mid shift. And a record captured with no signal is delivered when the device next reaches the network, which can be hours later. Attachment bytes are never delivered, so follow this block with List Record Attachments and Download Record Attachment when the flow needs the photos.

Frequently Asked Questions

What can FlowRunner do with ArcGIS QuickCapture?

FlowRunner agents can run Search QuickCapture Projects, Get Project, and Get Project Definition in ArcGIS QuickCapture, plus 25 more actions.

Does connecting ArcGIS QuickCapture to FlowRunner require OAuth?

Yes. ArcGIS QuickCapture connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can ArcGIS QuickCapture trigger a FlowRunner workflow automatically?

Yes. ArcGIS QuickCapture supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with ArcGIS QuickCapture

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us