Real-time
Two-way sync
Changes in Nutshell or Ramp instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Accounting and finance
Nutshell to Ramp integration — real-time, two-way sync
Keep Nutshell 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 Nutshell and Ramp
Sync customers, invoices, and payment status between Ramp and Nutshell in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Nutshell knows the relationship: who the contacts are and what is in motion with the account. Ramp knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.
Stacksync links Reimbursements, Bills, Vendors, Funds (Spend Controls) in Ramp to Products, Tags, Users, Leads in Nutshell with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.
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 Keep People and Companies consistent between Nutshell and email marketing or outreach tools.
- 04 Write subscription or product data from internal systems into Nutshell so reps see account context.
Common sync patterns
Collections with context
Finance sees the account owner and relationship history from Nutshell when chasing a balance, and sales sees that the chase is happening.
Where Nutshell tracks deals: closed-won creates the finance record
A won opportunity creates or updates the customer in Ramp with the right billing details, so invoicing starts without re-keying.
Payment status on the account
Invoice and payment status from Ramp appears on the account in Nutshell, so reps see overdue balances before they promise the next order.
What you can sync between Nutshell 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.
| Nutshell objects | Ramp objects | How this pairing syncs | |
|---|---|---|---|
| Users Rep records used to resolve ownership when syncing assignments | 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. | |
| Tags Segmentation labels mapped to lists or filters in downstream tools | Reimbursements Out-of-pocket expense claims; read for reporting and marked ready-to-sync then synced to the ERP. | Tags is specific to Nutshell and Reimbursements to Ramp — each maps to any object or custom field on the other side. | |
| Leads Nutshell's deal object; synced as the pipeline record linked to people and companies | Bills Accounts-payable bills; created, updated, approved, and paid, then posted ready-to-sync and synced to accounting. | Leads is specific to Nutshell and Bills to Ramp — each maps to any object or custom field on the other side. | |
| People Individual contacts, kept consistent with marketing and outreach tools | Vendors Supplier records under the accounting namespace; uploaded and updated for AP matching and payments. | People is specific to Nutshell and Vendors to Ramp — each maps to any object or custom field on the other side. | |
| Companies Account records that group people and leads for account-level syncs | Funds (Spend Controls) Spend controls governing card usage; read and created via the funds API to enforce budgets per user, department, or program. | Companies is specific to Nutshell and Funds (Spend Controls) to Ramp — each maps to any object or custom field on the other side. | |
| Activities Logged calls, meetings, and emails used for engagement reporting | General Ledger Accounts Chart-of-accounts entries uploaded from the ERP; accounting codings are posted back against transactions and bills. | Activities is specific to Nutshell and General Ledger Accounts to Ramp — each maps to any object or custom field on the other side. |
How changes propagate between Nutshell 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.
Nutshell Ramp Sub-second propagation
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
DeliveryEach detected change is written to Ramp through its API, with automatic retries and rate-limit backoff.
Ramp Nutshell 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 Nutshell through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Nutshell: Subject to the platform's 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 Nutshell ⇄ Ramp
Connect Nutshell and Ramp for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Nutshell–Ramp connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Nutshell 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 Nutshell or Ramp record.
Observability
Monitoring
Track your Nutshell ⇄ Ramp sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Nutshell and Ramp.
How the Nutshell and Ramp connectors work
Nutshell
- Integration surface
- JSON-RPC API over HTTPS; a newer REST API is also offered
- Authentication
- HTTP Basic with account email and API key
- Change detection
- webhook subscriptions for record events, with polling as fallback
- Capabilities
- read · write · webhooks
- Rate limits
- subject to the platform's 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.
How it works
How to connect Nutshell 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.
- 01
Connect your apps
Authenticate Nutshell 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.
Nutshell
connected
Ramp
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Nutshell 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.
objects · Nutshell ⇄ RampCustomers 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.
Nutshell RampCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Nutshell and Ramp integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Nutshell and Ramp: authenticate both systems, choose the objects to sync (such as Nutshell's Users and Tags), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Ramp side: Reimbursements, Bills, Vendors, Funds (Spend Controls), plus custom fields where Ramp exposes them. On the Nutshell side: Products, Tags, Users, Leads. 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 Nutshell and Ramp: Collections with context; Where Nutshell tracks deals: closed-won creates the finance record; Payment status on the account. Finance sees the account owner and relationship history from Nutshell when chasing a balance, and sales sees that the chase is happening.
-
Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. Ramp: 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). Stacksync manages authentication, retries, and rate limits on both sides.
-
Ramp: Accounting is push-based: partners upload GL accounts and field options, post codings, then post ready-to-sync and sync status — Ramp does not pull from the ERP. Nutshell: Nutshell's most full-featured API is JSON-RPC: each call names a method such as findLeads or editLead instead of hitting resource URLs, though a newer REST API is also available. Stacksync's field mapping accounts for these differences between Nutshell and Ramp without custom code.
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 415 integrations available for Nutshell and Ramp.
Popular · 5 of 415
No integrations match .
