Skip to content
Business productivity ⇄ CRM

ServiceNow to Xactly integration — real-time, two-way sync

Keep ServiceNow and Xactly in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect ServiceNow and Xactly

Sync what happens in ServiceNow with the customer records in Xactly, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever ServiceNow holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Change Requests, Problems, Service Catalog Requests, Configuration Items (CMDB) in ServiceNow to Quotas / Targets, Payment Summary (Payable), Products & Customers, Orders in Xactly with bi-directional, real-time sync. Activity and record changes in ServiceNow update the matching contact or account in Xactly, and CRM data flows the other way wherever ServiceNow can store and use it.

Common use cases

  • 01 Mirror incident and task data into Postgres or a warehouse for SLA and workload reporting
  • 02 Create ServiceNow tickets automatically from CRM cases and sync status back as agents work them
  • 03 Mirror commission Transactions and Credits into a data warehouse to power rep-facing dashboards and comp-plan analytics without manual exports.
  • 04 Sync Participants, Positions, Titles, and Quotas from an HRIS/HCM and planning tools into Xactly so the org hierarchy and targets stay aligned with headcount changes.

Common sync patterns

Where ServiceNow supplies contact or company data

Enriched fields land directly on records in Xactly, and refreshes keep them from going stale.

Where ServiceNow can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Xactly sync into ServiceNow, so people working there have the context without switching tools.

Where ServiceNow handles support or shared inboxes

Tickets and conversations attach to the right contact and account in Xactly, so sales sees open issues before the next call.

What you can sync between ServiceNow and Xactly

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

ServiceNow objects Xactly objects How this pairing syncs
Users and Groups Sys_user and group tables synced with HR systems and identity providers. Orders Sales order and transaction records loaded into Incent as the raw input for crediting and calculation; created and updated through Connect load and ETL steps (write) and read back for reconciliation, so read and write. Users and Groups is specific to ServiceNow and Orders to Xactly — each maps to any object or custom field on the other side.
Tasks The base task table that incidents, changes, and requests extend. Credits Crediting records that tie an order to a participant and position; system-calculated credits are read, while manual and adjustment credits are loaded through Connect, so read and write. Tasks is specific to ServiceNow and Credits to Xactly — each maps to any object or custom field on the other side.
Knowledge Articles Support content that can be mirrored to help centers or search indexes. Transactions (Commission & Bonus) Calculated commission and bonus line items produced by Incent's calculation engine; read as the output of comp runs for reporting and downstream payout, so effectively read-only results. Knowledge Articles is specific to ServiceNow and Transactions (Commission & Bonus) to Xactly — each maps to any object or custom field on the other side.
Custom Tables Scoped or u_-prefixed tables are addressable through the same Table API as standard ones. Participants (Payees) Sales reps and payees keyed to positions; loaded and updated from HRIS/HCM source data through Connect (write) and read for roster reporting, so read and write. Custom Tables is specific to ServiceNow and Participants (Payees) to Xactly — each maps to any object or custom field on the other side.
Incidents The core ITSM ticket; commonly synced with engineering trackers and CRMs. Positions & Titles Org-hierarchy positions and titles that credits and quotas roll up to; loaded and maintained through Connect (write) and read to resolve the hierarchy, so read and write. Incidents is specific to ServiceNow and Positions & Titles to Xactly — each maps to any object or custom field on the other side.
Change Requests Track planned changes; synced to deployment and release tooling. Quotas / Targets Period quota and target values per position or plan; loaded from planning tools through Connect (write) and read for attainment reporting, so read and write. Change Requests is specific to ServiceNow and Quotas / Targets to Xactly — each maps to any object or custom field on the other side.

How changes propagate between ServiceNow and Xactly

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

ServiceNow Xactly Interval-based propagation

DetectionStacksync polls ServiceNow for changes on an incremental schedule, reading only records changed since the previous pass. Polling on sys_updated_on timestamps.

DeliveryEach detected change is applied to Xactly as a row-level write, with types converted between the two schemas.

Xactly ServiceNow Interval-based propagation

DetectionStacksync polls Xactly for changes on an incremental schedule, reading only records changed since the previous pass. No CDC log for external tools to consume.

DeliveryEach detected change is written to ServiceNow through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • ServiceNow: Subject to instance-level API rate limits and concurrency semaphores configured by administrators.
  • Xactly: Xactly does not publish numeric per-second rate limits. The Connect platform enforces query concurrency and long-running-query limits, so large extracts are paged and heavy loads/queries run as asynchronous Connect jobs (submit, then retrieve results) rather than row-by-row calls; batch loads are the supported path for high volume.
What ships with ServiceNow ⇄ Xactly

Connect ServiceNow and Xactly for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every ServiceNow–Xactly connection.

Real-time

Two-way sync

Changes in ServiceNow or Xactly instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever ServiceNow or Xactly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single ServiceNow or Xactly record.

Observability

Monitoring

Track your ServiceNow ⇄ Xactly sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between ServiceNow and Xactly.

How the ServiceNow and Xactly connectors work

ServiceNow

Integration surface
REST API (Table, Import Set, and Aggregate APIs); SOAP remains for legacy integrations
Authentication
OAuth 2.0 or basic authentication against the instance
Change detection
Polling on sys_updated_on timestamps; instance admins can configure outbound push through business rules or Flow Designer
Capabilities
read · write
Rate limits
Subject to instance-level API rate limits and concurrency semaphores configured by administrators

Xactly

Integration surface
Xactly Connect REST API v2 (JSON), plus ODBC/JDBC drivers over the same ANSI-SQL data model. Incent data is exposed as SQL-queryable objects (for example xactly_order, xactly_credit, xactly_transaction, xactly_payment); data is loaded and extracted through Connect load/query steps and server-side ETL Pipelines. The base host is region/pod-specific (for example https://<pod>.xactlycorp.com).
Authentication
OAuth 2.0 via the Xactly Connect API Gateway (bearer tokens issued on behalf of an Xactly Incent user), with HTTP Basic authentication using a dedicated Xactly Connect service-user's credentials also supported for the Connect REST API v2. The connecting user needs Connect/API access plus the relevant object permissions in Incent.
Change detection
No CDC log for external tools to consume. Incremental sync uses SQL predicates on modified/last-updated timestamp columns (for example WHERE modified_date > watermark) against Connect's queryable objects, or scheduled Connect ETL Pipelines that pull deltas since the last run. Xactly Connect has no outbound HTTP webhooks, so change detection is pull/ETL-based.
Capabilities
read · write
Rate limits
Xactly does not publish numeric per-second rate limits. The Connect platform enforces query concurrency and long-running-query limits, so large extracts are paged and heavy loads/queries run as asynchronous Connect jobs (submit, then retrieve results) rather than row-by-row calls; batch loads are the supported path for high volume.
Xactly setup guide
How it works

How to connect ServiceNow to Xactly — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate ServiceNow and Xactly with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    ServiceNow connected
    Xactly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the ServiceNow and Xactly objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · ServiceNow ⇄ Xactly
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    ServiceNow Xactly
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

ServiceNow and Xactly integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 508 integrations available for ServiceNow and Xactly.

Popular · 8 of 508
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.