Feature Marketplace · Connectors
ServiceNow Connector
ServiceNow IT Service Management platform. Syncs incidents, users, configuration items, and change requests via the Table API with offset pagination and sys_updated_on based incremental tracking.
What syncs
The ServiceNow records STRAX brings into your hub.
Each kind of record is mapped once to your company model in the STRAX hub, then kept current in every system that needs it.
Incidents
IT incidents including state, priority, urgency, impact, category, and assignment details.
Users
Platform users including contact details, department, and account status.
Configuration Items
CMDB configuration items including class, asset tag, serial number, and operational status.
Change Requests
Change requests including type, state, risk, schedule, and assignment details.
ServiceNow data in your own SQL Server, then wherever it is needed.
STRAX is a self-hosted integration platform. The ServiceNow records land in the STRAX hub, a SQL Server database on your own servers, where your reports, portals and workflows read them. From there the hub delivers them to the other systems you connect, whether those run on SQL Server, MySQL, PostgreSQL or another API. STRAX signs in to ServiceNow with an API key that you provide, stored encrypted.
How STRAX connectors work → How the STRAX integration engine works → Connecting a system, in the documentation →
About this listing
| Version | 1.0.1 |
| Author | STRAX |
| Category | Connectors |
| Published | 2026-07-15 |
What's inside
| Connector profile | 1 |
Free listing
Install it from Feature Marketplace inside STRAX
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "ServiceNow Connector"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.