MULTI-APP TOOLKIT
Build with Calendly + GitHub
- Multi-app
- One MCP session
- 60 actions
- 31 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Calendly and GitHub 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": "calendly_v2,github",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Calendly and GitHub tools arrive
// together, each keyed by its own app's slug.
// e.g. run Cancel Event:
const result = await mcp.callTool({
name: "calendly_v2-cancel-event",
arguments: {
eventUuid: "Event UUID",
reason: "Reason",
},
})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 [calendlyV2Tools, githubTools] =
await Promise.all([
pd.components.list({ app: "calendly_v2" }),
pd.components.list({ app: "github" }),
])
// 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=calendly_v2" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=github" \
-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
Calendly
Connected account
GitHub
Connected account
TOOLS
Calendly tools
The Calendly tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 12
-
Cancel Event
actionCancel a scheduled Calendly event. Posts toPOST /scheduled_events/{uuid}/cancellation. Run List Events first to obtain the event UUID. Example: witheventUuidset toa1b2c3d4-e5f6-7890-abcd-ef1234567890andreasonset toSchedule conflict - rescheduling needed, the event is canceled and all invitees are notified. See the documentation.Writev0.0.2 -
Create a Scheduling Link
actionCreates a single-use scheduling link for an event type viaPOST /scheduling_links. Run List Event Types first to obtain the event type UUID. Example: withownerset tohttps://api.calendly.com/event_types/AAAAAAAAAAAAAAAA's UUID andmaxEventCountset to1, returns a booking URL likehttps://calendly.com/d/ABC-123/30-minute-meetingthat can be scheduled once before expiring. See the documentationWritev0.1.1 -
Create Invitee No Show
actionMarks an invitee as a no-show viaPOST /invitee_no_shows. Use when an invitee didn't attend a scheduled event and you want to flag it in Calendly. Run List Events first to obtain the event UUID, then select the invitee from the dropdown (populated from List Event Invitees). Example: witheventIdset toa1b2c3d4-e5f6-7890-abcd-ef1234567890, selecting invitee "Jane Doe" marks her as a no-show for that event. See the documentation.Writev0.0.7 -
Get Event
actionGets information about a scheduled event viaGET /scheduled_events/{uuid}. Provide either the Event UUID (from List Events) or the full Event URL. Example: witheventIdset toa1b2c3d4-e5f6-7890-abcd-ef1234567890, returns the event's name, start/end times, status, and location. See the documentation.Read-onlyv0.1.9 -
Get Event Invitee
actionRetrieve the full invitee resource (includingemail,name,status,reschedule_url, andno_show) viaGET /scheduled_events/{event_uuid}/invitees/{invitee_uuid}. Use the returnedreschedule_urlto direct an invitee to self-reschedule. Run List Events to find event UUIDs, then List Event Invitees to find invitee UUIDs. Example: witheventUuidset toa1b2c3d4-e5f6-7890-abcd-ef1234567890andinviteeUuidset tof7e6d5c4-b3a2-1098-fedc-ba9876543210, returns that invitee'semail,name, andstatus: "active". See the documentation.Read-onlyv0.0.2 -
List Event Invitees
actionList the invitees for a scheduled event viaGET /scheduled_events/{uuid}/invitees. Run List Events first to obtain the event UUID. Example: call witheventIdset toa1b2c3d4-e5f6-7890-abcd-ef1234567890andstatusset toactiveto return only that event's non-canceled invitees, each with auriwhose trailing segment is the invitee UUID used by Get Event Invitee and Create Invitee No Show. See the documentationRead-onlyv0.0.9 -
List Event Types
actionRetrieve the event types available to a user or organization viaGET /event_types. Use this to discover valid event type URIs and UUIDs for scheduling flows. Provide either an Organization URI or a User URI; if neither is provided the authenticated user is used. Use List Organization Memberships to find user and organization URIs. Example: called with no props, returns the authenticated user's event types such as{ name: "30 Minute Meeting", uuid: "AAAAAAAAAAAAAAAA" }— pass thatuuidas theownerprop in Create a Scheduling Link. See the documentation.Read-onlyv0.0.2 -
List Events
actionList scheduled Calendly events. Scope the results by providing at most one of Organization URI, User URI, or Group UUID; if none is provided, events for the authenticated user are returned (supplying more than one raises a configuration error). Narrow the results further with an invitee email to return only events scheduled with that invitee. Filter by date range usingMin Start Timeand/orMax Start Time, both ISO 8601 datetimes in UTC (e.g.2026-08-01T00:00:00Z). Each returned event includes auri; the trailing UUID segment is the event UUID used by downstream actions such as Get Event, List Event Invitees, Get Event Invitee, and Cancel Event. Example: called with no props, returns the authenticated user's upcoming events, each like{ name: "30 Minute Meeting", uri: "https://api.calendly.com/scheduled_events/a1b2c3d4-e5f6-7890-abcd-ef1234567890", status: "active" }. See the documentationRead-onlyv0.0.9
Triggers
-
New Event Scheduled
triggerEmit new event when a event is scheduled.v0.0.9 -
New Invitee Canceled
triggerEmit new event when an event is canceled.Instantv0.0.5 -
New Invitee Created
triggerEmit new event when a new event is scheduled.Instantv0.0.6 -
New Routing Form Submission Created
triggerEmit new event when a new routing form submission is created.Instantv0.0.5
TOOLS
GitHub tools
The GitHub tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 48
-
Create Issue
actionCreate a new issue in a repository, optionally with labels, assignees, and a milestone. Provide the repository as anowner/repostring. Labels and assignees are passed by name/login (e.g.bug,octocat) — setting them requires push access to the repo. To comment on an existing issue instead, use Create Issue Comment; to change an existing issue, use Update Issue. See the documentationWritev0.4.3 -
Search Issues and Pull Requests
actionSearch issues and pull requests across GitHub using the issues-search query DSL. This is the escape hatch for finding items by keyword, state, label, author, or assignee when you don't already know the issue/PR number. Build thequeryfrom space-separated qualifiers:repo:owner/nameto scope to one repo (a barerepo:namewith no owner is auto-resolved to your own account),is:issue/is:pr,is:open/is:closed,label:bug,author:octocat,assignee:octocat,in:title/in:body, and free-text keywords. Example:repo:PipedreamHQ/pipedream is:issue is:open label:bug raptor. Returns matching items (each withnumber,title,state,labels,html_url); feed a result'snumberinto Get Issue, Get Pull Request, or Create Issue Comment. See the query syntaxRead-onlyv0.3.3 -
Create Branch
actionCreate a new branch in a repository, pointing at the tip of a source branch. Provide the repository as anowner/repostring, the newbranchName, and optionally thesourceBranchto branch from (defaults to the repository's default branch). Use Create or Update File Contents to add commits to the new branch, then Create Pull Request to open a PR. See the documentationWritev1.0.2 -
Create Gist
actionAllows you to add a new gist with one or more files. See the documentationWritev0.0.18 -
Create Issue Comment
actionAdd a comment to an existing issue or pull request (GitHub treats PRs as issues for comments, so the samenumberworks for both). Provide the repository as anowner/repostring, the issue/PR number, and the comment body. If you only know the issue/PR by title, call Search Issues and Pull Requests first to resolve its number. See the documentationWritev0.1.3 -
Create or Update File Contents
actionCreate a new file or overwrite an existing one in a repository with a single commit. Provide the repository as anowner/repostring, the filepath, the raw textcontent(passed as-is — do not base64-encode it yourself), and a commit message. If the file already exists on the target branch it is overwritten; the required blob SHA is resolved for you automatically. Defaults to the repository's default branch unlessbranchis set. See the documentationWritev1.0.3 -
Create Pull Request
actionOpen a pull request proposing to merge one branch into another within a repository. Provide the repository as anowner/repostring, theheadbranch (the source containing your changes) and thebasebranch (the target, e.g.main), plus a title. The head and base branches must already exist and differ. For a cross-fork PR, setheadtousername:branch. Use Create or Update File Contents to push changes to a branch before opening the PR. See the documentationWritev1.0.3 -
Create Pull Request Review
actionSubmit a review on a pull request: approve it, request changes, or leave a general comment. SeteventtoAPPROVE,REQUEST_CHANGES, orCOMMENT— abodyis required forREQUEST_CHANGESandCOMMENT. Optionally attach inlinecommentstied to specific lines of the diff. GitHub forbids approving your own pull request, so useCOMMENTto leave feedback on PRs you authored. Provide the repository as anowner/repostring and the PR number. Use Get Pull Request Files to find the file paths and lines to comment on, and Search Issues and Pull Requests withis:prto resolve the PR number from a title. See the documentationWritev0.0.3
Triggers top 4 of 27
-
New Branch Created
triggerEmit new event when a branch is created.Instantv1.0.16 -
New Card in Column (Classic Projects)
triggerEmit new event when a (classic) project card is created or moved to a specific column. For Projects V2 useNew Issue with Statustrigger. More information hereInstantv1.0.15 -
New Collaborator
triggerEmit new event when a collaborator is addedInstantv1.0.16 -
New Commit
triggerEmit new event when commits are pushed to a branchInstantv1.0.17
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
- calendly_v2,github
- Primary app
- Calendly (calendly_v2)
- Second app
- GitHub (github)
- Authentication
- OAuth + OAuth
- Available actions
- 60
- Available triggers
- 31