Integration Products | Campaign Creators

ServiceNow HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 19, 2026, 6:08:01 AM
Integration Assessment
Integration Assessment · Enterprise

ServiceNow × HubSpot

How customer service work in ServiceNow (cases, incidents, problems, install base and entitlements) can reach HubSpot, so sales, account managers and marketing see each account's service health next to its pipeline and renewals, and how a won deal in HubSpot can start onboarding in ServiceNow.

Table API (REST)Import Set APIScripted REST APIsBusiness rules + outbound RESTCSM cases, accounts, contactsInstall base and entitlements
Platform ownerServiceNow, Inc.
Integration typeCustom build on ServiceNow's REST APIs
Primary directionTwo-way, ServiceNow → HubSpot first
FeasibilityStrong fit
API accessOpen API
01 — Summary

Does ServiceNow integrate with HubSpot?

Many enterprises run customer service in ServiceNow and run marketing, sales and renewals in HubSpot. The service team works the case. The people who renew and expand the account need to know how service is going before they call.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. Self-serve for the client's admin: the REST APIs are documented publicly, and a dedicated integration user holds only the roles it needs.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

Every ServiceNow table is reachable through a documented REST API, so HubSpot can show the service health of every account and hand new customers to the service team the moment a deal closes.

Campaign Creators assessment

CC builds this directly on ServiceNow's REST APIs. The Table API reads and writes any table the integration user is allowed to see, including the Customer Service Management (CSM) tables for accounts, contacts and cases. Business rules call a CC-hosted endpoint through outbound REST messages when records change. The Import Set API and a Scripted REST endpoint receive data from HubSpot, so ServiceNow's own transform rules decide how it lands. Two things set the pace: the client's ServiceNow admin grants roles and rate limits for the integration user, and the client decides which system owns the account record.

Scorecard
API accessOpen, role-based
Public docsExtensive
Rate limitsSet per instance
Build complexityMod–High

Ratings are CC judgments from ServiceNow's public API documentation. Table names, fields, roles and rate-limit rules are confirmed against the client's instance during discovery, because every instance is configured differently.

Strength

One API reaches every table

The Table API reads and writes any table by name, with encoded queries, field lists and paging. Cases, incidents, problems, install base and entitlements all use the same pattern.

Plan for

Each instance is configured differently

Custom fields (u_ prefix), custom case states, access controls and rate-limit rules vary by instance. CC inventories the client's instance before the field list is signed.

Gate

Agree who owns the account

ServiceNow CSM accounts and HubSpot companies describe the same customers. The client decides which system creates accounts and which fields each side may change before any build starts.

02 — API modules

Which ServiceNow APIs does the integration use?

Seven parts of ServiceNow matter to HubSpot. Four carry the core sync, two add service context, and one carries HubSpot data back into ServiceNow.

Core

Table API

/api/now/table/{tableName}

Create, read, update and delete records on any ServiceNow table, filtered with encoded queries.

  • sysparm_query, sysparm_fields and sysparm_limit
  • Paging with sysparm_offset and the Link header
  • X-Total-Count header for reconciliation
Core

CSM accounts, contacts & consumers

customer_account · customer_contact · csm_consumer

The customers the service team supports: business accounts, their contacts, and individual consumers where the client serves them.

  • Accounts matched to HubSpot companies on domain or ID
  • Contacts matched on email
  • Account hierarchy kept as parent and child companies
Core

Cases

sn_customerservice_case

Customer service cases with state, priority, account, contact, product and assignment. They become HubSpot tickets in a ServiceNow pipeline.

  • One HubSpot ticket per case, read-only in HubSpot
  • State and priority mapped to pipeline stages
  • Assigned agent matched to a HubSpot owner on email
Context

Incidents & problems

incident · problem

For clients that also run IT service management, incidents and problems that affect a customer account roll up to the HubSpot company as health signals.

  • Open and priority 1 incidents per account
  • Open problems linked to the account
  • Counts and dates, not the full records
Context

Install base & entitlements

sn_install_base_item · service_entitlement

What each customer owns (install base items and sold products) and what support they are entitled to, including entitlement end dates.

  • Installed products as a HubSpot custom object
  • Entitlement end dates as renewal signals
  • Case entitlements show what support was used
Integration path

Business rules & outbound REST

RESTMessageV2 · async business rules

Business rules run when a record is inserted or updated, and an outbound REST message notifies a CC-hosted endpoint, so changes reach HubSpot as they happen.

  • Runs after the database commit, asynchronously
  • Sends the record sys_id; the layer fetches the rest
  • Scheduled query by sys_updated_on as a safety net
HubSpot → ServiceNow

Import Set API & Scripted REST

/api/now/import/{stagingTable}

Data from HubSpot lands in a staging table, and transform maps write it to the target table. A Scripted REST endpoint can take a won deal and open onboarding in one call.

  • ServiceNow's own transform rules apply
  • insertMultiple for batches
  • Onboarding case or request from a won deal
03 — Framework

How does the ServiceNow HubSpot integration work?

ServiceNow business rules notify a CC-hosted endpoint when cases and accounts change. The integration layer fetches the full record through the Table API, matches the account and contact to HubSpot, computes service-health rollups and writes in batches. HubSpot sends won deals and account context back through the Import Set API or a Scripted REST endpoint.

ServiceNow instance
Business rulesoutbound REST on insert and update
Table APIcases, accounts, contacts
ITSM tablesincidents, problems
Install base & entitlementsproducts owned, support terms
CC integration layer
Webhook endpointauthenticated, fast acknowledgement
Record fetcherTable API, paced under the rate limit
Identity resolversys_id · email · domain
Health rollupsopen cases, P1 incidents, entitlements
HubSpot writerbatch upserts, associations, replay
HubSpot
Companiesservice health, entitlement end
ContactsCSM contacts matched on email
TicketsServiceNow case pipeline
Installed Products (custom object)install base items
Dealsrenewals and onboarding status
ServiceNow → HubSpot (cases, health signals, install base)HubSpot → ServiceNow (won deals as onboarding, account owner and renewal date)
Principle

ServiceNow owns the service work

Agents work cases and incidents in ServiceNow. HubSpot holds a read-only copy for context and reporting and never changes a case state.

Principle

HubSpot owns the revenue relationship

Companies, contacts, owners and deals live in HubSpot. ServiceNow receives the account context its agents need and a clean handoff when a deal closes.

Principle

Signals over transcripts

HubSpot stores counts, dates, states and flags. Work notes, comments and attachments stay in ServiceNow, linked by case number.

04 — Process

What does ServiceNow HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. ServiceNow → HubSpot goes live first, then the onboarding handoff from HubSpot.

1

Discovery & instance inventory

List the CSM and ITSM tables in use, custom fields and case states, the account model (business accounts, consumers or both), and the instances (development, test, production).

Gate to next phaseSigned table and field inventory
2

Access & integration user

The client's ServiceNow admin creates a dedicated integration user with read roles on the agreed tables, write access to the staging tables, an OAuth client, and a rate-limit rule sized for the sync.

Gate to next phaseTest calls succeed against the sub-production instance
3

Ownership & identity

Agree which system creates accounts and contacts, which fields each side may change, and the match rules (sys_id once linked; email for contacts; domain for accounts).

Gate to next phaseSigned ownership matrix and match rules
4

HubSpot data model

Create the ServiceNow ticket pipeline, the Installed Products custom object, custom properties, association labels and property groups in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build

Build the business rules and outbound REST messages with the client's admin, the CC endpoint, record fetcher, health rollups, ticket and install base sync, and the onboarding handoff through the Import Set API or Scripted REST.

Gate to next phaseAll agreed tables syncing between sandbox and sub-production
6

Backfill

Load accounts, contacts and an agreed case history window in pages, paced under the rate limit, then compute rollups once so company views start complete.

Gate to next phaseHubSpot counts reconcile to ServiceNow X-Total-Count for the agreed window
7

Workflows, parallel run & launch

Build renewal-risk alerts, onboarding notifications and service views with notifications paused, run two weeks in parallel, then switch on in production.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the ServiceNow HubSpot integration sync?

Table names follow ServiceNow's documentation. Field names shown are standard ServiceNow fields; each instance can add custom fields (u_ prefix) and change choice values, so every row is confirmed against the client's instance in discovery.

ServiceNow fieldHubSpot propertyObjectDirectionNotes
Accounts & contacts · CSM
customer_account.sys_idsn_account_sys_idCompanySN → HSMatch key once linked. Unique.
customer_account.numbersn_account_numberCompanySN → HSHuman-readable account number.
customer_account.namenameCompany↔ BothOwner agreed in discovery. HubSpot creates prospects; ServiceNow receives them at onboarding.
customer_account websitedomainCompany↔ BothPrimary match key before linking. Confirm field use in discovery.
customer_account.parentParent company associationCompanySN → HSKeeps the account hierarchy.
customer_contact.sys_idsn_contact_sys_idContactSN → HSMatch key once linked.
customer_contact.emailemailContact↔ BothMatch key. Support-only contacts can be set as non-marketing.
first_name, last_name, phonefirstname, lastname, phoneContact↔ BothFill blanks only in each direction.
customer_contact.accountContact to company associationContactSN → HS
Cases · sn_customerservice_case
numbersn_case_numberTicketSN → HSMatch key. Unique.
short_descriptionsubjectTicketSN → HS
statehs_pipeline_stageTicketSN → HSServiceNow case pipeline. Choice values confirmed per instance.
priorityhs_ticket_priorityTicketSN → HSMapped to Low, Medium, High, Urgent.
account, contactTicket associationsTicketSN → HSAssociated to the HubSpot company and contact.
assigned_tohubspot_owner_idTicketSN → HSMatched on agent email. Unmatched agents leave owner blank.
assignment_groupsn_assignment_groupTicketSN → HSGroup name from the reference field.
productsn_productTicketSN → HSDisplay value of the product reference.
opened_at, resolved_at, closed_atcreatedate, sn_resolved_at, closed_dateTicketSN → HS
Incidents, problems & install base
incident (open, by account)sn_open_incidentsCompanySN → HSComputed in the integration layer. Account field confirmed per instance.
incident (priority 1, last 90 days)sn_p1_incidents_90dCompanySN → HSComputed in the integration layer.
problem (open, linked to account)sn_open_problemsCompanySN → HSOnly where problems link to customer accounts.
sn_install_base_itemInstalled Product (custom object)Custom objectSN → HSProduct, serial or name, status, install date. Associated to the company.
service_entitlement end datesn_entitlement_endCompanySN → HSEarliest active entitlement end. Renewal signal.
Revenue context & onboarding
Deal closed wonOnboarding case or catalog requestDealHS → SNSent through the Import Set API or a Scripted REST endpoint. Target table agreed in discovery.
Deal line itemsOnboarding request detailsLine itemHS → SNListed on the onboarding record so the service team sees what was sold.
Company owner, tier, renewal datecustomer_account custom fields (u_)CompanyHS → SNAgents see the account's commercial context.
Onboarding case statesn_onboarding_statusDealSN → HSShows sales and success where onboarding stands.
Open cases, P1 incidents, entitlementssn_service_healthCompanySN → HSGreen, amber or red, from rules the client signs off.
06 — Auth & API

How are authentication and API limits handled?

ServiceNow access is granted by the client's instance admin. Values below come from ServiceNow's public API documentation; instance-specific settings are confirmed in discovery.

TopicServiceNowHubSpot
Access modelSelf-serve for the client's admin. A dedicated integration user holds only the roles the sync needs; access controls on each table decide what the API returns.Private app access token or OAuth 2.0 public app, scoped per object.
InterfacesREST over HTTPS at the client's instance URL: Table API (/api/now/table/), Import Set API (/api/now/import/), and Scripted REST APIs the client hosts. JSON or XML.REST APIs: CRM objects, tickets, custom objects, associations, properties.
AuthenticationOAuth 2.0 (authorization code, client credentials or JWT bearer) through an OAuth application registered in the instance, or basic auth for the integration user. CC recommends OAuth.Bearer token on every call.
Rate limitsSet by the instance admin as inbound REST rate-limit rules, per user, role or all users, per hour. Exceeded calls return 429 with a Retry-After header. No default is published; confirm the rule for the integration user.Per-10-second burst and daily limits by subscription tier.
Paging & volumeTable API pages with sysparm_limit and sysparm_offset; the Link and X-Total-Count headers support paging and reconciliation. The Table API inserts one record per call; insertMultiple on the Import Set API handles batches.Batch endpoints handle volume.
Change detectionAsync business rules call a CC endpoint through outbound REST messages on insert and update. A scheduled Table API query on sys_updated_on catches anything a rule misses.HubSpot workflows trigger the outbound handoff and account context.
Instances & environmentsEach client has its own instance URL, usually with development and test instances. Instance clones copy production data and settings, so endpoints and credentials are re-pointed after each clone.HubSpot sandbox for build and testing; production portal at launch.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Account ownership between systemsHigh

ServiceNow accounts and HubSpot companies overlap. Without a signed rule for who creates and edits accounts, duplicates follow. The rule is agreed before the build.

Rate-limit rule set by the clientMedium

ServiceNow does not publish a default. The client's admin creates a rule for the integration user sized for the backfill and the live sync, and the layer backs off on 429 responses.

Access controls shape the dataMedium

The API returns only what the integration user's roles allow, and sysparm_limit applies before access checks. Roles are tested against known records before backfill.

Instance clonesMedium

Cloning production into a test instance copies business rules that call the CC endpoint. Clone settings exclude or re-point them so test data never reaches the production portal.

Case volume in HubSpotMedium

Large service desks create many cases. HubSpot stores open cases and an agreed history window; older cases stay in ServiceNow and count toward rollups only.

Custom fields and states varyLow

Each instance has its own u_ fields and case states. The inventory is signed in discovery, and new values are flagged before they sync.

Opportunities in HubSpot

Renewal risk on the dealHigh value

Open escalations, priority 1 incidents and expiring entitlements attach to the renewal deal and alert the account owner before the renewal conversation.

A clean handoff at closeHigh value

A won deal opens onboarding in ServiceNow with the account, contacts and what was sold, so the service team starts with full context.

Service context before every callHigh value

Open cases, recent incidents and service health sit on the company record, so no one pitches into an unresolved problem.

Expansion from the install baseMedium value

Installed products and entitlement dates become HubSpot lists for upgrade, add-on and renewal campaigns.

Smarter marketing sendsMedium value

Contacts at accounts with open priority 1 incidents can be held out of promotional sends until service recovers.

One view of account healthMedium value

Service health, pipeline and product usage meet in HubSpot dashboards for leaders and customer success.

The core customer journey

From closed deal to renewal, each system does its job.

The integration follows one customer from the signed deal through service to the renewal conversation, with ServiceNow running the service work and HubSpot running the relationship.

  1. A deal closes in HubSpot and opens an onboarding case or request in ServiceNow with the account, contacts and line items.
  2. Cases, incidents and entitlements update the HubSpot company and its service-health rollup.
  3. An escalation, a priority 1 incident or an expiring entitlement attaches to the renewal deal and alerts the owner.
  4. HubSpot sends the owner, tier and renewal date back, so agents know the account's stakes.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the sn_ prefix in a ServiceNow property group. Standard HubSpot ticket properties are used wherever one fits. Rollups are calculated in the integration layer so every report agrees.

Internal nameLabelObjectTypeSource / logic
sn_account_sys_idServiceNow Account IDCompanySingle-line textcustomer_account sys_id; unique
sn_account_numberServiceNow Account NumberCompanySingle-line textcustomer_account number
sn_contact_sys_idServiceNow Contact IDContactSingle-line textcustomer_contact sys_id; unique
sn_case_numberServiceNow Case NumberTicketSingle-line textCase number; unique
sn_assignment_groupAssignment GroupTicketDropdownCase assignment group
sn_productServiceNow ProductTicketDropdownCase product display value
sn_open_casesOpen ServiceNow CasesCompanyNumberCount of cases not resolved, closed or cancelled
sn_open_incidentsOpen IncidentsCompanyNumberCount of open incidents for the account
sn_p1_incidents_90dP1 Incidents (90 days)CompanyNumberPriority 1 incidents in 90 days
sn_entitlement_endEntitlement End DateCompanyDate pickerEarliest active entitlement end
sn_service_healthService HealthCompanyDropdownGreen, amber or red from signed rules
sn_onboarding_statusOnboarding StatusDealDropdownState of the onboarding case
09 — Scope builder

Interactive scope builder

Choose the tables and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
ServiceNow × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

ServiceNow HubSpot integration FAQ

Does ServiceNow integrate with HubSpot?

Yes, through a custom build on ServiceNow's REST APIs. The Table API reads and writes the Customer Service Management tables for accounts, contacts and cases, business rules notify a CC-hosted endpoint when records change, and the Import Set API or a Scripted REST endpoint receives data from HubSpot.

What data syncs between ServiceNow and HubSpot?

ServiceNow accounts and contacts match to HubSpot companies and contacts, and cases become read-only tickets in a ServiceNow pipeline. Incidents, problems, install base items and entitlement end dates roll up to the company as service-health and renewal signals. Won HubSpot deals go back to ServiceNow to start onboarding.

Which system owns which data?

ServiceNow owns the service work: agents work cases and incidents there, and HubSpot never changes a case state. HubSpot owns the revenue relationship, including pipeline, renewals and marketing. The client decides which system creates accounts and which fields each side may change before the build starts.

What does setting up the ServiceNow HubSpot integration involve?

Seven phases, each closed by a client sign-off: discovery and an instance inventory, access and a dedicated integration user, ownership and identity rules, the HubSpot data model, the build, a backfill, and a parallel run before workflows are switched on.

How long does the integration take and what does it cost?

Timeline and cost depend on the ServiceNow tables and custom fields in scope, how the client's instance is configured, the history to load, and whether onboarding write-back is included. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.