Connect Ramp to Rig

    Sync Ramp card transactions, bills, reimbursements, vendors and statements into Rig so spend can be read by department, merchant and card holder. You create a Developer app in Ramp that uses the Client Credentials grant and paste its client ID and secret.

    Before you start

    • You need admin access in Ramp. The Developer page under Company is only available to admins.
    • Decide to give the app read scopes only. Rig never writes to Ramp.

    Step 1: Create a Ramp Developer app

    1. In Ramp, go to Company then Developer.
    2. Click Create New App, name it (for example "Rig") and accept the terms.
    3. Under Grant types, click Add new grant type and select Client Credentials.
    4. Under Scopes, click Configure allowed scopes and select all ten read scopes: transactions:read, cards:read, reimbursements:read, bills:read, users:read, departments:read, merchants:read, vendors:read, statements:read and transfers:read.
    5. Copy the Client ID and Client Secret.

    Grant every scope
    A stream whose scope is missing from the app is refused by Ramp. Add all ten read scopes now so every stream can sync.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Ramp, open the card and click Connect.
    3. Client ID: paste the client ID of your Ramp app.
    4. Client secret: paste the client secret of your Ramp app.
    5. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    6. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Ramp lands in its own ramp schema in your warehouse:

    • Spend: transactions, reimbursements, bills and transfers.
    • Cards and statements: cards and statements.
    • People and counterparties: users, departments, merchants and vendors.

    Ramp allows 200 requests per 10 seconds from one source address, and Rig stays within that.

    Good to know

    • Ramp access tokens only carry the scopes the app was granted. If you add a scope later, Rig fetches a new token on its next run.
    • Sandbox and production are separate apps in Ramp. Create the app in the environment that holds your real spend.
    • The app acts for the whole business and is limited only by its scopes, so name it clearly to make it easy to find later.
    • To disconnect Ramp, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • See spend by team without waiting for close
    • Find duplicate and creeping software spend
    • Join spend to the revenue it supports

    More ideas for using Ramp

    Was this guide helpful?