MULTI-APP TOOLKIT
Build with Databricks + PagerDuty
- Multi-app
- One MCP session
- 73 actions
- 2 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Databricks and PagerDuty 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": "databricks,pagerduty",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Databricks and PagerDuty tools arrive
// together, each keyed by its own app's slug.
// e.g. run Cancel All Runs:
const result = await mcp.callTool({
name: "databricks-cancel-all-runs",
arguments: {
jobId: "Job",
allQueuedRuns: true,
},
})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 [databricksTools, pagerdutyTools] =
await Promise.all([
pd.components.list({ app: "databricks" }),
pd.components.list({ app: "pagerduty" }),
])
// 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=databricks" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=pagerduty" \
-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
Databricks
Connected account
PagerDuty
Connected account
TOOLS
Databricks tools
The Databricks tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 42
-
Cancel All Runs
actionCancel all active runs for a job. The runs are canceled asynchronously, so it doesn't prevent new runs from being started. See the documentationWritev0.0.5 -
Cancel Run
actionCancel a job run. The run is canceled asynchronously, so it may still be running when this request completes. See the documentationWritev0.0.6 -
Create Endpoint
actionCreate a new vector search endpoint. See the documentationWritev0.0.6 -
Create Job
actionCreate a job. See the documentationWritev0.0.4 -
Create SQL Warehouse
actionCreates a new SQL Warehouse in Databricks. See the documentationWritev0.0.7 -
Create Vector Search Index
actionCreates a new vector search index in Databricks. See the documentationWritev0.0.3 -
Delete Data from Vector Search Index
actionDeletes rows from a Direct Access vector index by primary-key values. See the documentationWritev0.0.5 -
Delete Endpoint
actionDelete a vector search endpoint. See the documentationWritev0.0.5
Triggers
No Databricks triggers are available yet.
TOOLS
PagerDuty tools
The PagerDuty tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 31
-
Acknowledge Incident
actionDeprecated — use Update Incident instead. Acknowledge an incident. See the documentationWritev0.0.5 -
Add Note to Incident
actionAdd a text note to an incident. Notes are visible in the incident timeline and useful for documenting investigation steps, resolution details, or handoff notes. Use List Incidents or Get Incident to find the incident ID. See the documentationWritev0.0.2 -
Create Incident
actionTrigger a new incident on a PagerDuty service. Use List Services to find a service ID and List Escalation Policies to find a policy ID. Use List Priorities to find priority IDs. SetincidentKeyto a stable value derived from the alert source (e.g. a hash of title + service ID) to prevent duplicate incidents on retry — PagerDuty deduplicates open incidents with the same key on the same service. See the documentationWritev0.0.2 -
Create Schedule Override
actionOverride a schedule layer to assign a specific user for a time window. Use List Schedules to find a schedule ID and List Users to find the user ID. Time params use ISO 8601 with explicit UTC offset, e.g.2026-06-02T15:00:00-07:00. Always include the UTC offset — do not assume UTC; using the wrong offset will place the override in the wrong time slot. See the documentationWritev0.0.2 -
Create Service
actionCreate a new PagerDuty service. A service represents a system or application that generates incidents. Use List Escalation Policies to find a valid escalation policy ID (required). SetautoResolveTimeoutto0to disable auto-resolve. SetacknowledgementTimeoutto0to disable re-triggering after acknowledgment. See the documentationWritev0.0.2 -
Find Oncall User
actionFind the user on call for a specific schedule. See the documentationRead-onlyv0.0.5 -
Get Event Orchestration for Service
actionGet the active event orchestration routing rules configured for a service. Event orchestration routes incoming events to the right responders based on conditions. Use List Services to discover service IDs. See the documentationRead-onlyv0.0.2 -
Get Incident
actionGet full details for a single incident by ID, including its current status, urgency, assignments, andhtml_url. Use List Incidents to find the incident ID. See the documentationRead-onlyv0.0.2
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
- databricks,pagerduty
- Primary app
- Databricks (databricks)
- Second app
- PagerDuty (pagerduty)
- Authentication
- API key + OAuth
- Available actions
- 73
- Available triggers
- 2