Integration · Payments and finance
AI agents for Ramp
Read Ramp balances, card transactions, reimbursements, bills, vendors, statements and people, and add a memo to a transaction, in production or the Ramp sandbox.
- Actions
- 12
- Read
- 11
- Write
- 1
Actions
What your agents can do in Ramp
12 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 11
Look things up. Nothing changes.
Get the company
Reads the Ramp business the app belongs to.
Get balances and limits
Reads the company's Ramp card balance and limits.
Find card transactions
Lists Ramp card transactions, filtered by date range, person, card, department, merchant, state, approval status, amount.
Get a transaction
Reads one Ramp card transaction by ID, with merchant details.
Find people
Lists the people in Ramp, optionally by email, role, status, department or employee ID.
Find reimbursements
Lists out-of-pocket and mileage reimbursements in Ramp, filtered by person, state, transaction date range or whether approved.
Find bills
Lists vendor bills in Ramp bill pay, filtered by vendor, invoice number, payment status (OPEN or PAID), approval status, or due or issued date ranges.
Get a bill
Reads one Ramp bill by ID.
Find vendors
Lists the business's vendors in Ramp, optionally by name or only active ones.
List statements
Lists Ramp card statements, newest first.
List departments
Lists the departments set up in Ramp, to filter transactions or people by department.
Write 1
Create, change or send.
Add a memo to a transaction
Writes the memo (the business reason) on a Ramp card transaction, replacing any memo it had; optionally keep it for this merchant's future transactions.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste the client ID and secret of an app your organization registered with Ramp. The platform fetches its tokens itself (OAuth client credentials).
Settings
- Environment
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Ramp data
Ask a question in plain words. The agent can get the company, get balances and limits or find card transactions in Ramp, then answers with what it found.
- 02
Let an agent update Ramp
Have the agent add a memo to a transaction in Ramp as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Ramp and Slack: it can get the company in Ramp and post a summary to a Slack channel in the same run.
FAQ
Ramp and MyDeepAgents
Can MyDeepAgents connect to Ramp?
Yes. The Ramp connector has 12 actions: 11 read and 1 makes changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Ramp?
Paste the client ID and secret of an app your organization registered with Ramp. The platform fetches its tokens itself (OAuth client credentials). The connection also asks for: Environment. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Ramp without asking?
Only if you let it. Its one action that changes data can be set to wait for a person's approval before it runs.
Can I use Ramp in workflows as well as agents?
Yes. Every Ramp action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Ramp to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.