Real-time
Two-way sync
Changes in Freshworks CRM or Splunk instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Analytics
Freshworks CRM to Splunk integration — real-time, two-way sync
Keep Freshworks CRM 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 Freshworks CRM and Splunk
Put live Freshworks CRM data behind every dashboard and cohort in Splunk, and write the segments and scores Splunk computes back onto the Freshworks CRM record — one connection, not a nightly export.
Splunk turns data into dashboards, cohorts, and metrics; Freshworks CRM 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 Sales activities, Lists, Notes, Contacts from Freshworks CRM 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 Freshworks CRM, 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 unified contact records, covering sales and marketing attributes, into a warehouse for full-funnel reporting.
- 04 Push scored leads from a data platform into Freshworks CRM and route them by lifecycle stage.
Common sync patterns
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 Freshworks CRM.
A record that outlives edits in the CRM
A continuously synced copy of Freshworks CRM'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 Freshworks CRM sync into Splunk, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.
What you can sync between Freshworks CRM 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.
| Freshworks CRM objects | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Sales activities Logged activity types used in engagement and productivity analysis. | 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. | Sales activities is specific to Freshworks CRM and Fired Alerts to Splunk — each maps to any object or custom field on the other side. | |
| Lists Contact list membership synced against segments computed in a warehouse. | 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. | Lists is specific to Freshworks CRM and KV Store Collections to Splunk — each maps to any object or custom field on the other side. | |
| Notes Context records attached to contacts, accounts, and deals. | 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. | Notes is specific to Freshworks CRM and Indexes to Splunk — each maps to any object or custom field on the other side. | |
| Contacts Unified sales-and-marketing person records; the core entity for bidirectional syncs. | 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. | Contacts is specific to Freshworks CRM and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side. | |
| Accounts Company records kept consistent with ERP and billing 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. | Accounts is specific to Freshworks CRM and Users and Roles to Splunk — each maps to any object or custom field on the other side. | |
| Deals Pipeline records synced out for forecasting and full-funnel 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. | Deals is specific to Freshworks CRM and Dashboards to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Freshworks CRM 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.
Freshworks CRM Splunk Sub-second propagation
DetectionFreshworks CRM notifies Stacksync of record changes through webhook events. Polling with updated-at filters.
DeliveryEach detected change is written to Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Freshworks CRM 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 Freshworks CRM through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Freshworks CRM: Subject to per-account API rate limits that vary by plan.
- 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 Freshworks CRM ⇄ Splunk
Connect Freshworks CRM and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Freshworks CRM–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Freshworks CRM 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 Freshworks CRM or Splunk record.
Observability
Monitoring
Track your Freshworks CRM ⇄ Splunk sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Freshworks CRM and Splunk.
How the Freshworks CRM and Splunk connectors work
Freshworks CRM
- Integration surface
- REST API
- Authentication
- API key sent as a Token authorization header
- Change detection
- Polling with updated-at filters; outbound webhooks can be configured through workflow automations
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that vary by plan
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 Freshworks CRM 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 Freshworks CRM 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.
Freshworks CRM
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Freshworks CRM 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 · Freshworks CRM ⇄ 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.
Freshworks CRM SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Freshworks CRM and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Freshworks CRM and Splunk: authenticate both systems, choose the objects to sync (such as Freshworks CRM's Sales activities and Lists), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Freshworks CRM: REST API. Authentication: API key sent as a Token authorization header. 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: Searches are asynchronous: POST /services/search/jobs returns a search ID (SID), and results are fetched from /services/search/jobs/{sid}/results once the job completes; oneshot and export modes return results synchronously. Freshworks CRM: Freshworks CRM was rebranded as Freshsales Suite; it shares the Freshsales API surface, with marketing features layered onto the same contact model. Stacksync's field mapping accounts for these differences between Freshworks CRM 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 Freshworks CRM and Splunk records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Freshworks CRM and Splunk connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Freshworks CRM–Splunk integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Freshworks CRM and Splunk. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 494 integrations available for Freshworks CRM and Splunk.
Popular · 8 of 494
-
Freshworks CRM ⇄ Treasuredata -
Freshworks CRM ⇄ Mixpanel -
Freshworks CRM ⇄ Microsoft Power Bi -
Freshworks CRM ⇄ Tableau -
Splunk ⇄ ZoomInfo -
Splunk ⇄ Vitally -
Splunk ⇄ DealCloud -
Splunk ⇄ Chorusai
No integrations match .
