Skip to content
Database ⇄ Accounting and finance

InterSystems IRIS to Ramp integration — real-time, two-way sync

Keep InterSystems IRIS and Ramp 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 InterSystems IRIS and Ramp

Work with Ramp's financial data straight from InterSystems IRIS: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Cards, Users, Departments, Reimbursements from Ramp into Namespaces, Stored Procedures, Tables, Views in InterSystems IRIS and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against InterSystems IRIS, and rows your code writes or updates flow back into Ramp with validation, so the finance system stays the system of record.

Common use cases

  • 01 Read Reimbursements into a finance database for cross-entity expense reporting and reconciliation without manual CSV exports.
  • 02 Two-way sync Transactions and their accounting codings with a Postgres warehouse so finance analyzes spend in SQL and pushes GL categories and memos back to Ramp.
  • 03 Replicate IRIS tables to Postgres so application teams can build against a familiar database
  • 04 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access

Common sync patterns

Query finance data like any other data

Customers, invoices, and payments from Ramp live in InterSystems IRIS as regular tables or collections your team can join, index, and query.

Internal tools without API plumbing

Build dashboards and back-office tools directly on InterSystems IRIS; Stacksync handles the API calls, rate limits, and retries against Ramp.

Write back safely

Updates written to the synced tables in InterSystems IRIS propagate into Ramp, so automations can create or correct finance records without custom integration code.

What you can sync between InterSystems IRIS and Ramp

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.

InterSystems IRIS objects Ramp objects How this pairing syncs
Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Cards Physical and virtual card records; created and managed through the API to provision or suspend cardholder spend. Persistent Classes is specific to InterSystems IRIS and Cards to Ramp — each maps to any object or custom field on the other side.
Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. Users Employee and cardholder records; invited, updated, and deactivated, commonly synced from an HRIS or identity provider. Globals is specific to InterSystems IRIS and Users to Ramp — each maps to any object or custom field on the other side.
Namespaces Namespaces partition databases and determine the connection context for integrations. Departments Org groupings for cost-center and GL allocation; pushed from an ERP/HRIS and referenced by cards and transactions. Namespaces is specific to InterSystems IRIS and Departments to Ramp — each maps to any object or custom field on the other side.
Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. Reimbursements Out-of-pocket expense claims; read for reporting and marked ready-to-sync then synced to the ERP. Stored Procedures is specific to InterSystems IRIS and Reimbursements to Ramp — each maps to any object or custom field on the other side.
Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Bills Accounts-payable bills; created, updated, approved, and paid, then posted ready-to-sync and synced to accounting. Tables is specific to InterSystems IRIS and Bills to Ramp — each maps to any object or custom field on the other side.
Views SQL views expose curated slices of data for outbound replication. Vendors Supplier records under the accounting namespace; uploaded and updated for AP matching and payments. Views is specific to InterSystems IRIS and Vendors to Ramp — each maps to any object or custom field on the other side.

How changes propagate between InterSystems IRIS and Ramp

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.

InterSystems IRIS Ramp Interval-based propagation

DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).

DeliveryEach detected change is written to Ramp through its API, with automatic retries and rate-limit backoff.

Ramp InterSystems IRIS Sub-second propagation

DetectionRamp notifies Stacksync of record changes through webhook events. Signed webhooks (HMAC-SHA256 X-Ramp-Signature) for bill, transaction, reimbursement, vendor, and user events.

DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • InterSystems IRIS: Constrained by database resources rather than published API rate limits.
  • Ramp: 200 requests per 10-second rolling window per source IP; exceeding it returns 429 Too Many Requests, and requests running over 60 seconds return 504. Results use keyset pagination (follow the page.next URL / start cursor); higher limits can be requested from support.
What ships with InterSystems IRIS ⇄ Ramp

Connect InterSystems IRIS and Ramp for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Ramp connection.

Real-time

Two-way sync

Changes in InterSystems IRIS or Ramp instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever InterSystems IRIS or Ramp 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 InterSystems IRIS or Ramp record.

Observability

Monitoring

Track your InterSystems IRIS ⇄ Ramp sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and Ramp.

How the InterSystems IRIS and Ramp connectors work

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published API rate limits

Ramp

Integration surface
REST API (Developer API v1)
Authentication
OAuth 2.0: exchange client_id/client_secret (HTTP Basic) at api.ramp.com/developer/v1/token for scoped bearer tokens; client_credentials grant for server-to-server and authorization_code for user-delegated access; scopes follow resource:permission (e.g. transactions:read, bills:write, accounting:write).
Change detection
Signed webhooks (HMAC-SHA256 X-Ramp-Signature) for bill, transaction, reimbursement, vendor, and user events; otherwise poll incrementally (synced_after on transactions, from_created_at on bills) with keyset pagination, or read the audit-logs/events feed.
Capabilities
read · write · webhooks
Rate limits
200 requests per 10-second rolling window per source IP; exceeding it returns 429 Too Many Requests, and requests running over 60 seconds return 504. Results use keyset pagination (follow the page.next URL / start cursor); higher limits can be requested from support.
Ramp setup guide
How it works

How to connect InterSystems IRIS to Ramp — 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.

  1. 01

    Connect your apps

    Authenticate InterSystems IRIS and Ramp with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    InterSystems IRIS connected
    Ramp connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the InterSystems IRIS and Ramp 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · InterSystems IRIS ⇄ Ramp
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    InterSystems IRIS Ramp
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

InterSystems IRIS and Ramp integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 462 integrations available for InterSystems IRIS and Ramp.

Popular · 7 of 462
All InterSystems IRIS integrations All Ramp integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own