Two-way sync
Changes in Intercom or Pendo instantly reflect in both systems. No stale data, no manual imports.
Keep Intercom and Pendo in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Pendo turns data into dashboards, cohorts, and metrics; Intercom is where customers, contacts, deals, and activity actually live and change. The two meet wherever a number is really about a specific account, segment, or stage — yet most teams feed the CRM into analytics as a nightly extract or a hand-maintained connector, so the reporting lags the business and can't be sliced by the customers and segments that matter.
Stacksync syncs Companies, Conversations, Tickets, Data Events from Intercom into Pendo field by field and within seconds, so every dashboard and cohort runs on current records instead of a stale copy. Because the connection runs both ways, the cohorts, scores, and metrics computed in Pendo write back to fields in Intercom, landing where the people working accounts can see them. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Accounts, contacts, deals, and activity from Intercom sync into Pendo, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.
New records and status changes in Intercom appear in Pendo within seconds, so dashboards and cohorts track the current pipeline rather than last night's export.
Cohorts, scores, and computed metrics from Pendo sync onto fields in Intercom, putting the analysis where reps and owners actually work the accounts.
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 | Pendo objects | How this pairing syncs | |
|---|---|---|---|
| Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Accounts Company/workspace records that roll visitors up to an account dimension; readable via Aggregation and a write target for custom fields (plan, ARR, health) via the Metadata API. | Custom Data Attributes is specific to Intercom and Accounts to Pendo — 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. | Feature Events Click/interaction events on tagged features, read-only through the Aggregation API over an event-time window and joined to the Feature definitions. | Tags is specific to Intercom and Feature Events to Pendo — each maps to any object or custom field on the other side. | |
| Segments Saved audience definitions are readable for targeting parity across tools. | Page Events Page-view events for tagged pages; read-only via the Aggregation API, used for adoption and path analysis in a warehouse. | Segments is specific to Intercom and Page Events to Pendo — each maps to any object or custom field on the other side. | |
| Admins & Teams Teammate records map conversation ownership to CRM users. | Guide Events Guide seen/advanced/dismissed and step events for in-app walkthroughs; read-only through the Aggregation API to measure onboarding flow adoption. | Admins & Teams is specific to Intercom and Guide Events to Pendo — 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. | Poll / NPS Responses Survey answers and NPS scores captured in-app (pollEvents / npsEvents); read-only via the Aggregation API as voice-of-customer data. | Articles is specific to Intercom and Poll / NPS Responses to Pendo — 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. | Features / Pages / Guides (metadata) Definitions of tagged UI elements listed through the entity endpoints; read-only reference used to label and join the event streams. | Contacts is specific to Intercom and Features / Pages / Guides (metadata) to Pendo — each maps to any object or custom field on the other side. |
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.
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 Pendo through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Pendo for changes on an incremental schedule, reading only records changed since the previous pass. Polling - reads query the Aggregation API over event-time windows.
DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Pendo connection.
Changes in Intercom or Pendo instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Intercom or Pendo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Intercom or Pendo record.
Track your Intercom ⇄ Pendo sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Intercom and Pendo.
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.
Authenticate Intercom and Pendo with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Intercom and Pendo 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Intercom and Pendo: authenticate both systems, choose the objects to sync (such as Intercom's Custom Data Attributes and Tags), map fields visually, and changes propagate both ways in milliseconds — no code required.
Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Pendo: Pendo Engage API (REST) on app.pendo.io (US) / app.eu.pendo.io (EU), base path /api/v1/ - Aggregation API for reads and the Metadata API for writes. Authentication: Integration key sent in the x-pendo-integration-key header, generated in Subscription Settings; keys are scoped read-only or read/write, so writes require a read/write key. Stacksync manages authentication, retries, and rate limits on both sides.
Pendo: Reads run through the Aggregation API (POST /api/v1/aggregation), a pipeline of a source plus transforms over feature/page/guide events, poll and NPS responses, visitors, and accounts; there is no CDC feed. Intercom: Intercom's Contacts API unifies users and leads into one object with a role attribute, replacing the older separate users and leads endpoints. Stacksync's field mapping accounts for these differences between Intercom and Pendo without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Intercom and Pendo records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Intercom and Pendo connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Intercom–Pendo integration in-house.
Yes — Stacksync ships production-grade connectors for both Intercom and Pendo. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 485 integrations available for Intercom and Pendo.