MULTI-APP TOOLKIT
Build with Ramp (Sandbox Version) + ServiceTitan
- Multi-app
- One MCP session
- 18 actions
- 3 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Ramp (Sandbox Version) and ServiceTitan tool at once — connect once, list tools, and call them like any single-app session.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "ramp_sandbox,servicetitan",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Ramp (Sandbox Version) and ServiceTitan tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create Department:
const result = await mcp.callTool({
name: "ramp_sandbox-create-department",
arguments: {
name: "Name",
},
})import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const externalUserId = "{external_user_id}" // any stable ID for this user in your system
const [rampSandboxTools, servicetitanTools] =
await Promise.all([
pd.components.list({ app: "ramp_sandbox" }),
pd.components.list({ app: "servicetitan" }),
])
// One external user owns both connected accounts, so either app's tools
// run on their behalf with the same externalUserId.curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=ramp_sandbox" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=servicetitan" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
# Connect both accounts to the same external_user_id, then
# configure and invoke either app's tools on that user's behalf.ARCHITECTURE
One user, two connected accounts
Your user connects each account once, under whatever ID they already have in your product. The two stay independent — either can be revoked on its own — and your code reaches both through that one user.
Your product
external_user_id
{external_user_id}Pipedream Connect
Managed identity
Auth · tools · routing
Ramp (Sandbox Version)
Connected account
ServiceTitan
Connected account
TOOLS
Ramp (Sandbox Version) tools
The Ramp (Sandbox Version) tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 18
-
Create Department
actionCreate a new Ramp Sandbox department (e.g.Engineering,Marketing). Use this to add an organizational unit before assigning users to it. Returns the new department'sid, which you can pass to Update User to set a user's department, or use to filter List Transactions / List Users. See the documentationWritev0.0.2 -
Create Location
actionCreate a new Ramp Sandbox location (e.g.New York HQ). Use this to add a site before assigning users to it; the returnedidcan be passed to Update User or used to filter List Transactions / List Users. Associating an entity is optional — set the Entity ID only for multi-entity businesses that scope locations to a specific legal entity. See the documentationWritev0.0.2 -
Create User Invite
actionInvite a new person to your Ramp Sandbox organization by email — use this to onboard an employee who doesn't yet have a Ramp Sandbox account. Requires their email, first and last name, androle(e.g.BUSINESS_USER); department, location, and direct manager are optional. Run List Departments and List Locations to find valid department/location IDs, and List Users to find a direct manager's user ID — each is a Ramp UUID, e.g.fffe6c22-698f-4dc5-b2b1-b35f86947d90. This is a deferred operation, so the invited user may not appear in List Users immediately; once they do, use Update User to change their role, department, location, or manager. See the documentationWritev0.0.5 -
Get Limit
actionRetrieve a single Ramp Sandbox spend limit by ID. Run the List Limits action first to find a valid limit ID. Example: given a limit id from List Limits, returns the limit's display name, state (e.g.ACTIVE), balance, spend program, and spending restrictions. See the documentationRead-onlyv0.0.2 -
Get Transaction
actionRetrieve a single Ramp Sandbox transaction by ID. Run the List Transactions action first to find a valid transaction ID. Example: given a transaction id from List Transactions, returns the full transaction — e.g. merchantFacebook Ads, amount$135.00, categoryAdvertising, plus line items and accounting detail. See the documentationRead-onlyv0.0.2 -
Get User
actionRetrieve a single Ramp Sandbox user by ID. Run the List Users action first to find a valid user ID. Example: given a user id from List Users, returns that user's full record — name, email, role (e.g.BUSINESS_OWNER), department id, and location id. See the documentationRead-onlyv0.0.2 -
Issue Virtual Card
actionIssue a new Ramp Sandbox virtual card (spend limit) for a user. Requires a Virtual Card Name and the user's ID (run List Users to find it). Works two ways: (1) link to an existing spend program — set Link to Existing Spend Program on and pass a Spend Program ID (run List Spend Programs), and the program governs the card's restrictions; or (2) set a custom limit — leave linking off and pass a Total Limit per Interval (e.g.$500) and an Interval (e.g.MONTHLY), optionally a per-transaction cap, allowed/blocked categories, and whether the physical card (Primary Card Enabled) and Reimbursements Enabled apply. Example: issue a $500/month card by passing a Virtual Card Name (e.g.Marketing SaaS), the user's ID,$500, andMONTHLY. See the documentationWritev0.1.1 -
List Departments
actionRetrieve a list of Ramp Sandbox departments. Use this to find department IDs for other actions such as Update User and List Transactions. Example: returns{ id, name }pairs such as{ "id": "fffe6c22-698f-4dc5-b2b1-b35f86947d90", "name": "Engineering" }— pass theidto Update User to set a user's department. Returns one page of up topageSizeresults (max 100); apage.nextvalue in the response means more departments exist beyond this page. See the documentationRead-onlyv0.0.2
Triggers
TOOLS
ServiceTitan tools
The ServiceTitan tools this pairing puts in reach, each one running on your user's own connected account.
Actions
No ServiceTitan actions are available yet.
Triggers
No ServiceTitan triggers are available yet.
MULTI-APP
Works with more apps
The combinations customers connect alongside these two — nothing here is limited to a pair.
REFERENCE
Toolkit details
- x-pd-app-slug
- ramp_sandbox,servicetitan
- Primary app
- Ramp (Sandbox Version) (ramp_sandbox)
- Second app
- ServiceTitan (servicetitan)
- Authentication
- OAuth + OAuth
- Available actions
- 18
- Available triggers
- 3