Customer map
Record which customers each asset, site or segment serves, so a flow can reach exactly the customers affected when something happens there.
Updated 11/10/2026
On this page
When something happens to a part of your operation (a pipeline section is shut for maintenance, a substation goes down, a delivery route is delayed), you need to know which customers it affects. The customer map answers that. It lists each asset or segment and the customers it serves, with their ids in your CRM and other systems.
Flows use it to find the affected customers and contact each one, for example with an approved notice and a case in your CRM. It is a lookup only: Nexra never reads from or changes your operations systems through it.
Open Connect → Customer map in the console.
Add customers
One at a time: choose Add a customer to an asset and enter the asset or segment, the customer's name and, if you have them, their CRM id and another system's id.
From a file: choose Upload the customer map and pick a CSV file (up to 2 MB and 5,000 rows).
The file needs an asset column and a customer column. Optional columns are asset_name, crm_id and external_id. Nexra also accepts common alternatives such as segment, asset_id, customer_name, account_id and customer_id.
asset,asset_name,customer,crm_id
section-4,Section 4 pipeline,Northfield Power,0015g00000ABCDE
section-4,Section 4 pipeline,Riverside Bakery,0015g00000FGHIJ
substation-12,Substation 12,Harbour Cold Store,0015g00000KLMNOWhen you upload, choose what to do with what is already there:
Keep it, and add or update these customers (the default).
Replace the customers of the assets in this file: every asset named in the file keeps only the customers in the file. Assets not in the file are left alone.
A workspace can hold up to 50,000 entries. If a line can't be read, the upload stops and says which line to fix.
Use it
Filter by asset to see who an asset serves, or search by asset, customer or CRM id.
In a flow: the asset_customers.list built-in step returns the customers of one asset, ready for a step that repeats for each customer.
With Nexra Agent: ask "who is affected if section 4 is interrupted?". To add customers, Nexra Agent prepares the change and a different person who manages records approves it. For long lists, use the CSV upload instead.
Who can do what
Everyone who can see Connect, apart from documentation editors and billing administrators, can see the map.
Owners, admins, Connect operators and developers can add, upload and remove customers.
Over the API
All routes are under /api/console/connect and are in the API reference under Records.
| Method and path | What it does |
|---|---|
GET /asset-customers | The map. asset returns one asset's customers; q searches; limit up to 1,000 |
POST /asset-customers | Add a customer to an asset (assetKey, assetName, customerName, crmId, externalId) |
POST /asset-customers/upload | Upload CSV text: { "csv": "...", "mode": "add" } or "replace" |
DELETE /asset-customers/:assetCustomerId | Remove a customer from an asset |