Service Now
ServiceNow is an enterprise workflow platform used for IT, employee, asset, facility, and operational service processes. In Keynius projects, ServiceNow is relevant when locker events need to become part of formal request, incident, asset, or employee-service workflows.
Services
- Enterprise workflow management
- IT service management
- Facilities and field service workflows
- REST API integration
- Asset and request process orchestration
Industries
- Corporate Workspace
- Healthcare
- Industrial & Logistics
- Government
- Education
Why Keynius + ServiceNow matters
Keynius and ServiceNow help enterprises connect physical locker activity to digital workflow governance. A locker can become the secure handover point for IT assets, employee equipment, parcels, keys, samples, or service parts, while ServiceNow tracks the request, approval, SLA, and service ownership. This is valuable for organizations that already rely on ServiceNow as a system of record and want locker events to support cleaner evidence, less manual ticket work, and better exception handling.
Compatibility
- Keynius Smart Locker Systems
- Keynius API/event workflows
- ServiceNow REST APIs
- Enterprise ITSM, ESM, asset, or facilities workflows
Access Methods
- SSO
- Web Browser Login
- Mobile App
- PIN
- QR Code
Integration
- REST API
- Workflow integration
- Ticket/request synchronization
- Asset handover event mapping
Best For
- Enterprise IT asset lockers
- Employee service desks
- Facilities operations
- Field service parts lockers
- Regulated asset handover
Integration Enablement
- Use ServiceNow as the workflow system of record while Keynius handles physical storage and access.
- Trigger ticket updates or fulfillment milestones from locker assignment, pickup, return, or expiry events.
- Give IT and facilities teams better evidence when resolving disputes or SLA questions.
Sample Use Cases
- New starter IT kits placed in lockers and marked fulfilled after pickup.
- Broken device returns where locker drop-off updates a ServiceNow incident.
- Facilities key or equipment handover controlled through approvals and locker audit logs.
Integration Enablement
Step 1
Identify the ServiceNow table, workflow, and status model that the locker process should update.
Step 2
Define field mapping for users, assets, request IDs, locker IDs, timestamps, and exception states.
Step 3
Configure ServiceNow API credentials and Keynius integration credentials in a test environment.
Step 4
Run end-to-end tests for request creation, locker assignment, pickup/return, timeout, cancellation, and failed sync.
Step 5
Document operational ownership for workflow changes, API errors, and user support.
Technical Requirements
Software
- Keynius platform/API access
- ServiceNow instance with REST API access
- Defined workflow/table scope
- Approved field mapping and status transitions
Network
- HTTPS/TLS 1.2 or higher
- Outbound port 443 from the Keynius integration environment
- Firewall allowlisting for partner API endpoints where required
- Stable internet connection for locker controllers, payment devices, or access readers in scope
Credentials
- ServiceNow integration user or OAuth credential
- Keynius integration token
- ServiceNow admin/developer support
- Test request, user, and asset records
Data and governance
- Use least-privilege roles for API access
- Map locker evidence to the correct workflow history
- Define retention and privacy rules
- Monitor failed syncs and duplicate updates
Need help with the Integration?
Our integration specialists are ready to guide you through the setup process.
%201.svg){kind=logo}
%201.svg){kind=icon}
