MULTI-APP TOOLKIT
Build with Datadog + HubSpot
- Multi-app
- One MCP session
- 121 actions
- 28 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Datadog 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": "datadog,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: Datadog and HubSpot 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, hubspotTools] =
await Promise.all([
pd.components.list({ app: "datadog" }),
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=datadog" \
-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
Datadog
Connected account
HubSpot
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
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
- datadog,hubspot
- Primary app
- Datadog (datadog)
- Second app
- HubSpot (hubspot)
- Authentication
- API key + OAuth
- Available actions
- 121
- Available triggers
- 28