MULTI-APP TOOLKIT
Build with Google Calendar + PostgreSQL
- Multi-app
- One MCP session
- 26 actions
- 11 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Google Calendar and PostgreSQL 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,postgresql",
},
},
},
)
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 PostgreSQL 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, postgresqlTools] =
await Promise.all([
pd.components.list({ app: "google_calendar" }),
pd.components.list({ app: "postgresql" }),
])
// 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=postgresql" \
-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
PostgreSQL
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
PostgreSQL tools
The PostgreSQL tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 9
-
Execute SQL Query
actionExecute a custom PostgreSQL query. See our docs to learn more about working with SQL in Pipedream.Writev3.0.5 -
Delete Row(s)
actionDeletes a row or rows from a table. See the documentationWritev2.0.9 -
Find Row
actionFinds a row in a table via a lookup column. See the documentationRead-onlyv2.0.9 -
Find Row With Custom Query
actionFinds a row in a table via a custom query. See the documentationRead-onlyv2.0.9 -
Insert Row
actionAdds a new row. See the documentationWritev2.0.9 -
List Schema Options
actionRetrieves available options for the Schema field.Read-onlyv0.0.1 -
Query SQL Database
actionExecute a SQL Query. See our docs to learn more about working with SQL in Pipedream.Writev0.0.5 -
Update Row
actionUpdates an existing row. See the documentationWritev2.0.9
Triggers top 4 of 5
-
New Column
triggerEmit new event when a new column is added to a table. See the documentationv2.0.8 -
New or Updated Row
triggerEmit new event when a row is added or modified. See the documentationv2.0.9 -
New Row
triggerEmit new event when a new row is added to a table. See the documentationv3.0.8 -
New Row Custom Query
triggerEmit new event when new rows are returned from a custom query that you provide. See the documentationv2.0.8
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,postgresql
- Primary app
- Google Calendar (google_calendar)
- Second app
- PostgreSQL (postgresql)
- Authentication
- OAuth + API key
- Available actions
- 26
- Available triggers
- 11