Real-time
Two-way sync
Changes in Rillet or Splunk instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Analytics
Rillet to Splunk integration — real-time, two-way sync
Keep Rillet 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 Rillet and Splunk
Feed the customers, invoices, and revenue records in Rillet into Splunk in real time, so dashboards and reports run on current numbers instead of last night's export.
Rillet holds the financial truth: who the customers are, what they were invoiced, what they paid, and what revenue landed. Splunk is where that data is turned into dashboards, reports, and metrics, but it only reflects the world as of its last load. When the connection between them is a scheduled extract or a hand-built pipeline, analysis runs a step behind the books, and the numbers on a chart rarely match the numbers in the finance system.
Stacksync keeps Reimbursement, Custom Field, Account, Customer in Rillet in sync with Dashboards, Search Results, Saved Searches, Fired Alerts in Splunk, field by field and in real time. A customer, invoice, or amount created or corrected in Rillet shows up in Splunk within seconds, mapped to the right record. Where Splunk keeps its own accounts or users, the flow runs both ways, so finance attributes can enrich what Splunk already tracks.
There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning's reporting running on yesterday's figures.
Common use cases
- 01 Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
- 02 Push billing events from a product or usage-metering system into Rillet for revenue recognition.
- 03 Export Users and Roles into an IAM database for periodic access reviews, or provision them from an identity source of truth.
- 04 Sync fired-alert history and saved-search definitions into Postgres so security and reliability teams query alert trends and detection coverage in SQL.
Common sync patterns
Reports refresh as the books change
Instead of waiting for a scheduled load, Splunk updates the moment a figure moves in Rillet, so a dashboard opened at any point in the day is current.
Where Splunk keeps account or user records: finance attributes enrich them
Status, plan, or outstanding balance from Rillet attaches to the matching account or user in Splunk, so segments and cohorts can be cut by real financial standing.
Financial records land in Splunk for reporting
Invoices, payments, and revenue from Rillet flow into Splunk as they change, so dashboards are built on live figures rather than a periodic extract.
What you can sync between Rillet 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.
| Rillet objects | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Invoice Payment Synced with incremental and full sync per the Stacksync docs. | 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. | Invoice Payment is specific to Rillet and Fired Alerts to Splunk — each maps to any object or custom field on the other side. | |
| Charge Synced with incremental and full sync per the Stacksync docs. | 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. | Charge is specific to Rillet and KV Store Collections to Splunk — each maps to any object or custom field on the other side. | |
| Reimbursement Synced with incremental and full sync per the Stacksync docs. | 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. | Reimbursement is specific to Rillet and Indexes to Splunk — each maps to any object or custom field on the other side. | |
| Custom Field Synced with incremental and full sync per the Stacksync docs. | 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 Field is specific to Rillet and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side. | |
| Account Synced with incremental and full sync per the Stacksync docs. | 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. | Account is specific to Rillet and Users and Roles to Splunk — each maps to any object or custom field on the other side. | |
| Customer Synced with incremental and full sync per the Stacksync docs. | 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. | Customer is specific to Rillet and Dashboards to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Rillet 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.
Rillet Splunk Sub-second propagation
DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.
DeliveryEach detected change is written to Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Rillet 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 Rillet through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Rillet: 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 Rillet ⇄ Splunk
Connect Rillet and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rillet–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Rillet 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 Rillet or Splunk record.
Observability
Monitoring
Track your Rillet ⇄ Splunk sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Rillet and Splunk.
How the Rillet and Splunk connectors work
Rillet
- Integration surface
- REST API (OpenAPI-specified, with production and sandbox environments)
- Authentication
- API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
- Change detection
- Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
- Capabilities
- read · write · CDC · 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 Rillet 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 Rillet 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.
Rillet
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Rillet 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 · Rillet ⇄ 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.
Rillet SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Rillet and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Rillet and Splunk: authenticate both systems, choose the objects to sync (such as Rillet's Invoice Payment and Charge), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Rillet and Splunk. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Rillet: Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h). 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 Rillet side: Reimbursement, Custom Field, Account, Customer, plus custom fields where Rillet exposes them. On the Splunk side: Dashboards, Search Results, Saved Searches, Fired Alerts. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Rillet and Splunk: Reports refresh as the books change; Where Splunk keeps account or user records: finance attributes enrich them; Financial records land in Splunk for reporting. Instead of waiting for a scheduled load, Splunk updates the moment a figure moves in Rillet, so a dashboard opened at any point in the day is current.
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 399 integrations available for Rillet and Splunk.
Popular · 5 of 399
No integrations match .
