CONNECT APP
Build with Drata
Business Management
- API key
MCP
Give your agent Drata tools
Every Drata action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Drata account for each tool call — you store no tokens.
// 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": "drata",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Create Asset:
const result = await mcp.callTool({
name: "drata-create-asset",
arguments: {
name: "Name",
description: "Description",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"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": "drata",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Create Asset:
result = await session.call_tool("drata-create-asset", {
"name": "Name",
"description": "Description",
})API PROXY
Call the Drata API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Drata API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://public-api.drata.com/public/controls",
})
// Any allowed Drata endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://public-api.drata.com/public/controls
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9wdWJsaWMtYXBpLmRyYXRhLmNvbS9wdWJsaWMvY29udHJvbHM?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Drata actions from your backend
Connect a user's Drata account once, then run Create Asset on their behalf from your own code — TypeScript, Python, or plain HTTP.
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 result = await pd.actions.run({
id: "drata-create-asset",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
drata: { authProvisionId: "apn_xxxxxxx" },
name: "Name",
description: "Description",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="drata-create-asset",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"drata": {"authProvisionId": "apn_xxxxxxx"},
"name": "Name",
"description": "Description",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "drata-create-asset",
"configured_props": {
"drata": { "authProvisionId": "apn_xxxxxxx" },
"name": "Name",
"description": "Description"
}
}'TOOLS
Drata actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Create Asset
actionCreate an asset. See the documentation.Writev0.0.4 -
Create Control
actionCreate a new Control. See the documentation.Writev0.0.4 -
Create Vendor
actionCreate a new Vendor. See the documentation.Writev0.0.4 -
Find Controls
actionFind Controls. See the documentation.Read-onlyv0.0.4 -
Find Personnel
actionFind Personnel. See the documentation.Read-onlyv0.0.4 -
Find Vendors
actionFind Vendors. See the documentation.Read-onlyv0.0.4 -
List Control ID Options
actionRetrieves available options for the Control ID field.Read-onlyv0.0.1 -
List Device ID Options
actionRetrieves available options for the Device ID field.Read-onlyv0.0.1 -
List Vendor ID Options
actionRetrieves available options for the Vendor ID field.Read-onlyv0.0.1 -
List Workspace ID Options
actionRetrieves available options for the Workspace ID field.Read-onlyv0.0.1 -
Update Vendor
actionUpdate a Vendor. See the documentation.Writev0.0.4 -
Upload Background Check
actionUpload background check for a personnel. See the documentation.Writev0.0.4 -
Upload Device Compliance Document
actionUpload a device compliance document. See the documentation.Writev0.0.4 -
Upload User Compliance Document
actionUpload a user compliance document. See the documentation.Writev0.0.4
-
Employee Terminated
triggerEmit a new event when an employee is terminated. See the documentation.v0.0.3 -
Failed Monitor
triggerEmit a new event whenever a monitor fails. See the documentation.v0.0.2 -
New Asset Added
triggerEmit a new event for every new asset. See the documentation.v0.0.3 -
New Control Added
triggerEmit a new event for every new control. See the documentation.v0.0.3 -
New Evidence for Control Added
triggerEmit a new event for every new evidence for a control. See the documentation.v0.0.3 -
New Personnel Added
triggerEmit a new event for every new personnel. See the documentation.v0.0.3 -
New Vendor Added
triggerEmit a new event for every new vendor. See the documentation.v0.0.3 -
Vendor Updated
triggerEmit a new event when a vendor is updated. See the documentation.v0.0.3
MULTI-APP
Use Drata with other popular apps
Most products don't stop at one integration. Pair Drata with the other apps your users rely on, and ship use cases that span both.
- App slug
- drata
- Authentication
- API key
- Categories
- Business Management
- Actions
- 14
- Triggers
- 8
- API proxy
- Available