FSI CMS4 Destination

The FSI CMS Destination connector sends Work Orders from the Mapped Graph into FSI CMS (Facilities Services International). It creates or updates FSI tickets from selectable ticket sources and synchronizes related FSI assets.

Use Cases

• Route Work Orders from Mapped into FSI CMS: Send operational Work Orders from other Mapped-connected systems into the FSI workflow used by your facilities teams.
• Standardize multi-source maintenance intake: Use Mapped as the hub for Work Orders, then push only the approved subset into FSI CMS.
• Bulk migration and replay: Backfill historical Work Orders by date range or by specific Work Order IDs.

Configuration

The connector authenticates directly to the FSI CMS API and requires a segment selection so Work Orders are only written against the intended FSI scope.

Field	Required	Description	Where to Find
Username	Yes	FSI CMS username	Provided by your FSI CMS administrator
Password	Yes	FSI CMS password	Provided by your FSI CMS administrator
Site Code	Yes	FSI site code used for API access	Provided by your FSI CMS administrator
Subscription Key	Yes	API subscription key	Provided by your FSI CMS administrator
Segment	Yes	The FSI segment where Work Orders should be created and updated	Select from the connector UI after entering valid credentials
Each FSI CMS4 connector can only connect to one Segment at a time.

Select Buildings

You select the FSI buildings that should be eligible for sync.

Field	Required	Notes
Selected Buildings	Yes	The connector syncs only Work Orders related to places inside these FSI buildings and the configured segment.

Work Orders that are not related to the configured Buildings are ignored.

FSI Mappings

The FSI Mappings step maps Mapped Work Order values to FSI IDs.

Mapping Family	Maps From Mapped	Maps To FSI
Work Order Status	jobStatus	FSI Work Order status
Work Order Priority	jobPriority	FSI Work Order priority
Category	jobType	FSI Work Order category
Trade	sector	FSI trade

For each mapping family, you can:

• enable or disable the mapping family
• map each Mapped value to a specific FSI value
• optionally define a default FSI value
• optionally use the default only when a specific Mapped value does not already have its own mapping

If a required mapping family is enabled but a Work Order value has no usable mapping, that Work Order is skipped instead of being sent with incomplete required data.

Advanced Options

Source Connector Filter

The Settings section controls which source connectors are allowed to publish Work Orders into FSI CMS.

• If Source Connectors is not configured, Work Orders from all source connectors are eligible.
• If Source Connectors is configured but none are enabled, all Work Orders are filtered out.
• If one or more source connectors are enabled, only Work Orders from those enabled connectors are eligible.

Work Order Defaults

The Work Order Defaults section lets you set:

Option	Description
Default Billable Status	Applied to newly created FSI Work Orders after creation.
Default Common Problem	Written when the connector sends the Work Order, using the selected FSI common-problem value.

Historical Data Backfill

Backfill supports two modes:

Mode	Description
Date Range	Reprocesses Work Orders created or updated within a selected time window.
Specific IDs	Reprocesses only the Mapped Work Order IDs you provide. This must be the Mapped Entity Id for the Work Order.

Mapped Concepts

Concept	Mapped Entity	Notes
Ticket creation in FSI CMS	WorkOrder	The existing Mapped Work Order is updated with a destination identity so future runs use the update path.
FSI destination identifier	ExternalIdentity	Written in the format urn:fsi:workorder🆔<fsi-work-order-id>

Sync Behavior

Function	Frequency	Behavior
Work Order Poll	Every 2 minutes	Reads eligible Mapped Work Orders and creates or updates them in FSI CMS. On first run, it looks back 24 hours.
Asset Sync During Updates	As needed	Keeps FSI Work Order asset attachments aligned with the assets currently related to the Mapped Work Order.
Identity Write-Back	After successful create	Adds an FSI destination identity to the Mapped Work Order so later runs update the same FSI record.
Historical Data Backfill	On demand	Reprocesses Work Orders by date range or by specific Mapped Work Order IDs.

Notes

• The FSI Work Order description is built from the Mapped summary and description fields.
• If a Mapped Work Order includes a referenceUrl,, the connector sends it to FSI CMS as a clickable comment.
• Very long descriptions are shortened to fit FSI CMS field limits.
• Updates with no meaningful changes are skipped, which helps reduce unnecessary updates to FSI CMS.

Syncing Requirements for Work Orders

• The Work Order must originate from an enabled source connector under Source Connector Filter.
• The Work Order must be related to a location that's part of a selected Building in this connector's segment (configured in the Auth tab).
• If enum mapping is enabled, the Work Order's value for that mapping family must be mapped under FSI Mappings. If a required mapping family is enabled but a Work Order value has no usable mapping, that Work Order is skipped instead of being sent with incomplete required data.

Sample Code

You can query Work Orders by the connector's ID and identify related assets and places. Read more about Work Orders.

{
workOrders(filter: {connectedDataSourceId: {eq: "your-connector-Id"}}) {
  id
  name
  description
  dateCreated
  mappingKey
  identities {
  	...on ExternalIdentity {
  		__typename
  		value
  	}
  }
  relatesTo {
    ... on Thing {
      id
      name
      exactType
    }
    ... on Building {
      id
      name
      exactType
    }
    ... on Space {
      id
      name
      exactType
    }
  }
}
}