Real-time
Two-way sync
Changes in Dynamics 365 Business Central or Splunk instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Analytics
Dynamics 365 Business Central to Splunk integration — real-time, two-way sync
Keep Dynamics 365 Business Central 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 Dynamics 365 Business Central and Splunk
Put Dynamics 365 Business Central's records into Splunk as live data for reporting and dashboards, without nightly exports, and send the segments and metrics Splunk computes back where Dynamics 365 Business Central can use them.
ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether Dynamics 365 Business Central carries financials, operations, workforce data, or all three, those numbers belong in Splunk, next to the product, behavioral, and web data the team already measures.
Stacksync syncs Sales Invoices, Purchase Orders, General Ledger Entries, Journals from Dynamics 365 Business Central into Splunk continuously, handling API limits and schema drift as it goes, so each record type arrives as Indexes, HTTP Event Collector, Users and Roles, Dashboards ready to report on. The connection is bi-directional, so segments, scores, and metrics computed in Splunk can be written back to fields in Dynamics 365 Business Central where that is useful.
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 Mirror items and inventory levels into external channels so stock data stays current outside the ERP.
- 04 Replicate GL entries and dimensions into a SQL database for financial reporting without giving analysts ERP logins.
Common sync patterns
Where Dynamics 365 Business Central runs operations: inventory and fulfillment metrics
Operational records from Dynamics 365 Business Central become measurable in Splunk, joinable with the rest of what the company tracks for supply and fulfillment reporting.
Where Dynamics 365 Business Central is the HR system of record: workforce and cost analysis
Worker and organization data from Dynamics 365 Business Central syncs into Splunk for headcount, cost, and utilization reporting alongside other company data.
Write-back where Dynamics 365 Business Central exposes writable fields: segments and scores return
Segments, scores, or metrics computed in Splunk sync onto the matching records in Dynamics 365 Business Central, so operations act on what the analysis found.
What you can sync between Dynamics 365 Business Central 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.
| Dynamics 365 Business Central objects | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Vendors Supplier master data synced with procurement and AP automation tools. | 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. | Vendors is specific to Dynamics 365 Business Central and Users and Roles to Splunk — each maps to any object or custom field on the other side. | |
| Items Product and inventory records aligned with e-commerce and warehouse systems. | 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. | Items is specific to Dynamics 365 Business Central and Dashboards to Splunk — each maps to any object or custom field on the other side. | |
| Sales Orders Order headers and lines created from external channels and read back for fulfillment status. | 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. | Sales Orders is specific to Dynamics 365 Business Central and Search Results to Splunk — each maps to any object or custom field on the other side. | |
| Sales Invoices Billing documents synced to CRMs and payment platforms. | 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. | Sales Invoices is specific to Dynamics 365 Business Central and Saved Searches to Splunk — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | 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. | Purchase Orders is specific to Dynamics 365 Business Central and Fired Alerts to Splunk — each maps to any object or custom field on the other side. | |
| General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | 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. | General Ledger Entries is specific to Dynamics 365 Business Central and KV Store Collections to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Dynamics 365 Business Central 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.
Dynamics 365 Business Central Splunk Sub-second propagation
DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.
DeliveryEach detected change is written to Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Dynamics 365 Business Central 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 Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- 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 Dynamics 365 Business Central ⇄ Splunk
Connect Dynamics 365 Business Central and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dynamics 365 Business Central 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 Dynamics 365 Business Central or Splunk record.
Observability
Monitoring
Track your Dynamics 365 Business Central ⇄ Splunk sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central and Splunk.
How the Dynamics 365 Business Central and Splunk connectors work
Dynamics 365 Business Central
- Integration surface
- REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
- Authentication
- OAuth 2.0 via Microsoft Entra ID
- Change detection
- API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
- Capabilities
- read · write · webhooks
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 Dynamics 365 Business Central 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 Dynamics 365 Business Central 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.
Dynamics 365 Business Central
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dynamics 365 Business Central 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 · Dynamics 365 Business Central ⇄ 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.
Dynamics 365 Business Central SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dynamics 365 Business Central and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Dynamics 365 Business Central and Splunk: authenticate both systems, choose the objects to sync (such as Dynamics 365 Business Central's Vendors and Items), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Dynamics 365 Business Central: REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL. Authentication: OAuth 2.0 via Microsoft Entra ID. 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: Indexed events are immutable and time-stamped, so incremental extraction advances an earliest/latest window over _time (or _indextime) rather than using a modified-date CDC feed. Dynamics 365 Business Central: Writes use ETags with If-Match headers for optimistic concurrency, so stale updates are rejected instead of silently overwriting ERP data. Stacksync's field mapping accounts for these differences between Dynamics 365 Business Central 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 Dynamics 365 Business Central and Splunk records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dynamics 365 Business Central and Splunk connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dynamics 365 Business Central–Splunk integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Dynamics 365 Business Central 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 481 integrations available for Dynamics 365 Business Central and Splunk.
Popular · 7 of 481
-
Dynamics 365 Business Central ⇄ Microsoft Power Bi -
Dynamics 365 Business Central ⇄ Tableau -
Dynamics 365 Business Central ⇄ Adobeanalytics -
Dynamics 365 Business Central ⇄ Pendo -
Splunk ⇄ Infor CloudSuite - Splunk ⇄ Infor LN
- Splunk ⇄ Infor M3
No integrations match .
