Incident IQ FileWave Asset Integration
Quick answer: Incident IQ, often styled by Incident IQ as iiQ and sometimes searched for as IIQ or IncidentIQ, can use the FileWave MDM integration to sync FileWave asset data into Incident IQ. To configure the integration, provide Incident IQ with your FileWave Server Address URL and a base64 FileWave Application Token.
Incident IQ describes its FileWave integration as an Asset & MDM integration that can sync detailed asset data between FileWave and Incident IQ, show asset metadata, and support reporting with MDM data. This FileWave article covers the FileWave-side values needed for that setup.
Third Party Software
Incident IQ is a third-party application. Incident IQ’s UI, field labels, and integration behavior are controlled by Incident IQ. The steps below explain where to find the FileWave values that Incident IQ asks for.
Terminology
Use Incident IQ when referring to the company or platform. Incident IQ uses the iiQ style for products such as iiQ Ticketing and iiQ Assets. Because many districts also write the acronym as IIQ or write the name without a space as IncidentIQ, this article includes those forms for searchability while using Incident IQ as the main product name.
Before you begin
Make sure you have:
- Access to FileWave Central.
- Administrative permissions in FileWave.
- Access to configure apps or integrations in Incident IQ.
- The FileWave Server Address URL.
- A FileWave Application Token in base64 format.
Information required by Incident IQ
Incident IQ typically asks for these FileWave values when configuring the FileWave integration:
| Incident IQ field | FileWave value to provide |
|---|---|
| Server Address URL | The FileWave server address used by Incident IQ to connect to your FileWave environment. |
| Token | The FileWave Application Token in base64 format. |
| Token End Date, Token Expiration Date, or similar date field | FileWave application tokens do not expose an expiration date in the value you copy. Enter a customer-appropriate future review or rotation date according to your organization’s credential policy. |
Locate the FileWave Server Address URL
- Open FileWave Central.
- Go to Preferences.
- Select Mobile.
- Locate the Server Address URL field.
- Copy the server address URL.
Enter this value in Incident IQ as the FileWave server address.
Create or locate a FileWave Application Token
For security and auditing, use a dedicated FileWave administrator account for the Incident IQ integration instead of a personal administrator account. Grant only the permissions required for the integration to function.
- Open FileWave Central.
- Go to Assistants > Manage Administrators.
- Create or select the administrator account that will be used for the Incident IQ integration.
- Open the Application Tokens tab.
- Locate Token (base64).
- Copy the token value.
Enter this value in Incident IQ as the authentication token.
Configure the FileWave integration in Incident IQ
- Sign in to Incident IQ with an account that can manage apps or integrations.
- Open the FileWave integration settings in Incident IQ.
- Enter the FileWave Server Address URL copied from FileWave Central.
- Enter the FileWave Application Token copied from FileWave Central.
- If Incident IQ requires a token end date, expiration date, or similar validation date, enter a future date that aligns with your organization’s token review or credential rotation policy.
- Save the integration settings.
- Test or validate the connection, if Incident IQ provides that option.
After configuration
After the integration is active, confirm that FileWave asset data is appearing in Incident IQ. Incident IQ’s FileWave integration page says districts can sync detailed asset data, view asset metadata, generate reports using MDM data, and choose mapping options for FileWave fields.
If data is missing or does not appear as expected, review the FileWave token permissions, confirm the server URL is reachable by Incident IQ, and check the mapping options in Incident IQ.
Security notes
- Treat the FileWave Application Token as sensitive information because it grants API access through the integration.
- Do not share the token publicly or store it in unsecured locations.
- If the token is exposed or no longer needed, regenerate or replace it according to your organization’s security procedures.
- Review the dedicated administrator account and token periodically according to your organization’s credential rotation policy.