Real-time
Two-way sync
Changes in Kustomer or Splunk instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Analytics
Kustomer to Splunk integration — real-time, two-way sync
Keep Kustomer 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 Kustomer and Splunk
Put live Kustomer data behind every dashboard and cohort in Splunk, and write the segments and scores Splunk computes back onto the Kustomer record — one connection, not a nightly export.
Splunk turns data into dashboards, cohorts, and metrics; Kustomer 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 Custom Objects (Klasses), Users, Teams, Tags from Kustomer 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 Kustomer, 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 Sync fired-alert history and saved-search definitions into Postgres so security and reliability teams query alert trends and detection coverage in SQL.
- 02 Ingest application, CRM, or database records into Splunk via the HTTP Event Collector so operational data lands alongside logs for correlation and dashboards.
- 03 Sync customers bi-directionally with the CRM and ERP so agents see deal, billing, and subscription context on the timeline
- 04 Push order and shipment records from commerce systems into Kustomer custom objects so agents answer order-status questions without switching tools
Common sync patterns
Where Kustomer accepts updates: segments and scores back on the record
Cohorts, scores, and computed metrics from Splunk sync onto fields in Kustomer, putting the analysis where reps and owners actually work the accounts.
One customer across analytics and CRM
The same account or person is keyed consistently in both systems, so a profile or row in Splunk lines up with the contact or account in Kustomer.
A record that outlives edits in the CRM
A continuously synced copy of Kustomer's records and activity in Splunk keeps a queryable history even as records change or age out of the CRM.
What you can sync between Kustomer 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.
| Kustomer objects | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Companies Organization records group customers and map to CRM accounts. | 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. | Companies is specific to Kustomer and Indexes to Splunk — each maps to any object or custom field on the other side. | |
| Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. | 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. | Custom Objects (Klasses) is specific to Kustomer and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side. | |
| Users Agent records map conversation ownership to people in other systems. | 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. | Users is specific to Kustomer and Users and Roles to Splunk — each maps to any object or custom field on the other side. | |
| Teams Team assignments support routing parity and reporting. | 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. | Teams is specific to Kustomer and Dashboards to Splunk — each maps to any object or custom field on the other side. | |
| Tags Labels on conversations and customers sync for categorization and analytics. | Search Results SPL searches dispatched via POST /services/search/jobs return a search ID (SID); results are pulled from /services/search/jobs/{sid}/results once the job completes, or synchronously via oneshot/export mode. The primary read path for streaming indexed events out to a warehouse. | Tags is specific to Kustomer and Search Results to Splunk — each maps to any object or custom field on the other side. | |
| Notes Internal annotations carry context alongside synced conversations. | Saved Searches Scheduled searches, reports, and the definitions behind alerts at /services/saved/searches with full create, update, and delete. Read out for governance and coverage review, or provisioned and updated from a config source. | Notes is specific to Kustomer and Saved Searches to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Kustomer 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.
Kustomer Splunk Sub-second propagation
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
DeliveryEach detected change is written to Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Kustomer 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 Kustomer through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Kustomer: Subject to the platform's API rate limits.
- 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 Kustomer ⇄ Splunk
Connect Kustomer and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kustomer–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Kustomer 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 Kustomer or Splunk record.
Observability
Monitoring
Track your Kustomer ⇄ Splunk sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Kustomer and Splunk.
How the Kustomer and Splunk connectors work
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
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 Kustomer 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 Kustomer 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.
Kustomer
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Kustomer 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 · Kustomer ⇄ 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.
Kustomer SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Kustomer and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Kustomer and Splunk: authenticate both systems, choose the objects to sync (such as Kustomer's Companies and Custom Objects (Klasses)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Splunk: Splunk exposes two API surfaces: the management REST API (default port 8089) for search jobs, saved searches, KV Store, indexes, users, and roles, and the HTTP Event Collector (default port 8088, port 443 on Splunk Cloud) for pushing events and metrics in — so the connector both reads from and writes into Splunk. Kustomer: Kustomer's data model centers on a customer timeline: conversations, messages, and custom object records all appear chronologically against one customer record rather than as separate tickets. Stacksync's field mapping accounts for these differences between Kustomer and Splunk 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 Kustomer and Splunk records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Kustomer and Splunk connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Kustomer–Splunk integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Kustomer and Splunk. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Kustomer: Outbound webhooks on record 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.
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 390 integrations available for Kustomer and Splunk.
Popular · 7 of 390
-
Kustomer ⇄ Pendo -
Kustomer ⇄ Mixpanel -
Kustomer ⇄ Microsoft Power Bi -
Splunk ⇄ Salesforce -
Splunk ⇄ HubSpot -
Splunk ⇄ Microsoft Dynamics 365 Sales -
Splunk ⇄ Attio
No integrations match .
