Ramp
Connect Ramp to Ploy to see every user in your Ramp business, whether they are active, invited or deactivated, and the role each one holds. Ploy can also invite users, deactivate and reactivate them, and change their role.
Ploy connects through the Ramp Developer API with an app that you register in your own Ramp business.
This integration is in beta
The Ramp integration is in beta. It was built from Ramp's API documentation and has not yet been checked against a live Ramp business, so some details may need adjusting once customers connect it. Beta does not limit what the integration can do.
The first step of setup is a consent checkbox. Ticking it lets Ploy capture redacted error data when a request to Ramp fails: the error response Ramp sends back, with personal details, keys and other secrets removed. Ploy uses it only to fix problems with this integration. You must tick the box to continue.
What Ploy reads
Every Ramp user, including invited, draft and deactivated users, with their name, email address and employee ID
Each user's status: active, onboarding, invited, draft, invitation expired, deactivated or suspended
Each user's role, for example Business admin, Business user, Bookkeeper, Auditor, IT admin or Guest user
Ploy does not read cards, transactions, bills, reimbursements, vendors, contracts or any spend data. Departments, locations and custom roles are not scanned.
Before you start
You need a Ramp admin or business owner, who can register a Developer API app.
Register a Developer API app in Ramp
Sign in to Ramp as an admin or business owner.
Open Ramp's developer settings and create a new app.
Allow the Client Credentials grant type.
Add the users:read scope, so Ploy can scan your users.
Add the users:write scope, so Ploy can invite, deactivate and reactivate users and change their role. Ploy asks Ramp for both scopes every time it connects, so the app needs both.
Copy the client ID and client secret. Treat the secret like a password.
Connect Ramp in Ploy
In Ploy, open Integrations and choose Ramp.
Tick the beta consent checkbox.
Paste the client ID and client secret.
Click Test. Ploy reads your Ramp users to check the app works.
Finish the setup. The first scan starts straight away.
Things to know
Deactivated and suspended users show as having lost access straight away.
Invited users who have not accepted yet count as having access, because an admin sent the invitation. Draft users and expired invitations do not.
Each user's role shows as a label in Ploy. When someone's role changes in Ramp, the old label is removed on the next scan.
Ramp has no way to delete a user. To remove someone's access from Ploy, deactivate them. Deactivating freezes their cards; reactivating restores them with the role they had. Ploy does not reactivate a user Ramp itself suspended.
Users invited from Ploy get the role the flow chooses, or Business user if it chooses none. Ramp emails them an invitation and adds them a few seconds later, so they may appear in Ploy only after the next scan.
Ploy can change a user's role to Auditor, Business admin, Business bookkeeper, Business user, Guest user or IT admin. It cannot make anyone the business owner or change the business owner's role.
Removing the Business admin role from Ploy makes the person a Business user. Other roles are changed by giving the person a different role, or in Ramp.
Ploy will not change the role of a deactivated user. Reactivate them first.
Ramp limits how fast its API can be called from one address. A large business may take a little longer to scan.
Troubleshooting
Ramp rejected that client ID and secret: check both were copied in full, that the app still exists and that it allows the Client Credentials grant.
That app cannot read users: add the users:read and users:write scopes to the app in Ramp, then test again.
Ramp refused the change: add the users:write scope to the app, then try again.
Ramp refused the change, with a reason: the message shows Ramp's reason, for example an email address that is not valid.