Meraki Systems Manager for the North-West and Midlands offices (an extraordinarily long instance label)

Phase 1 preview — pages render fixture data only; no changes are saved.

Meraki Systems Manager for the North-West and Midlands offices (an extraordinarily long instance label)

Active

Ready to sync. Switched on with every required field set. Phase 1 never connects to the vendor.

Connection

Type: Meraki Systems Manager
Label: Meraki Systems Manager for the North-West and Midlands offices (an extraordinarily long instance label)
Address key: meraki-sm-with-an-extraordinarily-long-instance-label-for-the-north-west-and-midlands-offices
Company: Shared
Switched on: Yes
Push to vendor: Not supported by this type
Server: api.example.test
Created: 2026-09-01 10:00 Admin User

Only the host of the server address is shown. Credentials are stored encrypted and never leave the server.

Credentials and settings

Field	Value	Details	Actions
API key	Configured	Required
Organization ID	org-0001	Required

A secret is write-only: a blank input keeps the stored value.

Sync options

Asset tag pattern: TC-{serial}
Default category: Discovered Hardware
Default status: Deployed
Match people by: Username, then email
Create assets that don't exist: Yes
Adopt an existing asset by serial number: Yes
Fetch details per device: Yes
Suppress notifications: Yes
Check in when the vendor has no user: No

Field mapping

Vendor field	Stored in	Direction
Hostname	name	Vendor → asset
Serial number	serial	Vendor → asset
Asset tag	asset tag	Skipped
Model	model	Vendor → asset
MAC address	primary mac	Vendor → asset
IP address	primary ip	Vendor → asset
Operating system	os	Vendor → asset
OS version	os version	Vendor → asset
Last seen	last seen	Vendor → asset

Last sync

Last sync: Never

Legacy keeps only the latest result as free text: there is no run history.

Linked assets (0)

No linked assets

Devices appear here after a sync links them to assets.

Each asset links to at most one device per instance. Deleting an instance leaves these rows behind, and a new instance with the same address key picks them up again.