Pull from Ramp
The Pull from Ramp step syncs your Ramp data into Parabola on a schedule or on demand. Pull from any of eleven Ramp resources, optionally scoped by date range, state, or merchant category.Authentication
Parabola connects to Ramp via OAuth 2.0 — authorize once per Ramp business.Each authorization covers one Ramp business. For multiple businesses, add a separate Pull from Ramp step per business and click Edit accounts to authorize each one.
bills:read, cards:read, transactions:read, etc.) and never requests write access or sensitive scopes like cards:read_vault.
Configure your settings
Pick a Dataset to pull in from the dropdown. The eleven supported resources are:- Spend activity — Transactions, Reimbursements, Bills, Purchase orders
- Cards and limits — Cards, Limits
- Counterparties — Vendors, Merchants
- Organization — Users, Departments, Locations
- Date range — Transactions, Bills, Reimbursements, and Purchase orders support relative ranges (e.g. “Last 7 days”). Use this for incremental loads to avoid re-pulling history on every run.
- State/Status — Filter Transactions (Cleared, Pending, Declined, Error), Reimbursements (Pending, Approved, Awaiting export, etc.), or Bills (Open, Paid). Leave blank to pull all states.
- Merchant category — Scope Merchants by category name, or leave blank for all.
Ramp’s API doesn’t support server-side filtering on amount or custom fields. Use a Filter rows step downstream for that logic.
Common use cases
- Spend reconciliation — Join Ramp transactions to GL data from QuickBooks, NetSuite, or Xero to catch missing categorizations before close.
- Executive dashboards — Combine transactions, reimbursements, and bills, then push results to Google Sheets, Looker, or Metabase.
- Reimbursement alerts — Filter for pending or approved reimbursements and notify your finance lead in Slack.
- Vendor & category reports — Aggregate spend by vendor or merchant category and email weekly to stakeholders.
- Warehouse sync — Push Ramp data to Snowflake, BigQuery, or Redshift for unified spend analytics.
Tips
- Incremental loads: Set a relative date range (e.g. “Last 1 day”) and schedule the flow instead of re-pulling history each run.
- Multiple businesses: Add one step per Ramp business, then use a Stack tables step to combine outputs.
- Enrich with context: Join Transactions to Users, Departments, or Cards on their IDs — Ramp returns IDs by default, so joins are lightweight.
- Name your steps: With eleven resources sharing field names like
id,state, andamount, labeling each step (e.g. “Pull Ramp transactions”) keeps flows readable.
Troubleshooting
| Error | Fix |
|---|---|
| ”Select what to pull from Ramp.” | Choose a dataset from the Dataset to pull in dropdown. |
| ”Ramp authorization is required.” | Click Edit accounts and re-authorize. |
| ”Ramp API returned an error.” | Re-run the flow. If it persists, check that the connected Ramp user still has access to the resource. |
| Date range invalid. | Make sure your start date is before your end date. |
| Pagination limit reached. | Narrow your date range and run the flow in multiple passes, or contact Parabola support. |