The Benivo Integration Scoped Application is designed for enterprises that use ServiceNow to manage workflows and rely on Benivo to support global mobility programs. It provides a unified, automated connection between the two systems so HR, Mobility, IT, and Support teams can maintain accurate cases, tasks, and employee data without manual updates or duplicate effort.
Organizations often struggle with fragmented mobility information spread across platforms, leading to delays, inconsistent data, and inefficient case handling. This application solves those issues by synchronizing Tickets, Tasks, Users, Policies, Offices, and Services in real time. The result is faster resolution times, reduced manual work, and cleaner data across both systems. Customers also gain improved visibility into employee mobility journeys, fewer missed updates, and smoother collaboration between teams.
What sets this solution apart is its simplicity, security, and native fit within ServiceNow. It requires only ITSM, installs quickly, and uses secure OAuth 2.0 communication with upgrade-safe architecture. It delivers a standardized, supportable approach with preconfigured flows and Benivo Spoke actions that reduce implementation time and long-term maintenance costs. Enterprises get a reliable, scalable integration purpose-built for modern mobility operations.
Outbound Flows (ServiceNow → Benivo)
-
Incident → Benivo Ticket
-
Automatically creates or updates a Benivo Ticket whenever a ServiceNow Incident is created or updated.
-
-
Task → Benivo Task
-
Creates or updates a Benivo Task for any customer-selected task table.
-
-
User → Benivo User
-
Creates or updates a Benivo user profile when a user record is created or updated in ServiceNow.
-
Inbound Flows (Benivo → ServiceNow)
-
Benivo calls ServiceNow Table APIs to import:
-
Benivo Ticket staging table
-
Benivo Task staging table
-
-
Transform Maps move data from staging tables into:
-
The Incident table
-
The configured Task table
-
Master Data Imports
(Policies, Offices, Services)
-
Supported master data domains:
-
Policies → x_beniv_benivo_policy
-
Offices → x_beniv_benivo_office
-
Services → x_beniv_benivo_service
-
-
Each domain includes:
-
An Import Set table
(x_beniv_benivo_import_benivo_policy,
x_beniv_benivo_import_benivo_office,
x_beniv_benivo_import_benivo_service) -
A Data Source with scripted loader
-
A Scheduled Import Set
-
A Transform Map into its target table
-
-
Scheduled Import Sets run daily to ensure Policies, Offices, and Services remain synchronized.
Access Token Handling
-
A dedicated “Get Access Token” REST endpoint retrieves an access token from Benivo.
-
The token is stored in a system property.
-
It is automatically used as a Bearer token in Authorization headers for all Policies, Offices, and Services API calls.
Benivo Integration Scoped Application – Release Notes (v1.0.0) Initial Public Release Overview
Version 1.0.0 marks the first public release of the Benivo Integration Scoped Application, providing secure, bidirectional integration between ServiceNow and Benivo.
This release delivers the core foundation required to synchronize mobility-related data and automate key workflows across both platforms.
Highlights
-
Bidirectional sync for Tickets, Tasks, Users, Policies, and Offices
-
Benivo ServiceNow Spoke with prebuilt flows and actions
-
Secure OAuth 2.0–based authentication
-
Scoped Application architecture with administrative configuration UI
Notes
-
This release includes core synchronization capabilities
-
Additional automation and enhancements will be introduced in future versions
Required ServiceNow Products and Plugins
The Benivo Integration Scoped Application depends on the following ServiceNow components.
Required Product
ServiceNow ITSM (Information Technology Service Management)
-
Used for Ticket and Task workflows that synchronize with Benivo.
-
Provides the core Incident/Task tables leveraged by the integration.
No Other Products or Plugins Required
The Benivo Integration Scoped Application does not require any of the following:
-
HRSD / HR Core – Not required
-
CSM – Not required
-
ITOM, MID Server, Security Operations, Asset, SAM, etc. – Not required
-
Incident / Problem / Change plugins – Not required
-
(Only needed if a client explicitly chooses to map Benivo Tickets to those modules — the app itself does not depend on them.)
-