Pull from Ramp
The Pull from Ramp step syncs your Ramp data into Prowork on a schedule or on demand. Pull from any of eleven Ramp resources, optionally scoped by date range, state, or merchant category.Authentication
Prowork connects to Ramp via OAuth 2.0. Authorize once per Ramp business.1
Add a Pull from Ramp step from the Finance section of the step library.
2
Click Authorize Ramp and sign in to Ramp in the window that opens.
3
Confirm your Ramp business and click Authorize to grant read-only access.
4
You’ll be redirected back to Prowork with your account connected.
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
FAQ
Who needs to authorize Ramp?
A Ramp admin (or owner). Ramp restricts third-party app authorization to admin-level roles, so a non-admin clicking Authorize Ramp will hit a permissions error in Ramp’s consent window. The admin only needs to do this once per Ramp business.Does the admin have to build the flow?
No. The admin authorizes the connection, and that credential can then be shared with other Prowork users in your workspace, who can use it in their own flows without ever signing into Ramp. See Connecting integration accounts.Can the admin limit what Prowork can see?
Scope is set during the Ramp authorization step. Prowork requests read-only scopes (transactions:read, cards:read, bills:read, etc.) and never requests write access or sensitive scopes like cards:read_vault. If the admin declines a scope, datasets relying on it will return an authorization error on pull.