Docs Portal

WebTMA Source

WebTMA logo

The WebTMA Source connector imports CMMS data from WebTMA into the Mapped graph. It brings in your location hierarchy, equipment assets, Work Orders, and service requests so operations teams can query maintenance activity alongside Buildings, Spaces, and other connected systems.

Use Cases

Unified maintenance visibility: View WebTMA work orders and service requests in the same graph as your buildings, spaces, and equipment.
Asset and location context: Link tickets to mapped buildings, floors, spaces, and equipment for better troubleshooting and reporting.
Portfolio-wide CMMS analytics: Analyze backlog, priority, request status, and maintenance activity across multiple sites in a consistent graph model.

Configuration

Auth Requirements

Provide the WebTMA credentials used to access your tenant.

Field	Required	Description	Where to Find
Client Name	Yes	Your WebTMA client or tenant name	Provided by your WebTMA administrator
Username	Yes	WebTMA username for API access	Provided by your WebTMA administrator
Password	Yes	Password for the WebTMA user	Provided by your WebTMA administrator

Place Mappings

The connector reads WebTMA areas and builds a location mapping table for the hierarchy it will create in Mapped.

Mapping Field	Required	Description	Notes
Site ID	Yes	Groups buildings under a site when present	Used to create or associate a Site above the building
Building Name	Yes	Building name from WebTMA	Used for the Building entity
Building Address	Yes	Building address details	Used when available for building metadata
Floor Name	Yes	Floor or level name	Used for the Floor entity name
Floor Level	Yes	Numeric floor level	Helps standardize floor ordering with FloorLevelIdentity value
Space Name	Yes	Room or area name	Used for the Space entity
Space Ref ID	Yes	Unique room or area identifier	Used for identity matching
Space Code	Yes	Room number or short code	Useful for room lookup and naming

Save the mapping step before syncing assets or ticket data. The connector uses these place mappings to relate work orders, service requests, and assets to the correct building, floor, or space.

Asset Type Mapping

WebTMA equipment types are mapped to Mapped exact types for the Thing entities created during asset sync.

Option	Description
Asset Type Mapping	Maps each WebTMA equipment type to a Mapped exact type such as AHU, FAN, PUMP, or a more general THING
Asset Sync Building Selection	Lets you choose which mapped buildings should be included when running an asset sync

Asset syncing is started from the Asset Mappings step after you save the mappings.

Advanced Options

Option	Description
Polling Work Orders	Enables continuous syncing of WebTMA work orders into Mapped
Polling Service Requests	Enables continuous syncing of WebTMA service requests into Mapped
Backfill	Lets you sync historical work orders and service requests by date range or by specific WebTMA IDs

Mapped Concepts

API to Mapped Entities

WebTMA data	Mapped entity	Exact type	Relationships created
Site/building mapping	Site	SITE	hasPart to buildings
Building mapping	Building	BUILDING	isPartOf site, hasPart floors
Floor mapping	Floor	FLOOR	isPartOf building, hasPart spaces
Area / room mapping	Space	Varies by Mapped place model	isPartOf floor
Equipment record	Thing	User-mapped exact type	hasLocation building, floor, or space
Equipment model data	DeviceModel	DEVICE_MODEL	Linked from the related Thing
Work order	WorkOrder	WORK_ORDER	relatesTo places and equipment, hasAssignedGroup, hasAssignee, isCreatedBy, isClosedBy
Service request	ServiceRequest	SERVICE_REQUEST	relatesTo places and equipment, isReportedBy, hasAssignee, isResponsibilityOf
Requestor / technician / closer	Person	PERSON	Linked from work orders and service requests
Repair center	PeopleGroup	PEOPLE_GROUP	Linked from work orders or service requests; may also hasMember assigned people

Each synced record also receives WebTMA external identities in the identities field so it can be matched back to its source record.

Sample Code

Query Work Orders

Read more about querying Work Orders in the Mapped Graph.

Request ResponseCopy1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
{
  workOrders(filter: {connectedDataSourceId: {eq: "your-connector-Id"}}) {
    id
    name
    exactType
    mappingKey
    dateCreated
    dateUpdated
    dateClosed
    jobPriority
    jobStatus
    jobType
    sector
    description
    summary
    hasAssignedGroup {
      name
    }
    isReportedBy {
      name
    }
    hasAssignee {
      name
    }
    isClosedBy {
      name
    }
    isCreatedBy {
      name
    }
    identities {
      ... on ExternalIdentity {
        __typename
        value
      }
    }
    relatesTo {
      ... on Building {
        id
        name
        exactType
        identities {
          ... on ExternalIdentity {
            __typename
            value
          }
        }
      }
      ... on Floor {
        id
        name
        exactType
        identities {
          ... on ExternalIdentity {
            __typename
            value
          }
        }
      }
      ... on Space {
        id
        name
        exactType
        identities {
          ... on ExternalIdentity {
            __typename
            value
          }
        }
      }
      ... on Thing {
        id
        name
        exactType
        identities {
          ... on ExternalIdentity {
            __typename
            value
          }
        }
      }
    }
  }
}