Real-time
Two-way sync
Changes in Rollworks or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Marketing ⇄ Database
Rollworks to SAP Hana integration — real-time, two-way sync
Keep Rollworks and SAP Hana 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 Rollworks and SAP Hana
Give your team Rollworks's contacts, campaigns, and engagement in SAP Hana: query them with SQL, push audiences built from your own data back to Rollworks, and skip the marketing API.
Rollworks holds the people, audiences, and campaign activity that marketing runs on, but that data sits behind interfaces built for marketers, not for your internal systems. Engineers and analysts who need contacts, list membership, or engagement, for reporting, attribution, or product logic, end up writing integration code against a rate-limited API and maintaining it forever. Meanwhile the customer and usage data marketers want for targeting already lives in SAP Hana, hard to get into campaigns without manual exports.
Stacksync mirrors Campaigns, Ad Groups and Ads, Reporting and Attribution, Target Account Lists from Rollworks into Triggers, System-versioned temporal tables, System views (SYS schema), Column store tables in SAP Hana field by field, in real time, and in both directions. Marketing records become rows your code can query and join with product and customer data; audiences and attributes computed in SAP Hana, from usage, orders, or account status, sync back into Rollworks to drive campaigns and ads, with Rollworks kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.
Common use cases
- 01 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.
- 02 Detect inserts, updates, and deletes on high-write tables via AFTER triggers or a last-modified column and replicate the deltas downstream near-real-time.
- 03 Create and edit Prospecting v2 Campaigns and Ad Groups programmatically so budgets and targeting stay in step with an internal planning system.
- 04 Consolidate account-level ad engagement by domain into a reporting database to join RollWorks spend against CRM Opportunities.
Common sync patterns
Query Rollworks like a database
Contacts, leads, audiences, and campaign metrics from Rollworks live in SAP Hana as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.
Build audiences from your own data
Segments computed in SAP Hana from product usage, orders, or account status sync into Rollworks as lists or audiences, so campaigns and ads target the people your data says they should.
Engagement and results next to the customer
Opens, clicks, sends, RSVPs, or ad activity from Rollworks land in SAP Hana beside the matching customer record, ready for reporting and revenue attribution.
What you can sync between Rollworks and SAP Hana
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.
| Rollworks objects | SAP Hana objects | How this pairing syncs | |
|---|---|---|---|
| Reporting and Attribution Delivery and attribution metrics (impressions, clicks, cost, conversions, view-throughs) from the GraphQL Reporting API; read-only, aggregated by campaign, ad, and account domain. | Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Reporting and Attribution is specific to Rollworks and Sequences to SAP Hana — each maps to any object or custom field on the other side. | |
| Target Account Lists Named lists of B2B accounts for ABM; managed through /audience/v1/target_accounts so a CRM or warehouse can push and reconcile the accounts RollWorks advertises against. | Triggers AFTER INSERT/UPDATE/DELETE triggers capture changes into a shadow/logging table so updates and deletes are detected near-real-time without full scans. | Target Account Lists is specific to Rollworks and Triggers to SAP Hana — each maps to any object or custom field on the other side. | |
| Account Tiers Groups within a Target Account List; an account belongs to only one tier per list, so tier assignments are written from source-of-truth data to drive tiered targeting. | System-versioned temporal tables Column store tables with a history table tracking each row's validity period; used to reconstruct update and delete history for change capture. | Account Tiers is specific to Rollworks and System-versioned temporal tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Accounts (TAL Items) Individual accounts identified by domain; added or removed via the tier items endpoint (POST/DELETE) so an operational database can control which domains are targeted. | System views (SYS schema) Catalog and monitoring views such as SYS.TABLES and TABLE_COLUMNS; read to discover schema and auto-generate field mappings for new tables. | Accounts (TAL Items) is specific to Rollworks and System views (SYS schema) to SAP Hana — each maps to any object or custom field on the other side. | |
| Audience Segments CRM (email), custom (cookie or ID), and lookalike segments created via /audience/v1/segments; membership is written from a warehouse with a duration of 1 to 540 days. | Column store tables HANA's default table type, optimized for analytics; synced two-way as rows over the SQL interface with the primary key driving upserts and delete tracking. | Audience Segments is specific to Rollworks and Column store tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Campaigns Prospecting v2 campaigns running on Web and LinkedIn with budget, KPI, and flight settings; created and edited via API and read back for status and pacing. | Row store tables OLTP-oriented tables held fully in memory; read and written the same way through the SAP HANA client for high-write operational tables. | Campaigns is specific to Rollworks and Row store tables to SAP Hana — each maps to any object or custom field on the other side. |
How changes propagate between Rollworks and SAP Hana
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.
Rollworks SAP Hana Interval-based propagation
DetectionStacksync polls Rollworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule.
DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.
SAP Hana Rollworks Sub-second propagation
DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.
DeliveryEach detected change is written to Rollworks through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Rollworks: NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
- SAP Hana: No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
What ships with Rollworks ⇄ SAP Hana
Connect Rollworks and SAP Hana for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rollworks–SAP Hana connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Rollworks or SAP Hana 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 Rollworks or SAP Hana record.
Observability
Monitoring
Track your Rollworks ⇄ SAP Hana sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Rollworks and SAP Hana.
How the Rollworks and SAP Hana connectors work
Rollworks
- Integration surface
- REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API
- Authentication
- OAuth 2.0 via NextRoll (Authorization Code grant, Bearer tokens per RFC 6749/6750); Personal Access Tokens supported for server-side scripts
- Change detection
- Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule; no change webhooks or CDC feed is published
- Capabilities
- read · write
- Rate limits
- NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
SAP Hana
- Integration surface
- SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access
- Authentication
- Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting.
- Change detection
- Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks.
- Capabilities
- read · write · CDC
- Rate limits
- No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
How it works
How to connect Rollworks to SAP Hana — 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 Rollworks and SAP Hana with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Rollworks
connected
SAP Hana
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Rollworks and SAP Hana 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 · Rollworks ⇄ SAP HanaCustomers 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.
Rollworks SAP HanaCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Rollworks and SAP Hana integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Rollworks and SAP Hana: authenticate both systems, choose the objects to sync (such as Rollworks's Reporting and Attribution and Target Account Lists), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Rollworks and SAP Hana records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Rollworks and SAP Hana connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Rollworks–SAP Hana integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Rollworks and SAP Hana. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Rollworks: Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule; no change webhooks or CDC feed is published. On SAP Hana: Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the SAP Hana side: Triggers, System-versioned temporal tables, System views (SYS schema), Column store tables, plus custom fields where SAP Hana exposes them. On the Rollworks side: Campaigns, Ad Groups and Ads, Reporting and Attribution, Target Account Lists. Stacksync auto-detects both schemas and converts types between the two systems.
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 404 integrations available for Rollworks and SAP Hana.
Popular · 5 of 404
No integrations match .
