MULTI-APP TOOLKIT
Build with Calendly + Intercom
- Multi-app
- One MCP session
- 25 actions
- 20 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Calendly and Intercom 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,intercom",
},
},
},
)
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 Intercom 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, intercomTools] =
await Promise.all([
pd.components.list({ app: "calendly_v2" }),
pd.components.list({ app: "intercom" }),
])
// 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=intercom" \
-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
Intercom
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
Intercom tools
The Intercom tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 13
-
Add Tag To Contact
actionAdds a specific tag to a contact in Intercom. Use Search Contacts to find the contact's ID and List Tag ID Options to find valid tag IDs before calling this action. Example: set Contact ID to63a07ddf05a32042dffac965and Tag ID to7522907to tag that contact. Returns the updated tag object on success. See the documentation.Writev0.0.5 -
Create Note
actionCreates a note on a contact's record in Intercom. The note is automatically attributed to the currently authenticated admin — no Admin ID prop is required. Use Search Contacts to find the contact's ID before calling this action. Example: set User to63a07ddf05a32042dffac965and Body toFollowed up via email on 2024-01-15to log a note on that contact. Returns the new note object includingid,body, andauthor. See the documentationWritev0.0.9 -
List Admin ID Options
actionRetrieves all admins in your Intercom workspace and returns their IDs and names. Call this action before any action that requires an Admin ID — such as Manage A Conversation, Reply To Conversation, or Send Message To Contact — to discover valid values. Example: returns[{ label: "Jane Doe", value: "25" }, ...]. See the documentation.Read-onlyv0.0.3 -
List Assignee ID Options
actionRetrieves all teams in your Intercom workspace and returns their IDs and names. Call this action before Manage A Conversation to discover valid team IDs for conversation assignment. Example: returns[{ label: "Support", value: "334" }, ...]. Use0to represent Unassigned. See the documentation.Read-onlyv0.0.3 -
List Conversations
actionLists conversations in your Intercom workspace, most recently updated first (GET /conversations). Use this to discover a conversation's ID before calling Reply To Conversation, Manage A Conversation, or Retrieve Conversation — there is no other way to look one up. Returns a bounded page of conversations, each includingid,state,created_at, and the latest message part. Ifpages.next.starting_afteris present in the response, call this action again with that cursor in Starting After to retrieve the next page. Pass Fields (e.g.["id", "state", "created_at"]) to limit each returned conversation to only those keys. Example: leave all props empty to fetch the 20 most recently updated conversations. See the documentation.Read-onlyv0.0.2 -
List Tag ID Options
actionRetrieves all tags in your Intercom workspace and returns their IDs and names. Call this action before Add Tag To Contact to discover valid tag IDs. Example: returns[{ label: "VIP", value: "7522907" }, ...]. See the documentation.Read-onlyv0.0.3 -
Manage A Conversation
actionClose, snooze, open, or assign a conversation by its ID. Which of the optional props apply depends on Message Type:closeuses Body,snoozeduses Snoozed Until,assignmentuses Type together with Assignee ID or Team Assignee ID, andopenuses none of them. Example: set Conversation ID to192783634529321, Message Type toclose, and Body toIssue resolvedto close that conversation with a closing comment. See the documentation.Writev0.1.2 -
Reply To Conversation
actionReply to an existing Intercom conversation as an admin or on behalf of a contact (POST /conversations/{conversation_id}/reply). Use List Admin ID Options to find a valid Admin ID, and Search Contacts to find a contact's Intercom user ID, email, or external user ID. Example: set Conversation ID to192783634529321, Reply Type toadmin, Message Type tocomment, Body toThanks for reaching out!, and Admin ID to25to post that comment as an admin reply. See the documentation.Writev0.1.1
Triggers top 4 of 16
-
New Companies
triggerEmit new event each time a new company is added.v0.0.9 -
New Reply From Admin
triggerEmit new event each time an admin replies to a conversation.v0.0.9 -
New Conversations
triggerEmit new event each time a new conversation is added.v0.0.9 -
New Reply From User
triggerEmit new event each time a user replies to a conversation.v0.0.9
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,intercom
- Primary app
- Calendly (calendly_v2)
- Second app
- Intercom (intercom)
- Authentication
- OAuth + OAuth
- Available actions
- 25
- Available triggers
- 20