Real-time
Two-way sync
Changes in Agiloft or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Database
Agiloft to SAP Hana integration — real-time, two-way sync
Keep Agiloft 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 Agiloft and SAP Hana
Mirror Agiloft's data into SAP Hana so your own code can read and write it like any other table, with changes flowing both ways in seconds.
Engineers integrate with tools like Agiloft through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in SAP Hana.
Stacksync mirrors Companies, People, Attachments, Approvals from Agiloft into Sequences, Triggers, System-versioned temporal tables, System views (SYS schema) in SAP Hana and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Agiloft, so the tool and the database never disagree.
Common use cases
- 01 Two-way sync Contracts between Agiloft and an ERP or warehouse so value, renewal dates, and status stay current without manual re-keying.
- 02 Push generated documents and executed PDFs into Agiloft Attachments from a document system, or pull signed contracts out for archival.
- 03 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.
- 04 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.
Common sync patterns
React to changes as they happen
Updates in Agiloft arrive as row changes in SAP Hana, so triggers, jobs, and services can respond in near real time.
One integration pattern for the whole stack
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Read Agiloft with a query
Records from Agiloft are ordinary rows in SAP Hana; join them, index them, and use them in application logic without touching the vendor API.
What you can sync between Agiloft 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.
| Agiloft objects | SAP Hana objects | How this pairing syncs | |
|---|---|---|---|
| Companies Records for every organization - counterparties, vendors, customers - linked to contracts and people; read and written to keep account master data aligned with a CRM or ERP. | 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. | Companies is specific to Agiloft and System views (SYS schema) to SAP Hana — each maps to any object or custom field on the other side. | |
| People Parent table for individuals, split into Employees (internal users) and Contacts (external company contacts); synced to map signers, approvers, and account owners to CRM or HR records. | 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. | People is specific to Agiloft and Column store tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Attachments File records holding the executed contract PDFs and supporting documents linked to a contract; read to pull signed files out, or written to push generated documents in. | 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. | Attachments is specific to Agiloft and Row store tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Approvals Per-record approval instances generated from Approval Templates and Workflows; read to report approval status and cycle time, or written to trigger and record decisions. | Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. | Approvals is specific to Agiloft and Calculation views to SAP Hana — each maps to any object or custom field on the other side. | |
| Tasks Assigned action items with owners, due dates, and states tied to contracts or projects; synced two-way to surface Agiloft work inside a PM or operations system. | SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. | Tasks is specific to Agiloft and SQL views to SAP Hana — each maps to any object or custom field on the other side. | |
| Clause Library Reusable, approved contract clauses with metadata and categories; read to feed clause content into other systems or reporting, or maintained from an external source of truth. | Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Clause Library is specific to Agiloft and Schemas to SAP Hana — each maps to any object or custom field on the other side. |
How changes propagate between Agiloft 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.
Agiloft SAP Hana Sub-second propagation
DetectionAgiloft notifies Stacksync of record changes through webhook events. Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL.
DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.
SAP Hana Agiloft 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 Agiloft through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Agiloft: Agiloft publishes no fixed per-minute REST quota; throughput is instance-specific and bounded by license seats (Assigned/Floating Power User) and concurrent API sessions. Each SOAP/EWS call runs in its own transaction, and REST logins issue a session token meant to be reused rather than re-authenticated per call.
- 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 Agiloft ⇄ SAP Hana
Connect Agiloft and SAP Hana for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Agiloft–SAP Hana connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Agiloft 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 Agiloft or SAP Hana record.
Observability
Monitoring
Track your Agiloft ⇄ 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 Agiloft and SAP Hana.
How the Agiloft and SAP Hana connectors work
Agiloft
- Integration surface
- REST API (/ewws/rest/{kb}) and SOAP/EWS v2 web services (EWWSv2Service WSDL), plus a native Webhooks subscription API
- Authentication
- OAuth 2.0 via OAuth2 Client Setup - Authorization Code with PKCE for user-delegated apps and Client Credentials for machine-to-machine; also JWT tokens or Basic Auth with a session token from POST /ewws/rest/{kb}/login
- Change detection
- Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL; otherwise poll each table by its Date Updated / modified-time fields. Agiloft has no database change-data-capture log.
- Capabilities
- read · write · webhooks
- Rate limits
- Agiloft publishes no fixed per-minute REST quota; throughput is instance-specific and bounded by license seats (Assigned/Floating Power User) and concurrent API sessions. Each SOAP/EWS call runs in its own transaction, and REST logins issue a session token meant to be reused rather than re-authenticated per call.
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 Agiloft 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 Agiloft 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.
Agiloft
connected
SAP Hana
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Agiloft 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 · Agiloft ⇄ 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.
Agiloft SAP HanaCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Agiloft and SAP Hana integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Agiloft and SAP Hana: authenticate both systems, choose the objects to sync (such as Agiloft's Companies and People), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Agiloft and SAP Hana. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Agiloft: Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL; otherwise poll each table by its Date Updated / modified-time fields. Agiloft has no database change-data-capture log. 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 Agiloft side: Companies, People, Attachments, Approvals, plus custom fields where Agiloft exposes them. On the SAP Hana side: Sequences, Triggers, System-versioned temporal tables, System views (SYS schema). 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 Agiloft and SAP Hana: React to changes as they happen; One integration pattern for the whole stack; Read Agiloft with a query. Updates in Agiloft arrive as row changes in SAP Hana, so triggers, jobs, and services can respond in near real time.
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
CSA STAR
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 441 integrations available for Agiloft and SAP Hana.
Popular · 4 of 441
No integrations match .
