MULTI-APP TOOLKIT
Build with Procore + Ramp
- Multi-app
- One MCP session
- 24 actions
- 20 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Procore and Ramp 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": "procore,ramp",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Procore and Ramp tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create Incident:
const result = await mcp.callTool({
name: "procore-create-incident",
arguments: {
companyId: 10,
projectId: 10,
},
})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 [procoreTools, rampTools] =
await Promise.all([
pd.components.list({ app: "procore" }),
pd.components.list({ app: "ramp" }),
])
// 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=procore" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=ramp" \
-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
Procore
Connected account
Ramp
Connected account
TOOLS
Procore tools
The Procore tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Create Incident
actionCreate a new incident. See the documentation.Writev0.0.3 -
Create Manpower Log
actionCreate a new manpower log. See the documentation.Writev0.0.3 -
Create RFI
actionCreate a new RFI. See the documentation.Writev0.0.2 -
Create Submittal
actionCreate a new submittal. See the documentation.Writev0.0.2 -
Create Timesheet
actionCreate a new timesheet. See the documentation.Writev0.0.2 -
List Company ID Options
actionRetrieves available options for the Company ID field.Read-onlyv0.0.1
Triggers top 4 of 17
-
Budget Snapshot Event (Instant)
triggerEmits an event each time a Budget Snapshot is created, updated, or deleted in a project.Instantv0.0.2 -
Commitment Change Order Event (Instant)
triggerEmits an event each time a Commitment Change Order is created, updated, or deleted in a project.Instantv0.0.2 -
New Budget Snapshot Event (Instant)
triggerEmit new event when a new budget snapshot event is created. See the documentation.Instantv0.0.1 -
New Change Order Package Event (Instant)
triggerEmit new event when a new change order package event is created. See the documentation.Instantv0.0.1
TOOLS
Ramp tools
The Ramp 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 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.3 -
Create Location
actionCreate a new Ramp 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.3 -
Create User Invite
actionInvite a new person to your Ramp organization by email — use this to onboard an employee who doesn't yet have a Ramp 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.6 -
Get Limit
actionRetrieve a single Ramp 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.3 -
Get Transaction
actionRetrieve a single Ramp 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.3 -
Get User
actionRetrieve a single Ramp 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.3 -
Issue Virtual Card
actionIssue a new Ramp virtual card (spend limit) for a user. Run List Users to find the user ID. 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 and allowed/blocked categories. Example: issue a $500/month card by passing the user's ID,$500, andMONTHLY. See the documentationWritev0.1.1 -
List Departments
actionRetrieve a list of Ramp 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.3
Triggers
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
- procore,ramp
- Primary app
- Procore (procore)
- Second app
- Ramp (ramp)
- Authentication
- OAuth + OAuth
- Available actions
- 24
- Available triggers
- 20