MULTI-APP TOOLKIT
Build with Datadog + Notion
- Multi-app
- One MCP session
- 38 actions
- 10 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Datadog and Notion 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": "datadog,notion",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Datadog and Notion tools arrive
// together, each keyed by its own app's slug.
// e.g. run Get Account Info:
const result = await mcp.callTool({
name: "datadog-get-account-info",
arguments: {},
})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 [datadogTools, notionTools] =
await Promise.all([
pd.components.list({ app: "datadog" }),
pd.components.list({ app: "notion" }),
])
// 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=datadog" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=notion" \
-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
Datadog
Connected account
Notion
Connected account
TOOLS
Datadog tools
The Datadog tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 13
-
Get Account Info
actionDetect the Datadog region for the connected account. Call this FIRST before any other Datadog tool if you do not already know the region. Returns the region domain (e.g.datadoghq.com) which must be passed as theregionparameter to Search Logs, Search Monitors, Get Metric Data, and all other Datadog tools. See the docsRead-onlyv1.0.2 -
Get Account Region
actionDetect the Datadog region for the connected account by validating the API key against each regional endpoint. Use this to discover the correct region before calling other Datadog actions. See the docsRead-onlyv0.0.1 -
Get Metric Data
actionQuery time-series metric data for analyzing trends and system performance. Query syntax:avg:system.cpu.user{*},sum:requests.count{env:prod} by {host},max:system.mem.used{service:web}. Bothfromandtoare POSIX timestamps in seconds. Use Search Metrics first to discover available metric names. Use Search Hosts to find valid host tags for scoping. After finding anomalies, use Search Logs to investigate related entries. See the docsRead-onlyv1.0.2 -
List Logs
actionGet a list of logs matching a filter query. Uses the GET endpoint with a higher rate limit (3600/hr vs 300/hr). See the docsRead-onlyv0.0.1 -
Post Metric Data
actionPost custom time-series metric data points to Datadog. Data appears in dashboards, monitors, and can be queried via Get Metric Data. Points: JSON object where keys are Unix timestamps (seconds) and values are numeric, e.g.{"1640995200": 1.0}. Use Search Metrics to verify a metric name exists, or post to a new name to create it. This is a WRITE operation that creates or appends data to a metric time series. See the docsWritev1.0.2 -
Search Dashboards
actionList and search Datadog dashboards. Returns dashboard IDs, titles, URLs, and metadata. Dashboard URL:https://app.{region}/dashboard/{id}where region comes from Get Account Info. Use alongside Search Services to find dashboards related to a specific service. See the docsRead-onlyv1.0.2 -
Search Events
actionSearch Datadog events: monitor state changes, deployment markers, error spikes, and infrastructure events. Filter bysources(e.g.nagios,docker),tags(e.g.env:prod,service:web), andpriority(normalorlow). Time range defaults to last 24h (POSIX timestamps in seconds). To investigate a monitor alert, use Search Monitors first, then search events for the relevant time range. Follow up with Search Logs for deeper investigation. See the docsRead-onlyv1.0.2 -
Search Hosts
actionSearch monitored infrastructure hosts. Filter by tag (env:production), name (host:web-01), or partial match. Sort bycpu,iowait,load,status, orapps. Host names from results can scope queries in Get Metric Data (e.g.avg:system.cpu.user{host:web-01}), filter logs in Search Logs (host:web-01), or filter metrics in Search Metrics. Max 1000 results. See the docsRead-onlyv1.0.2
TOOLS
Notion tools
The Notion tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 25
-
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 documentationWritev1.0.1 -
Complete File Upload
actionUse this action to finalize amode=multi_partfile upload after all of the parts have been sent successfully. See the documentationWritev0.0.11 -
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.26 -
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.1.1 -
Create Database
actionCreate a new Notion database (data source) as a subpage of a parent page, defining its column schema. Provide the parent page ID or URL (use Search to resolve a page name into an ID).propertiesis a JSON object of column-name → column type. Each value is a property schema object, or shorthand for simple types:{ "Name": "title", "Quantity": "number", "Category": { "select": { "options": [ { "name": "A" }, { "name": "B" } ] } } }. Exactly one column must be thetitletype. See the documentationWritev1.0.1 -
Create File Upload
actionCreate a file upload. See the documentationWritev0.0.11 -
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 documentationWritev1.0.1 -
Create Page from Data Source
actionCreate a page from a data source. See the documentationWritev2.0.3
Triggers top 4 of 9
-
New Comment Created
triggerEmit new event when a new comment is created in a page or block. See the documentationv0.0.9 -
New Data Source Created
triggerEmit new event when a data source is created. See the documentationv0.1.1 -
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 documentationv1.0.1 -
New or Updated Page in Data Source (By Timestamp)
triggerEmit new event when a page is created or updated in the selected data source. See the documentationv1.0.1
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
- datadog,notion
- Primary app
- Datadog (datadog)
- Second app
- Notion (notion)
- Authentication
- API key + OAuth
- Available actions
- 38
- Available triggers
- 10