Real-time
Two-way sync
Changes in Intercom or Splunk instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Analytics
Intercom to Splunk integration — real-time, two-way sync
Keep Intercom and Splunk 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 Splunk
Put live Intercom data behind every dashboard and cohort in Splunk, and write the segments and scores Splunk computes back onto the Intercom record — one connection, not a nightly export.
Splunk 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 Admins & Teams, Articles, Contacts, Companies from Intercom into Splunk 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 Splunk 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.
Common use cases
- 01 Read and write KV Store collections to keep Splunk lookups — asset inventories, allow/deny lists, enrichment tables — in sync with an external source of truth in both directions.
- 02 Provision and update Saved Searches, alerts, and Dashboards from a Git-backed config repository so detections and reports stay versioned and consistent across search heads.
- 03 Push product usage events from an application database into Intercom to trigger onboarding and retention messages
- 04 Mirror conversations and tickets into a warehouse for support analytics and SLA reporting
Common sync patterns
A record that outlives edits in the CRM
A continuously synced copy of Intercom's records and activity in Splunk keeps a queryable history even as records change or age out of the CRM.
Customer context in Splunk
Accounts, contacts, deals, and activity from Intercom sync into Splunk, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.
Report on live CRM data
New records and status changes in Intercom appear in Splunk within seconds, so dashboards and cohorts track the current pipeline rather than last night's export.
What you can sync between Intercom and Splunk
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 | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Data Events Behavioral events pushed in from product databases trigger messages and flows. | Fired Alerts Triggered alert instances listed at /services/alerts/fired_alerts; alert configuration (conditions, schedule, actions) lives on the corresponding saved search. Landed in a database for alert-trend and detection-coverage reporting. | Data Events is specific to Intercom and Fired Alerts to Splunk — 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. | KV Store Collections App-scoped, MongoDB-backed key-value collections at /servicesNS/{owner}/{app}/storage/collections/data/{collection} with full CRUD and batch endpoints. Genuinely bidirectional lookup/state store — read records out or write records in. | Custom Data Attributes is specific to Intercom and KV Store Collections to Splunk — 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. | Indexes Index inventory and settings (retention, max size, event counts) via /services/data/indexes, with create and edit; loaded into a database for capacity, retention, and data-onboarding tracking. | Tags is specific to Intercom and Indexes to Splunk — each maps to any object or custom field on the other side. | |
| Segments Saved audience definitions are readable for targeting parity across tools. | HTTP Event Collector The write-in path: POST events and metrics to /services/collector (port 8088, or 443 on Splunk Cloud) authenticated with a per-input HEC token, so external records are indexed alongside logs for search and correlation. | Segments is specific to Intercom and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side. | |
| Admins & Teams Teammate records map conversation ownership to CRM users. | Users and Roles Accounts at /services/authentication/users and role/capability definitions at /services/authorization/roles, with full CRUD; exported for access reviews or provisioned from an identity source of truth. | Admins & Teams is specific to Intercom and Users and Roles to Splunk — 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. | Dashboards Simple XML dashboard and view definitions at /servicesNS/{owner}/{app}/data/ui/views; exported for backup and audit, or created and updated programmatically from version control. | Articles is specific to Intercom and Dashboards to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Intercom and Splunk
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 Splunk 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 Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Intercom Sub-second propagation
DetectionSplunk notifies Stacksync of record changes through webhook events. Time-range searches over indexed events (earliest/latest on _time or _indextime).
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.
- Splunk: The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
What ships with Intercom ⇄ Splunk
Connect Intercom and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Intercom or Splunk 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 Splunk record.
Observability
Monitoring
Track your Intercom ⇄ Splunk 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 Splunk.
How the Intercom and Splunk 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
Splunk
- Integration surface
- REST API (management API + HTTP Event Collector)
- Authentication
- HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud).
- Change detection
- Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action.
- Capabilities
- read · write · webhooks
- Rate limits
- The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
How it works
How to connect Intercom to Splunk — 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.
- 01
Connect your apps
Authenticate Intercom and Splunk with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Intercom
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Intercom and Splunk 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.
objects · Intercom ⇄ SplunkCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Intercom SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Intercom and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Intercom and Splunk: authenticate both systems, choose the objects to sync (such as Intercom's Data Events and Custom Data Attributes), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Splunk records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Intercom and Splunk connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Intercom–Splunk integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Intercom and Splunk. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Intercom: Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill. On Splunk: Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Splunk side: Search Results, Saved Searches, Fired Alerts, KV Store Collections, plus custom fields where Splunk exposes them. On the Intercom side: Admins & Teams, Articles, Contacts, Companies. Stacksync auto-detects both schemas and converts types between the two systems.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 485 integrations available for Intercom and Splunk.
Popular · 7 of 485
-
Intercom ⇄ Treasuredata -
Intercom ⇄ Mixpanel -
Intercom ⇄ Microsoft Power Bi -
Intercom ⇄ Tableau -
Splunk ⇄ Close -
Splunk ⇄ Copper CRM -
Splunk ⇄ Creatio CRM
No integrations match .
