MULTI-APP TOOLKIT
Build with Box + Google Calendar
- Multi-app
- One MCP session
- 36 actions
- 9 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Box and Google Calendar 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": "box,google_calendar",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Box and Google Calendar tools arrive
// together, each keyed by its own app's slug.
// e.g. run Add Comment:
const result = await mcp.callTool({
name: "box-add-comment",
arguments: {
folderId: "Parent Folder",
fileId: "File",
},
})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 [boxTools, googleCalendarTools] =
await Promise.all([
pd.components.list({ app: "box" }),
pd.components.list({ app: "google_calendar" }),
])
// 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=box" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=google_calendar" \
-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
Box
Connected account
Google Calendar
Connected account
TOOLS
Box tools
The Box tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 19
-
Add Comment
actionAdds a comment to a Box file. To mention a user, include@[user_id:name]in the message and Box will notify them by email. Use Get Comments to read existing comments on a file. See the documentation.Writev0.0.2 -
Create Box Sign Request
actionCreates a Box Sign signature request and sends it to the listed signers. Requires at least one signer, plus the document(s) to sign passed viaAdditional Options— eithersource_files(e.g.[{"id": "123456789", "type": "file"}]) or atemplate_id; Box rejects requests with no document source. The signed document and signing log are saved to theParent Folder. See the documentation.Writev0.0.9 -
Create Collaboration
actionAdds a collaboration for a user or group on a file or folder, granting them access with a role (editor, viewer, previewer, uploader, previewer uploader, viewer uploader, or co-owner). Item Type must befileorfolder. Invite users by email or user ID; groups must be invited by group ID only. Can View Path applies only to folder collaborations. Use Delete Collaboration to revoke access. See the documentation.Writev0.0.2 -
Create Folder
actionCreates a new empty folder within the specified parent folder. Parent folder ID0is the root (All Files). Folder names must be 1-255 characters, use only Unicode Basic Multilingual Plane (BMP) characters, and cannot contain non-printable characters,/or\, leading or trailing spaces, or be.or... Names must be unique within the parent (case-insensitive). Use List Folder Items to inspect contents, or Move Folder / Delete Folder to reorganize afterward. See folder name restrictions. See the documentation.Writev0.0.2 -
Create Shared Link
actionCreates or updates a shared link for a file or folder. Access levels:open,company, orcollaborators. A password can only be set when access isopen; download permission applies only when access isopenorcompany. A resource can have only one shared link at a time. See the documentation.Writev0.0.2 -
Delete Collaboration
actionRemoves a collaboration, revoking a user's or group's access to a file or folder. Use Create Collaboration to grant access first and obtain a collaboration ID from its response. See the documentation.Writev0.0.2 -
Delete Folder
actionDeletes a folder by moving it to trash (or permanently when enterprise settings require). Set Recursive totrueto delete non-empty folders and all contents; without it, deleting a non-empty folder fails. Deleting a large folder can take longer than Box's request timeout — Box then returns HTTP 503 while the deletion continues in the background, which this action reports as accepted (accepted: true). This cannot be undone from this action — use List Folder Items to verify contents first. See the documentation.Writev0.0.2 -
Download File
actionDownloads a file from Box to your workflow's/tmpdirectory and returns the saved file path. Use Get File Metadata to check the file's name and size first, or Get File Text to extract text content without downloading. See the documentationWritev0.0.12
Triggers
-
New Event
triggerEmit new event when any of the selected event types occurs on the target file or folder, via a Box webhook. See the documentationInstantv0.0.10 -
New File Event
triggerEmit new event when a file is uploaded to, or moved into, the target folder (FILE.UPLOADED), via a Box webhook. Box fires this trigger for both cases, so moving an existing file into the folder also emits an event. See the documentationInstantv0.1.5 -
New Folder Event
triggerEmit new event when a folder is created within the target folder (FOLDER.CREATED), via a Box webhook. See the documentationInstantv0.0.10
TOOLS
Google Calendar tools
The Google Calendar tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 17
-
Add Attendees To Event
actionAdd one or more attendees (invitees) to an event that ALREADY EXISTS on a Google Calendar, without recreating it. New attendees are merged into the event's current attendee list — existing attendees are preserved, not replaced. Use this when the user wants to invite additional people to an event they already have; identify the target event witheventIdfirst (e.g. via list-events or get-event). When creating a brand-new event, set its attendees directly in create-event instead of calling this afterward. See the documentationWritev0.0.11 -
Add Quick Event
actionCreate a quick event to the Google Calendar. See the documentationWritev0.1.15 -
Create Event
actionCreate a new event on a Google Calendar — a single or recurring appointment at a specific date/time (optionally with attendees, location, and description). Use this whenever the user wants to add something to their calendar. This creates calendar EVENTS only: it cannot configure calendar settings, working hours, availability, or default preferences, and it cannot create a new calendar. Do not represent any of those requests as an event — creating an event named after the request does not fulfill it. See the documentationWritev1.1.2 -
Delete an Event
actionDelete a single event from a Google Calendar. Deletes only the one event identified byeventId— it does NOT clear a whole day or delete multiple events. When the user asks to delete several events, clear a day, or the target is ambiguous, first confirm with the user (ideally listing what will be deleted) before calling this, and call it once per event. See the documentationWritev0.1.14 -
Get Current User
actionRetrieve information about the authenticated Google Calendar account, including the primary calendar (summary, timezone, ACL flags), a list of accessible calendars, user-level settings (timezone, locale, week start), and the color palette that controls events and calendars. Ideal for confirming which calendar account is in use, customizing downstream scheduling, or equipping LLMs with the user’s context (timezones, available calendars) prior to creating or updating events. See the documentation.Read-onlyv0.0.6 -
Get Date Time
actionGet current date and time for use in Google Calendar actions. Useful for agents that need datetime awareness and timezone context before calling other Google Calendar tools.Read-onlyv0.0.5 -
List Calendars
actionRetrieve a list of calendars from Google Calendar. See the documentationRead-onlyv0.1.13 -
List Color ID Options
actionRetrieves available options for the Color ID field.Read-onlyv0.0.3
Triggers top 4 of 6
-
New Created or Updated Event (Instant)
triggerEmit new event when a Google Calendar events is created or updated (does not emit cancelled events)v0.1.20 -
New Calendar Created
triggerEmit new event when a calendar is created.v0.1.16 -
New Event Matching a Search
triggerEmit new event when a Google Calendar event is created that matches a searchv0.1.16 -
New Cancelled Event
triggerEmit new event when a Google Calendar event is cancelled or deletedv0.1.16
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
- box,google_calendar
- Primary app
- Box (box)
- Second app
- Google Calendar (google_calendar)
- Authentication
- OAuth + OAuth
- Available actions
- 36
- Available triggers
- 9