
The FAMIS360 Destination connector sends Work Orders from the Mapped graph into FAMIS360, a CMMS commonly used in higher-education and facilities-management environments. It reads existing Work Order context from Mapped, creates or updates the corresponding FAMIS360 record, and writes the FAMIS360 Work Order identity back to the same Mapped Work Order.
The connector uses FAMIS360 username / password authentication.
| Field | Required | Description | Where to Find |
|---|---|---|---|
| Base URL | Yes | Your FAMIS360 instance URL | Your FAMIS360 administrator (for example https://your-instance.famis360.com) |
| Username | Yes | Username used to create and update Work Orders in FAMIS360 | Your FAMIS360 administrator |
| Password | Yes | Password used to access the FAMIS360 API | Your FAMIS360 administrator |
Use credentials with permission to create and update Work Orders.
The place-mapping step is used only to choose which FAMIS360 buildings are in scope for Work Order synchronization.
| Selection | Required | Notes |
|---|---|---|
| Selected buildings | Yes | Only Work Orders related to these buildings are sent to FAMIS360 |
Notes
The connector provides field mapping for the main FAMIS360 Work Order classification fields.
| Mapped Work Order field | FAMIS360 field |
|---|---|
| Job Priority | Request Priority |
| Sector | Request Type |
| Problem Description | Request Sub Type |
| Job Type | Work Type |
| Job Status | Status (updates only) |
Each mapping supports these behaviors:
| Option | Description |
|---|---|
| Enable / disable mapping | Pass mapped values, or leave the original graph value unmapped |
| Default value | Use a fallback FAMIS360 value when no explicit mapping is found |
| Undefined-only mode | Apply the default only when a source value has no explicit mapping |
The connector also refreshes FAMIS360 request-type / request-sub-type and building / request-type relationships so valid combinations can be reviewed before sync.
Historical Data Backfill
The data backfill lets you re-send or re-sync Work Orders that might have had changes or corrections.
| Mode | Description |
|---|---|
| Date range | Reprocess Work Orders created or updated during a selected time window |
| Specific IDs | Reprocess only the listed Mapped Work Order IDs. This must be the Mapped entity Id for the Work Order(s). |
Backfill uses the same create / update rules as normal polling.
| FAMIS360 destination behavior | Mapped entity | Exact type | Notes |
|---|---|---|---|
| Created or updated FAMIS360 Work Order | WorkOrder | WORK_ORDER | Existing Mapped Work Order remains in place; the connector adds or preserves the FAMIS360 identity |
| Synced FAMIS360 identity | ExternalIdentity on identities | N/A | Written as urn:famis360:workorder:id:<id> |
| Function | Frequency | Description |
|---|---|---|
| Work Order poll | Every 1 minute | Processes new and updated Mapped Work Orders for the selected buildings. On the first run, it looks back 2 hours. |
| Historical backfill | On demand | Replays Work Orders by date range or by specific Work Order IDs |
| Relationship refresh | First poll and on demand | Refreshes request-type, request-sub-type, and building relationship data used by the mapping workflow |
| Deprovision | On connector removal | Clears connector action state |
Syncing Requirements for Work Orders
The below query shows the related Space and identifies for Famis360 Work Orders. Read more about Work Orders.
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{ workOrders(filter: {connectedDataSourceId: {eq: "your-connector-Id"}}) { id name jobPriority jobStatus jobType summary dateCreated mappingKey identities { ... on ExternalIdentity { __typename value } } relatesTo { ... on GenericPlace { id name exactType mappingKey identities { ... on ExternalIdentity { __typename value } } } } } }