Two-way sync
Changes in Intercom or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Keep Intercom and SAP Hana in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in SAP Hana, where it can be queried and joined like everything else.
Stacksync mirrors Conversations, Tickets, Data Events, Custom Data Attributes from Intercom into Triggers, System-versioned temporal tables, System views (SYS schema), Column store tables in SAP Hana with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Intercom with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Field and stage updates in Intercom arrive as row changes in SAP Hana, ready to drive jobs and notifications.
Accounts, contacts, and custom objects from Intercom become tables in SAP Hana you can join with application data directly.
Signup, usage, or lifecycle changes written to SAP Hana sync onto the matching records in Intercom, giving go-to-market teams live product context.
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 | SAP Hana objects | How this pairing syncs | |
|---|---|---|---|
| Segments Saved audience definitions are readable for targeting parity across tools. | Row store tables OLTP-oriented tables held fully in memory; read and written the same way through the SAP HANA client for high-write operational tables. | Segments is specific to Intercom and Row store tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Admins & Teams Teammate records map conversation ownership to CRM users. | Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. | Admins & Teams is specific to Intercom and Calculation views to SAP Hana — 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. | SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. | Articles is specific to Intercom and SQL views to SAP Hana — 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. | Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Contacts is specific to Intercom and Schemas to SAP Hana — 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. | Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Companies is specific to Intercom and Sequences to SAP Hana — each maps to any object or custom field on the other side. | |
| Conversations Support and sales threads sync outward for analytics and CRM context. | Triggers AFTER INSERT/UPDATE/DELETE triggers capture changes into a shadow/logging table so updates and deletes are detected near-real-time without full scans. | Conversations is specific to Intercom and Triggers to SAP Hana — 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 applied to SAP Hana as a row-level write, with types converted between the two schemas.
DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.
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–SAP Hana connection.
Changes in Intercom or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Intercom or SAP Hana 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 SAP Hana record.
Track your Intercom ⇄ SAP Hana sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Intercom and SAP Hana.
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 SAP Hana 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 SAP Hana 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 SAP Hana: authenticate both systems, choose the objects to sync (such as Intercom's Segments and Admins & Teams), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Intercom side: Conversations, Tickets, Data Events, Custom Data Attributes, plus custom fields where Intercom exposes them. On the SAP Hana side: Triggers, System-versioned temporal tables, System views (SYS schema), Column store tables. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Intercom and SAP Hana: Trigger workflows from CRM changes; Query the CRM like a database; Product events onto CRM records. Field and stage updates in Intercom arrive as row changes in SAP Hana, ready to drive jobs and notifications.
Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. SAP Hana: SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access. Authentication: Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting. Stacksync manages authentication, retries, and rate limits on both sides.
Intercom: Conversations are composed of nested conversation parts (messages, notes, assignments), which matters when replicating full thread history. SAP Hana: System-versioned temporal tables are supported only on column store tables, not on the row store. Stacksync's field mapping accounts for these differences between Intercom and SAP Hana without custom code.
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 547 integrations available for Intercom and SAP Hana.