MULTI-APP TOOLKIT
Build with Google Calendar + Notion (API Key)
- Multi-app
- One MCP session
- 30 actions
- 12 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Google Calendar and Notion (API Key) 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,notion_api_key",
},
},
},
)
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 Notion (API Key) 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, notionApiKeyTools] =
await Promise.all([
pd.components.list({ app: "google_calendar" }),
pd.components.list({ app: "notion_api_key" }),
])
// 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=notion_api_key" \
-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
Notion (API Key)
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.13 -
Add Quick Event
actionCreate a quick event to the Google Calendar. See the documentationWritev0.1.17 -
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.2.1 -
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.15 -
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.7 -
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.6 -
List Calendars
actionRetrieve a list of calendars from Google Calendar. See the documentationRead-onlyv0.1.14 -
List Color ID Options
actionRetrieves available options for the Color ID field.Read-onlyv0.0.4
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.21 -
New Calendar Created
triggerEmit new event when a calendar is created.v0.1.17 -
New Event Matching a Search
triggerEmit new event when a Google Calendar event is created that matches a searchv0.1.17 -
New Cancelled Event
triggerEmit new event when a Google Calendar event is cancelled or deletedv0.1.17
TOOLS
Notion (API Key) tools
The Notion (API Key) tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 13
-
Append Block to Parent
actionAppend Markdown content to the bottom of a Notion page (or block). Thecontentis parsed from Markdown into Notion blocks — use it to add paragraphs, headings, bullet/numbered lists, to-dos, quotes, code, etc. Provide the page ID or URL (use Search to resolve a page name into an ID). To change a database row's property values instead, use Update Page. See the documentationWritev0.0.5 -
Copy Page From Template
actionCopy an EXISTING page (template) into a new page with a new title. Use this ONLY when the user is reusing the structure of an existing page as a template (e.g. "copy this offer letter template for a new candidate"). Do NOT use to create a new page with original content — for that, use Create Page. The source page must already exist in Notion and is identified by its page ID. See the documentationWritev0.0.5 -
Create Comment
actionAdd a comment to a Notion page, or reply to an existing discussion thread. Provide either a page ID/URL (use Search to resolve a page name) or a discussion ID — not both. See the documentationWritev0.0.5 -
Create Page
actionCreate a new Notion page. Theparentcan be either another page (creates a subpage) or a database/data source (creates a row in that database). Provide the parent's ID or URL — use Search to resolve a name into an ID. When the parent is a database, setpropertiesto a flat JSON object of column-name → value (e.g.{ "Status": "Active", "ThreatLevel": 9 }); call Retrieve Database Schema first to learn the exact column names and valid select options.contentis the page body as Markdown (headings, bullet lists, paragraphs, etc.). See the documentationWritev0.0.5 -
Create Page from Data Source
actionCreate a new page (row) in a Notion data source (database). Provide the parent data source ID and the row's field values as a JSON object keyed by column name. Use the Search action (withfilter: data_source) to resolve a database name into its data source ID, and Retrieve Database Schema to learn the exact column names and types before setting values. Optionally add page body content withPage Content(Markdown). Example: parentDataSource"a1b2c3d4-..."with properties{ "Name": "Q1 Report", "Status": "In Progress", "Tags": ["finance"] }→ creates a new row with those fields and returns the created page object. See the documentationWritev0.0.5 -
Get Page
actionRetrieve a Notion page: both its property values and its body content rendered as Markdown. Use this to read what a page says or to inspect a database row's fields. Provide a page ID or a Notion page URL (use Search to resolve a page name into an ID). See the documentationRead-onlyv0.0.5 -
Query Data Source
actionFilter and sort the pages (rows) inside a Notion database (data source) by their property values. Discover exact property names and option values with Retrieve Database Schema first, then build a filter against them. Afilteris a JSON object: a single condition{ "property": "Status", "select": { "equals": "Escaped" } }, or a compound{ "and": [ ... ] }/{ "or": [ ... ] }. The condition key matches the property type — e.g.select,status,multi_select,number({ "greater_than": 5 }),checkbox({ "equals": true }),rich_text/title({ "contains": "..." }),date. Omitfilterto return all rows. Provide the data source ID (use Search withfilter: data_sourceto resolve a database name). See the documentationRead-onlyv0.0.5 -
Retrieve Data Source Content
actionGet all content of a data source. See the documentationRead-onlyv0.0.5
Triggers top 4 of 6
-
New Comment Created
triggerEmit new event when a new comment is created in a page or block. See the documentationv0.0.5 -
New Data Source Created
triggerEmit new event when a data source is created. See the documentationv0.0.5 -
New or Updated Page in Data Source (By Property)
triggerEmit new event when a page is created or updated in the selected data source. See the documentationv0.0.5 -
New Page in Data Source
triggerEmit new event when a page is created in the selected data source. See the documentationv0.0.5
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,notion_api_key
- Primary app
- Google Calendar (google_calendar)
- Second app
- Notion (API Key) (notion_api_key)
- Authentication
- OAuth + API key
- Available actions
- 30
- Available triggers
- 12