Skip to content
CRM

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

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

Run Intercom and Vitally side by side with the same accounts and contacts in both, whether they serve different teams or one is replacing the other.

Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.

Stacksync syncs Contacts, Companies, Conversations, Tickets in Intercom with Custom Trait, Account, User, Organization in Vitally in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.

Common use cases

  • 01 Sync contacts and companies bi-directionally with the CRM so support sees deal context and sales sees conversation history
  • 02 Push product usage events from an application database into Intercom to trigger onboarding and retention messages
  • 03 Push billing and subscription changes from an ERP or billing system into Vitally to keep success playbooks accurate.
  • 04 Keep CS tasks and notes aligned between Vitally and ticketing or project tools.

Common sync patterns

Where both track pipeline: deal visibility across systems

Deal stage and value on shared accounts stay visible from either CRM.

Post-acquisition consolidation

Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.

Migration with a parallel run

When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.

What you can sync between Intercom and Vitally

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 Vitally objects How this pairing syncs
Conversations Support and sales threads sync outward for analytics and CRM context. Conversation Customer conversations logged in Vitally; activity objects include parent object details in the payload. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Contacts A single contact model covers both users and leads, distinguished by a role attribute. Note Account and user notes captured by success teams. Contacts is specific to Intercom and Note to Vitally — each maps to any object or custom field on the other side.
Companies Company records group contacts and carry plan and account attributes used in segmentation. NPS Response NPS survey responses for account-health reporting. Companies is specific to Intercom and NPS Response to Vitally — each maps to any object or custom field on the other side.
Tickets Structured ticket records track issues alongside conversational threads. Custom Trait Custom account and user traits for segmentation. Tickets is specific to Intercom and Custom Trait to Vitally — each maps to any object or custom field on the other side.
Data Events Behavioral events pushed in from product databases trigger messages and flows. Account Core customer account records with health scores and lifecycle traits; created, updated, retrieved, and listed via the REST API. Data Events is specific to Intercom and Account to Vitally — each maps to any object or custom field on the other side.
Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. User End users tied to accounts, including activity and custom traits. Custom Data Attributes is specific to Intercom and User to Vitally — each maps to any object or custom field on the other side.

How changes propagate between Intercom and Vitally

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

Vitally Intercom Sub-second propagation

DetectionVitally notifies Stacksync of record changes through webhook events. Incremental polling on updatedAt cursors.

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.
  • Vitally: Default rate limit of 1,000 requests/min (token bucket); write operations consume more budget, headers expose remaining quota.
What ships with Intercom ⇄ Vitally

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Intercom ⇄ Vitally 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 Vitally.

How the Intercom and Vitally 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

Vitally

Integration surface
REST API with cursor-based pagination (sortable by createdAt/updatedAt)
Authentication
API key via Basic Auth; keys created in Settings -> Integrations -> REST API and individually revocable
Change detection
Incremental polling on updatedAt cursors; playbook-triggered webhooks can push events for near real-time updates
Capabilities
read · write · webhooks
Rate limits
Default rate limit of 1,000 requests/min (token bucket); write operations consume more budget, headers expose remaining quota.
How it works

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

    Choose tables

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

Intercom and Vitally 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
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:

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 390 integrations available for Intercom and Vitally.

Popular · 8 of 390
All Intercom integrations All Vitally 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