Skip to content
Database ⇄ Accounting and finance

DuckDB to Ramp integration — real-time, two-way sync

Keep DuckDB 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 DuckDB and Ramp

Work with Ramp's financial data straight from DuckDB: 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 Vendors, Funds (Spend Controls), General Ledger Accounts, Transactions from Ramp into Schemas, Tables, Views, External files (Parquet/CSV/JSON) in DuckDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against DuckDB, 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 Mirror Bills and their approval and payment state into an AP or ERP system, marking each one ready-to-sync then synced to keep both ledgers reconciled.
  • 02 Read Reimbursements into a finance database for cross-entity expense reporting and reconciliation without manual CSV exports.
  • 03 Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
  • 04 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.

Common sync patterns

Query finance data like any other data

Customers, invoices, and payments from Ramp live in DuckDB 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 DuckDB; Stacksync handles the API calls, rate limits, and retries against Ramp.

Write back safely

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

What you can sync between DuckDB 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.

DuckDB objects Ramp objects How this pairing syncs
Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. Transactions Card purchase records with merchant, amount, and state; read for spend/GL sync and written back via accounting codings and sync status. Database files is specific to DuckDB and Transactions to Ramp — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to organize tables in sync outputs. Cards Physical and virtual card records; created and managed through the API to provision or suspend cardholder spend. Schemas is specific to DuckDB and Cards to Ramp — each maps to any object or custom field on the other side.
Tables Columnar tables created via SQL; the destination for materialized sync data. Users Employee and cardholder records; invited, updated, and deactivated, commonly synced from an HRIS or identity provider. Tables is specific to DuckDB and Users to Ramp — each maps to any object or custom field on the other side.
Views SQL views used to shape or filter data for downstream consumers. Departments Org groupings for cost-center and GL allocation; pushed from an ERP/HRIS and referenced by cards and transactions. Views is specific to DuckDB and Departments to Ramp — each maps to any object or custom field on the other side.
External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. Reimbursements Out-of-pocket expense claims; read for reporting and marked ready-to-sync then synced to the ERP. External files (Parquet/CSV/JSON) is specific to DuckDB and Reimbursements to Ramp — each maps to any object or custom field on the other side.
Attached databases Additional database files or external systems attached into one session for cross-source queries. Bills Accounts-payable bills; created, updated, approved, and paid, then posted ready-to-sync and synced to accounting. Attached databases is specific to DuckDB and Bills to Ramp — each maps to any object or custom field on the other side.

How changes propagate between DuckDB 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.

DuckDB Ramp Interval-based propagation

DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.

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

Ramp DuckDB 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 DuckDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
  • 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 DuckDB ⇄ Ramp

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the DuckDB and Ramp connectors work

DuckDB

Integration surface
In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
Authentication
None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
Change detection
Polling or full re-reads; no change feed or transaction log API
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by local compute and I/O

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 DuckDB 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 DuckDB 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
    DuckDB connected
    Ramp connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the DuckDB 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 · DuckDB ⇄ 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
    DuckDB Ramp
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

DuckDB 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 443 integrations available for DuckDB and Ramp.

Popular · 7 of 443
All DuckDB 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