Overview
This guide walks you through configuring the ArcGIS integration in Limble/Prismatic.
The ArcGIS integration supports the following workflow:
Initial Asset Import: Imports ArcGIS features from selected layers into a Limble location as assets.
ArcGIS Attribute Sync: Maps selected ArcGIS attributes into Limble asset custom fields (prefixed as
ArcGIS: <AttributeName>).Ongoing Webhook Sync: Uses ArcGIS webhook events to apply feature creates, updates, deletes, and geometry changes to Limble.
Table of Contents
Prerequisites
Step 1: Connect Limble and ArcGIS
Step 2: Select Feature Service
Step 3: Map Layers to a Limble Location
Step 4: Choose Attributes and Asset Naming
Step 5: Configure Notifications
Results
Automatic Webhooks
Syncing Existing Assets
Troubleshooting
Prerequisites
An active ArcGIS Online environment.
A valid ArcGIS Feature Service URL (
.../FeatureServer) with the layers you want to sync.An ArcGIS account with permission to read features, attributes, and geometry, and to create/manage webhooks on the Feature Service (typically an Administrator or Publisher role).
Step 1: Connect Limble and ArcGIS
Open Settings > Integration Center in Limble.
Open ArcGIS Sync and select Reconfigure.
On the Connections page, authorize the ArcGIS Connection using ArcGIS OAuth 2.0 credentials that have access to the target Feature Service. The ArcGIS account used to sign in must have permission to read features and manage webhooks on the Feature Service (typically an Administrator or Publisher role).
Select Next.
ArcGIS OAuth 2.0 credential setup (step-by-step):
Sign in to ArcGIS with an account that can create developer credentials.
Open ArcGIS Content, select New Item, then choose Developer credentials.
On Create developer credentials, select OAuth 2.0 credentials (for app authentication) and select Next.
When asked where the credentials will be used, select Private application with selected privileges and access and select Next.
On Item access, select Grant access to specific items, then check the Feature Service (feature layer) you want to sync and select Next.
On Item details, enter a title (required) and select Create.
Open the credential item. Under Settings, set Redirect URLs and Referrer URLs to
https://*.prismatic.ioand select Save.Copy Client ID and Client Secret from the Credentials section on the same page.
Return to Limble Integration Center and use these credentials to authorize the ArcGIS connection.
Important: Keep the Client Secret secure and rotate it if exposed.
Step 2: Select Feature Service
On the Feature Service page, paste the full ArcGIS Feature Service URL.
Use this format:
https://servicesX.arcgis.com/<org-id>/arcgis/rest/services/<ServiceName>/FeatureServer.Confirm it is a FeatureServer endpoint (not MapServer).
Select Next.
Step 3: Map Layers to a Limble Location
On Layer Mappings, choose the target Limble Location and select one or more ArcGIS layers to sync.
Confirm the selected layers are the exact layers you want represented in Limble.
Select Next.
Step 4: Choose Attributes and Asset Naming
On Attributes to Import, choose which ArcGIS fields should sync to Limble custom fields.
Optional: set Asset Name Attribute to derive Limble asset names from a specific ArcGIS attribute.
If no Asset Name Attribute is selected, default naming is
<Layer Name> <ArcGIS ObjectID>(example:Bulk Water Pipe 125).Select Next.
Notes:
ArcGIS attributes are stored as Limble custom fields named
ArcGIS: <AttributeName>.If multiple layers are selected, prefer attributes that are valid across those layers.
Step 5: Configure Notifications
On Notifications, enter Notification Recipient Emails (comma-separated). Example:
ops@acme.com,admin@acme.com.Enable Notify Status Reports to receive import completion and sync summaries.
Enable Notify Errors to receive failure/error alerts.
Select Save to finish the configuration.
Results
Once setup is complete, the ArcGIS integration will:
Import ArcGIS features as Limble assets.
Keep selected attributes in sync.
Process ongoing feature changes through webhooks.
Maintain ArcGIS linkage using
ArcGIS: GlobalID.
Automatic Webhooks
The integration automatically registers a webhook on the ArcGIS Feature Service when deployed. It subscribes to feature creates, updates, deletes, and edits. The webhook is also automatically removed if the integration is deleted. You do not need to create or configure a webhook manually in ArcGIS.
Prerequisite: The ArcGIS Feature Service must have Keep Track of changes to the data (Change Tracking) enabled. Without this, ArcGIS cannot fire webhooks for feature edits.
Syncing Existing Limble Assets
If you have existing Limble assets that you want to link to ArcGIS features, you can do so by adding the ArcGIS: GlobalID custom field to the asset and entering the matching ArcGIS feature's GlobalID value.
The integration runs a weekly scan (Sundays) that automatically detects assets with a GlobalID but missing ArcGIS data and backfills:
Map location (geoLocation) from the ArcGIS feature geometry
ArcGIS: Layer field identifying which layer the feature belongs to
ArcGIS attribute fields for all attributes selected in the configuration
Asset name (if an Asset Name Attribute is configured)
Assets that already have complete sync data are skipped. After the weekly scan picks up an asset, subsequent changes to that feature in ArcGIS will be synced automatically via webhooks.
Troubleshooting
If records are missing or not updating:
Confirm the auto-registered webhook is active in ArcGIS (check the Feature Service's WebHooks page).
Confirm selected layers and attributes are still valid in ArcGIS.
Check execution results for rate limiting (
429) or field-attachment errors.Ensure expected custom fields are present and writable in the target Limble location.
If webhook sync shows a URL validation error:
The integration validates that all ArcGIS URLs belong to
*.arcgis.comor*.arcgisonline.com. Ensure the Feature Service URL is a standard ArcGIS Online URL.Webhook-derived URLs (changes, status, result) must match the configured Feature Service hostname. If ArcGIS returns a URL on a different host, the request is blocked for security.
If duplicate or partial assets are observed:
Review execution errors for
ArcGIS: GlobalIDand required field attachment failures.Resolve any custom-field creation conflicts in Limble.
Re-run import after correcting missing field setup.


