Skip to content
CRM ⇄ Human resources

Intercom to Namely integration — real-time, two-way sync

Keep Intercom and Namely 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 Intercom and Namely

Keep the people who own accounts in Intercom in step with the workforce records in Namely, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.

Intercom runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Namely. Namely is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.

Stacksync syncs Custom Data Attributes, Tags, Segments, Admins & Teams in Intercom with Events, Profiles, Job Titles, Job Tiers in Namely field by field, in real time, and in both directions. You decide which system owns which fields, so Namely stays authoritative on roles and org structure while Intercom keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Mirror conversations and tickets into a warehouse for support analytics and SLA reporting
  • 02 Keep custom data attributes updated from billing or ERP systems so message segments reflect current plan and spend
  • 03 Push Groups and Teams (departments, locations, team categories) into downstream apps to keep org structure and reporting lines aligned.
  • 04 Feed Namely Reports as JSON into a database on a schedule for roster, turnover, and diversity dashboards without manual CSV exports.

Common sync patterns

Where Namely tracks people the business also engages: contacts stay in sync

A person recorded in Namely, such as a candidate or applicant, can create or update the matching contact in Intercom, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

New team members provisioned when they are hired

When Namely records a new hire, a matching user or owner is created in Intercom, so a new rep can start working accounts without waiting on a manual setup ticket.

Ownership and territory follow the org chart

When a person changes team, manager, or region in Namely, their accounts and territory assignments in Intercom update to match, so pipeline stays with the right owner.

What you can sync between Intercom and Namely

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.

Intercom objects Namely objects How this pairing syncs
Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. Events Home-feed items such as announcements, birthdays, anniversaries, and new arrivals; typically read-only into comms tools. Custom Data Attributes is specific to Intercom and Events to Namely — each maps to any object or custom field on the other side.
Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. Profiles The core employee record (personal, job, contact, and compensation fields); synced two-way via GET/POST/PUT with updated_at driving incremental polling. Tags is specific to Intercom and Profiles to Namely — each maps to any object or custom field on the other side.
Segments Saved audience definitions are readable for targeting parity across tools. Job Titles Job title definitions; read and written so titles stay aligned with an HRIS, directory, or reporting dimension. Segments is specific to Intercom and Job Titles to Namely — each maps to any object or custom field on the other side.
Admins & Teams Teammate records map conversation ownership to CRM users. Job Tiers Leveling hierarchy grouping zero-to-many Job Titles; read to map seniority into warehouse dimension tables. Admins & Teams is specific to Intercom and Job Tiers to Namely — each maps to any object or custom field on the other side.
Articles Help center content is accessible via API for knowledge sync and audits. Groups Departments and locations that organize Profiles; synced to keep org structure aligned with a warehouse or IdP. Articles is specific to Intercom and Groups to Namely — each maps to any object or custom field on the other side.
Contacts A single contact model covers both users and leads, distinguished by a role attribute. Teams Teams and team categories a Profile belongs to; read and written for org-chart and provisioning workflows. Contacts is specific to Intercom and Teams to Namely — each maps to any object or custom field on the other side.

How changes propagate between Intercom and Namely

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.

Intercom Namely Sub-second propagation

DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.

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

Namely Intercom Interval-based propagation

DetectionStacksync polls Namely for changes on an incremental schedule, reading only records changed since the previous pass. No webhooks.

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

Rate-limit considerations

  • Intercom: Subject to per-app rate limits on the Intercom API.
  • Namely: Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.
What ships with Intercom ⇄ Namely

Connect Intercom and Namely for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Intercom or Namely instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Intercom or Namely 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 Intercom or Namely record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Intercom and Namely.

How the Intercom and Namely connectors work

Intercom

Integration surface
REST API
Authentication
OAuth 2.0 for public apps or a workspace access token
Change detection
Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to per-app rate limits on the Intercom API

Namely

Integration surface
REST API (JSON over HTTPS)
Authentication
OAuth 2.0 authorization-code grant, or a personal access token sent as a Bearer token; all calls run over HTTPS against https://{subdomain}.namely.com/api/v1
Change detection
No webhooks; integrations poll GET endpoints and compare the updated_at / created_at timestamps on Profiles and related objects to detect changes
Capabilities
read · write
Rate limits
Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.
How it works

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

    Choose tables

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

Intercom and Namely 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 410 integrations available for Intercom and Namely.

Popular · 7 of 410
All Intercom integrations All Namely 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