Skip to content
Security and identity ⇄ Accounting and finance

Active Directory to Ramp integration — real-time, two-way sync

Keep Active Directory 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 Active Directory and Ramp

Keep the people who can act on financial records in Ramp matched to their identities in Active Directory, so access is provisioned, updated, and revoked in real time.

Ramp runs the money — the ledgers, invoices, budgets, and payments — and every one of those actions is taken by a person with a login. Active Directory is where those people and their access actually live: who is employed, what team they belong to, and what they are allowed to do. The two systems rarely share customers or transactions, but they share the one thing that governs both — the user. When that overlap is maintained by hand, a departed employee keeps finance access for weeks and a new hire waits on a ticket to get any.

Stacksync keeps Vendors, Funds (Spend Controls), General Ledger Accounts, Transactions in Ramp aligned with Directory roles, Service principals & applications, Organizational units, Organizational contacts in Active Directory, field by field and in real time. A person added, moved, or deactivated on the identity side updates their matching user in the finance system within seconds, with the role or permission set mapped from the group they belong to. Direction is yours to set: lead provisioning from the directory, or let an HR-owned finance record drive the downstream accounts.

For a finance team, that alignment is an audit control rather than a convenience. When the user list in the books matches the identity source of truth, segregation-of-duties and access reviews start from data that is already correct instead of an export that was current last quarter.

Common use cases

  • 01 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.
  • 02 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.
  • 03 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.
  • 04 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.

Common sync patterns

People attributes for allocation and approvals

Department, manager, and employee identifiers carried in Active Directory flow to Ramp, so expense routing, cost-center allocation, and approval chains use the same org data as the directory.

Where Active Directory is the identity source: offboarding reaches the books

When a person is deactivated in Active Directory, their matching user in Ramp is disabled in the same motion, so departed employees keep no standing access to financial records.

One user roster across both systems

People, their status, and their contact details stay matched between Ramp and Active Directory, so the finance system's login list reflects who actually works here instead of drifting out of date.

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

Active Directory objects Ramp objects How this pairing syncs
Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. Users Employee and cardholder records; invited, updated, and deactivated, commonly synced from an HRIS or identity provider. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. General Ledger Accounts Chart-of-accounts entries uploaded from the ERP; accounting codings are posted back against transactions and bills. Groups is specific to Active Directory and General Ledger Accounts to Ramp — each maps to any object or custom field on the other side.
Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. Transactions Card purchase records with merchant, amount, and state; read for spend/GL sync and written back via accounting codings and sync status. Group memberships is specific to Active Directory and Transactions to Ramp — each maps to any object or custom field on the other side.
Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. Cards Physical and virtual card records; created and managed through the API to provision or suspend cardholder spend. Devices is specific to Active Directory and Cards to Ramp — each maps to any object or custom field on the other side.
Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. Departments Org groupings for cost-center and GL allocation; pushed from an ERP/HRIS and referenced by cards and transactions. Directory roles is specific to Active Directory and Departments to Ramp — each maps to any object or custom field on the other side.
Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. Reimbursements Out-of-pocket expense claims; read for reporting and marked ready-to-sync then synced to the ERP. Service principals & applications is specific to Active Directory and Reimbursements to Ramp — each maps to any object or custom field on the other side.

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

Active Directory Ramp Sub-second propagation

DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.

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

Ramp Active Directory 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 written to Active Directory through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
  • 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 Active Directory ⇄ Ramp

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Active Directory and Ramp connectors work

Active Directory

Integration surface
Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
Authentication
OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
Change detection
Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
Capabilities
read · write · webhooks
Rate limits
Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.

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

    Choose tables

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

Active Directory 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
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 499 integrations available for Active Directory and Ramp.

Popular · 8 of 499
All Active Directory 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