MULTI-APP TOOLKIT
Build with Google Calendar + HubSpot
- Multi-app
- One MCP session
- 125 actions
- 33 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Google Calendar and HubSpot 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": "google_calendar,hubspot",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Google Calendar and HubSpot tools arrive
// together, each keyed by its own app's slug.
// e.g. run Add Attendees To Event:
const result = await mcp.callTool({
name: "google_calendar-add-attendees-to-event",
arguments: {
calendarId: "Calendar",
eventId: "Event",
},
})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 [googleCalendarTools, hubspotTools] =
await Promise.all([
pd.components.list({ app: "google_calendar" }),
pd.components.list({ app: "hubspot" }),
])
// 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=google_calendar" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=hubspot" \
-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
Google Calendar
Connected account
HubSpot
Connected account
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
TOOLS
HubSpot tools
The HubSpot tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 108
-
Add Comment
actionAdds a comment to a thread. See the documentationWritev0.0.8 -
Add Contact to List
actionAdds a contact to a specific static list. See the documentationWritev0.1.4 -
Add Note to Contact
actionMCP and AI agents: Prefer this action when the user wants to leave a note on a HubSpot contact using a contact ID and note text. Exposes onlyhubspot,contactId, andnoteBody(no engagement-type step, noreloadProps, no dynamic HubSpot schema fields). Do not use Create Engagement for this workflow. For every writable note property or non-contact associations, use Create Note instead. See the documentationWritev0.0.6 -
Archive Thread
actionArchives a thread (soft delete). The thread is hidden from active views but can be restored via the HubSpot UI or by listing archived threads. See the documentationWritev0.0.5 -
Batch Create Companies
actionCreate a batch of companies in Hubspot. See the documentationWritev0.0.18 -
Batch Create or Update Contact
actionCreate or update a batch of contacts by its ID or email. See the documentationWritev0.0.32 -
Batch Update Companies
actionUpdate a batch of companies in Hubspot. See the documentationWritev0.0.18 -
Batch Upsert Companies
actionUpsert a batch of companies in Hubspot. See the documentationWritev0.0.17
Triggers top 4 of 27
-
Deleted Blog Posts
triggerEmit new event for each deleted blog post.v0.0.45 -
New Company Property Change
triggerEmit new event when a specified property is provided or updated on a company. See the documentationv0.0.38 -
New Contact Added to List
triggerEmit new event when a contact is added to a HubSpot list. See the documentationv0.0.17 -
New Contact Property Change
triggerEmit new event when a specified property is provided or updated on a contact. See the documentationv0.0.41
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
- google_calendar,hubspot
- Primary app
- Google Calendar (google_calendar)
- Second app
- HubSpot (hubspot)
- Authentication
- OAuth + OAuth
- Available actions
- 125
- Available triggers
- 33