FRISS Spoke
-
- UpdatedJan 30, 2025
- 2 minutes to read
- Yokohama
- Now Platform Capabilities
Integrate a ServiceNow instance with your FRISS account to leverage the fraud detection capabilities for claims and to detect fraud early in the claims process.
Request apps on the Store
Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.
Subscription information
This spoke requires a subscription. Contact your ServiceNow account manager or sales representative for subscription details. For more information, see Legal schedules - IntegrationHub overview
Supported versions
This spoke was built for FRISS API version v 2.0 but may be compatible with later versions.
Key features
- Integrate with the FRISS API for Claims to save the scores returned by FRISS into the relevant claim data object.
- Detect fraud as you manage your claims cases.
- Get real-time scores of your claims data at different stages of the claims process.
- Use the user interface for portfolio monitoring.
Spoke dependencies
- ServiceNow IntegrationHub Action Step - REST (com.glide.hub.action_step.rest)
- ServiceNow IntegrationHub Runtime (com.glide.hub.integration.runtime)
- ServiceNow Flow Designer - Dynamic Inputs (com.glide.hub.dynamic_inputs)
- Some of these plugins may require the appropriate licensing if used outside the spoke implementation.
- The flow actions input parameter is provided for you to use. For more information on the sample input data structure and data types used in an array and object, see Complex data.
Spoke actions
The FRISS spoke provides actions that trigger FRISS Trust automation in response to events that occur within your ServiceNow instance. These actions are classified under the Claim Fraud Management category. Available actions include:
Connection and credential alias requirements
Integration Hub uses aliases to manage connection and credential information, and OAuth credentials. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you don't need to update any actions that use the connection.
For more information about setting up the FRISS spoke, see Set up the FRISS spoke.