Skip to content
Business productivity ⇄ Storage

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

Keep ServiceNow and Sharepoint 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 Sharepoint

Land the records and documents that build up in ServiceNow into Sharepoint as they are created, and surface Sharepoint's file details on the ServiceNow records that point to them, without an export job to maintain.

ServiceNow and Sharepoint hold different kinds of data. ServiceNow carries records and the activity around them — the tickets, messages, orders, or issues a team works through, often with documents attached. Sharepoint holds files and the metadata that describes them. Where the two meet is narrow but real: much of what ServiceNow produces has to be kept somewhere durable, and many of the files Sharepoint stores are the very documents ServiceNow's records point to.

Stacksync syncs Knowledge Articles, Custom Tables, Incidents, Change Requests in ServiceNow with Permissions and sharing, Site pages, Sites, Lists in Sharepoint in real time. Records and attachments created in ServiceNow are written into Sharepoint as objects or files within seconds of being created. In the other direction, the metadata Sharepoint keeps about those files — name, location, owner, modified date — flows back onto the matching record in ServiceNow, so people see the current document without leaving the tool. Field-level mapping controls exactly what crosses over and in which direction, so you keep a durable copy of what matters without an extract to schedule or a nightly dump that leaves the copy a day behind.

Common use cases

  • 01 Create ServiceNow tickets automatically from CRM cases and sync status back as agents work them
  • 02 Bi-directional sync of incidents with engineering issue trackers so IT and engineering work the same ticket without re-keying
  • 03 Sync list columns and content types so database fields map onto SharePoint list fields and schema stays aligned as either side changes.
  • 04 Provision site and item permissions and sharing links from an IdP or access-management system so SharePoint access follows onboarding and offboarding.

Common sync patterns

Feed a data lake or downstream pipeline

Structured records from ServiceNow land in Sharepoint as objects a data lake, search index, or processing pipeline can read, without a custom extract to build and babysit.

Archive what ServiceNow produces into Sharepoint

Records and events from ServiceNow — tickets, messages, orders, or issues — are written into Sharepoint as objects or files as they change, giving you a durable, addressable copy for retention and audit.

Where ServiceNow generates attachments: keep the files in Sharepoint

Documents attached to records in ServiceNow land in the storage system automatically, with the source record holding a link back, so files live in one governed place instead of inside the tool.

What you can sync between ServiceNow and Sharepoint

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 Sharepoint objects How this pairing syncs
Change Requests Track planned changes; synced to deployment and release tooling. Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. Change Requests is specific to ServiceNow and Site pages to Sharepoint — each maps to any object or custom field on the other side.
Problems Root-cause records linked to incidents, useful in cross-system reporting. Sites SharePoint site collections and subsites via /sites; read site properties and discover the document libraries (drives) and lists each site contains, addressed by hostname and site path or site ID. Problems is specific to ServiceNow and Sites to Sharepoint — each maps to any object or custom field on the other side.
Service Catalog Requests Requested items and approvals that often trigger provisioning in other systems. Lists Custom lists and libraries via /sites/{id}/lists; create and read lists along with their columns and content types so a target system can mirror or provision list definitions. Service Catalog Requests is specific to ServiceNow and Lists to Sharepoint — each maps to any object or custom field on the other side.
Configuration Items (CMDB) Asset and infrastructure records synced with discovery tools and asset databases. List items Rows in a SharePoint list via /lists/{id}/items with a fields facet of column values; full create, read, update, and delete, synced two-way with database rows. Configuration Items (CMDB) is specific to ServiceNow and List items to Sharepoint — each maps to any object or custom field on the other side.
Users and Groups Sys_user and group tables synced with HR systems and identity providers. Drive items (document libraries) Files and folders in a library's drive via /drives and /drive/root; upload, download, move, delete, and read per-item metadata, synced two-way with a store. Users and Groups is specific to ServiceNow and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side.
Tasks The base task table that incidents, changes, and requests extend. Columns and content types Field definitions and content types on a site or list; read the schema and create columns so database fields map cleanly onto SharePoint list fields. Tasks is specific to ServiceNow and Columns and content types to Sharepoint — each maps to any object or custom field on the other side.

How changes propagate between ServiceNow and Sharepoint

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 Sharepoint 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 written to Sharepoint through its API, with automatic retries and rate-limit backoff.

Sharepoint ServiceNow Sub-second propagation

DetectionSharepoint notifies Stacksync of record changes through webhook events. Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last.

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.
  • Sharepoint: SharePoint Online throttles per app, returning HTTP 429 (or 503) with a Retry-After header in seconds and IETF RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers; throttled requests still count toward limits, so clients honor the greater of Retry-After and RateLimit-Reset with exponential backoff.
What ships with ServiceNow ⇄ Sharepoint

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever ServiceNow or Sharepoint 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 Sharepoint record.

Observability

Monitoring

Track your ServiceNow ⇄ Sharepoint 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 Sharepoint.

How the ServiceNow and Sharepoint 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

Sharepoint

Integration surface
Microsoft Graph REST API (graph.microsoft.com/v1.0 and beta) covering SharePoint sites, lists, list items, columns, content types, and document-library drives and drive items; plus the classic SharePoint REST API (_api/web) and CSOM. Supports Graph JSON $batch (up to 20 requests per call).
Authentication
OAuth 2.0 via the Microsoft identity platform (Microsoft Entra ID). An app registration holds delegated or application (app-only) scopes such as Sites.Read.All, Sites.ReadWrite.All, Sites.Selected, Sites.Manage.All, or Sites.FullControl.All, plus Files.ReadWrite.All for drive content; application permissions require tenant admin consent.
Change detection
Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last deltaLink; change-notification subscriptions (push webhooks) POST near-real-time notifications for list and drive/root changes to a notification URL and must be renewed before they expire. Classic SharePoint list webhooks are also available.
Capabilities
read · write · webhooks
Rate limits
SharePoint Online throttles per app, returning HTTP 429 (or 503) with a Retry-After header in seconds and IETF RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers; throttled requests still count toward limits, so clients honor the greater of Retry-After and RateLimit-Reset with exponential backoff.
How it works

How to connect ServiceNow to Sharepoint — 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 Sharepoint 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
    Sharepoint connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the ServiceNow and Sharepoint 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 ⇄ Sharepoint
    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 Sharepoint
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

ServiceNow and Sharepoint 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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

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

Popular · 7 of 476
All ServiceNow integrations All Sharepoint integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own