Workwize
Visualize Workwize assets and employees, map assets to device owners, and monitor changes through queries and alerts.
- Installation
- Data Model
- Types
Installation
For this integration, you will need to generate an API Token in Workwize before initiating the integration in JupiterOne. Once the API Token has been retrieved, proceed to JupiterOne to continue.
Configuration in Workwize
- Log in to your Workwize account.
- Navigate to Settings > API.
- Click Generate API Token or Create New Token.
- Copy and securely save the generated API Token for use in JupiterOne.
API tokens should be treated securely and not shared. Ensure the user generating the token has sufficient permissions to access asset and employee data.
Configuration in JupiterOne
To complete the Workwize integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Workwize. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
The Account Name used to identify the Workwize account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen theAccountNametoggle is enabled. -
Description to assist in identifying the integration instance, if desired.
-
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration. -
The Workwize API Token generated for use with JupiterOne.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Asset | workwize_asset | Device |
| Employee | workwize_employee | User |
| Organization | workwize_organization | Account |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
workwize_employee | OWNS | workwize_asset |
workwize_organization | HAS | workwize_employee |
Workwize Asset
workwize_asset inherits from Device
| Property | Type | Description | Specifications |
|---|---|---|---|
category * | string | ||
condition * | string | ||
invoiceCurrency * | string | null | ||
invoicePrice * | number | null | ||
warehouseStatus * | string |
Workwize Employee
workwize_employee inherits from User
| Property | Type | Description | Specifications |
|---|---|---|---|
departmentId * | number | null | ||
departmentName * | string | null | ||
foreignId * | string | null | ||
isDeactivated * | boolean | ||
jobTitle * | string | null | ||
registrationStatus * | string | ||
team * | string | ||
userId * | number |
Workwize Organization
workwize_organization inherits from Account