Real-time
Two-way sync
Changes in Salesforce or Splunk instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Analytics
Salesforce to Splunk integration — real-time, two-way sync
Keep Salesforce 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 Salesforce and Splunk
Put live Salesforce data behind every dashboard and cohort in Splunk, and write the segments and scores Splunk computes back onto the Salesforce record — one connection, not a nightly export.
Splunk turns data into dashboards, cohorts, and metrics; Salesforce 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 Products and Price Books, Custom Objects, Accounts, Contacts from Salesforce 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 Salesforce, 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 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.
- 02 Export Users and Roles into an IAM database for periodic access reviews, or provision them from an identity source of truth.
- 03 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
- 04 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
Common sync patterns
Customer context in Splunk
Accounts, contacts, deals, and activity from Salesforce 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 Salesforce appear in Splunk within seconds, so dashboards and cohorts track the current pipeline rather than last night's export.
Where Salesforce accepts updates: segments and scores back on the record
Cohorts, scores, and computed metrics from Splunk sync onto fields in Salesforce, putting the analysis where reps and owners actually work the accounts.
What you can sync between Salesforce 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.
| Salesforce objects | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. | 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. | Custom Objects is specific to Salesforce and Search Results to Splunk — each maps to any object or custom field on the other side. | |
| Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | 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. | Accounts is specific to Salesforce and Saved Searches to Splunk — each maps to any object or custom field on the other side. | |
| Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | 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. | Contacts is specific to Salesforce and Fired Alerts to Splunk — each maps to any object or custom field on the other side. | |
| Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | 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. | Leads is specific to Salesforce and KV Store Collections to Splunk — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | 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. | Opportunities is specific to Salesforce and Indexes to Splunk — each maps to any object or custom field on the other side. | |
| Cases Support records; synced with help desk tools or internal databases for escalation workflows. | 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. | Cases is specific to Salesforce and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Salesforce 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.
Salesforce Splunk Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
DeliveryEach detected change is written to Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Salesforce 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 Salesforce through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Salesforce: Daily API request allocations vary by edition and license count.
- 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 Salesforce ⇄ Splunk
Connect Salesforce and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Salesforce–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Salesforce 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 Salesforce or Splunk record.
Observability
Monitoring
Track your Salesforce ⇄ Splunk sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Salesforce and Splunk.
How the Salesforce and Splunk connectors work
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
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 Salesforce 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 Salesforce 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.
Salesforce
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Salesforce 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 · Salesforce ⇄ 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.
Salesforce SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Salesforce and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Salesforce and Splunk: authenticate both systems, choose the objects to sync (such as Salesforce's Custom Objects and Accounts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Salesforce and Splunk: Customer context in Splunk; Report on live CRM data; Where Salesforce accepts updates: segments and scores back on the record. Accounts, contacts, deals, and activity from Salesforce sync into Splunk, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.
-
Salesforce: REST, SOAP, and Bulk APIs. Authentication: OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode. Splunk: 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). Stacksync manages authentication, retries, and rate limits on both sides.
-
Splunk: The KV Store is a MongoDB-backed, app-scoped collection store with full CRUD and batch endpoints (/servicesNS/{owner}/{app}/storage/collections/data/{collection}), so lookup records can be read and written in both directions. Salesforce: Records are queried with SOQL, and every standard and custom object carries a SystemModstamp field that sync engines use to order incremental changes. Stacksync's field mapping accounts for these differences between Salesforce 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 Salesforce and Splunk records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Salesforce and Splunk connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Salesforce–Splunk integration in-house.
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 509 integrations available for Salesforce and Splunk.
Popular · 7 of 509
-
Salesforce ⇄ Adobeanalytics -
Salesforce ⇄ Pendo -
Salesforce ⇄ Treasuredata -
Salesforce ⇄ Mixpanel -
Splunk ⇄ Gong -
Splunk ⇄ HubSpot -
Splunk ⇄ Microsoft Dynamics 365 Sales
No integrations match .
