Upload Device Compliance Document with Drata API on New Requests from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Drata, HTTP / Webhook and 2,400+ other apps remarkably fast.

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Upload Device Compliance Document with the Drata API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a HTTP / Webhook trigger and Drata action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Requests trigger
1. Optional- Configure Body Only
2. Optional- Configure Response Status Code
3. Optional- Configure Response Content-Type
4. Optional- Configure Response Body
5. Connect your HTTP / Webhook account
Configure the Upload Device Compliance Document action
1. Connect your Drata account
2. Select a Device ID
3. Select a Document Type
4. Configure URL
5. Configure Filename
6. Select a Extension
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Requests on HTTP / Webhook

Description:Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

Version:0.1.1

Key:http-new-requests

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Trigger Code#

import http from "../../http.app.mjs";

// Core HTTP component
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
N/A	`httpInterface`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
Body Only	`emitBodyOnly`	`boolean`	This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.
Response Status Code	`resStatusCode`	`string`	The status code to return in the HTTP response
Response Content-Type	`resContentType`	`string`	The `Content-Type` of the body returned in the HTTP response
Response Body	`resBody`	`string`	The body to return in the HTTP response
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

Action#

Upload Device Compliance Document on Drata

Description:Upload a device compliance document. [See the documentation](https://developers.drata.com/docs/openapi/reference/operation/DevicePublicController_uploadDocumentForDevice/).

Version:0.0.3

Key:drata-upload-device-compliance-document

View on GitHub

Drata Overview#

Drata is a compliance automation platform. Drata’s platform is built by compliance and security experts so you don’t have to be one. With 75+ native integrations, you can easily connect your tech stack and automate evidence collection and testing.

Pipedream customers get 25% off Drata, with implementation fees waived. Visit https://drata.com/partner/pipedream for more information.

Action Code#

import drata from "../../drata.app.mjs";
import { axios } from "@pipedream/platform";

const docsLink = "https://developers.drata.com/docs/openapi/reference/operation/DevicePublicController_uploadDocumentForDevice/";

export default {
  key: "drata-upload-device-compliance-document",
  name: "Upload Device Compliance Document",
  description: `Upload a device compliance document. [See the documentation](${docsLink}).`,
  version: "0.0.3",
  type: "action",
  props: {
    drata,
    deviceId: {
      propDefinition: [
        drata,
        "deviceId",
      ],
    },
    documentType: {
      type: "string",
      label: "Document Type",
      description: "The user document type",
      options: [
        "PASSWORD_MANAGER_EVIDENCE",
        "AUTO_UPDATES_EVIDENCE",
        "HARD_DRIVE_ENCRYPTION_EVIDENCE",
        "ANTIVIRUS_EVIDENCE",
        "LOCK_SCREEN_EVIDENCE",
      ],
    },
    url: {
      type: "string",
      label: "URL",
      description: "The URL of the document file.",
    },
    filename: {
      type: "string",
      label: "Filename",
      description: "The filename of the document file.",
    },
    extension: {
      type: "string",
      label: "Extension",
      description: "The extension of the document file.",
      withLabel: true,
      options: [
        {
          label: ".pdf",
          value: "application/pdf",
        },
        {
          label: ".doc",
          value: "application/msword",
        },
        {
          label: ".docx",
          value: "application/vnd.openxmlformats-officedocument.wordprocessingml.document",
        },
        {
          label: ".xls",
          value: "application/vnd.ms-excel",
        },
        {
          label: ".xlsx",
          value: "officedocument.spreadsheetml.sheet",
        },
        {
          label: ".png",
          value: "image/png",
        },
        {
          label: ".jpeg",
          value: "image/jpeg",
        },
      ],
    },
  },
  methods: {
    async downloadFile({ $ }) {
      const file = await axios($, {
        url: this.url,
        responseType: "arraybuffer",
      });
      return file.toString("base64");
    },
    buildFormData(fileBase64) {
      const form = new URLSearchParams();
      form.append("type", this.documentType);
      form.append("base64File", JSON.stringify({
        base64String: `data:${this.extension.value};base64,${fileBase64}`,
        filename: this.filename + this.extension.label,
      }));
      return form;
    },
  },
  async run({ $ }) {
    const fileBase64 = await this.downloadFile({
      $,
    });
    const data = this.buildFormData(fileBase64);

    const response = await this.drata.uploadDeviceComplianceDocument({
      deviceId: this.deviceId,
      data,
    });

    $.export("$summary", "Succesfully uploaded compliance document");

    return response;
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Drata	`drata`	`app`	This component uses the Drata app.
Device ID	`deviceId`	`string`	Select a value from the drop down menu.
Document Type	`documentType`	`string`	Select a value from the drop down menu:`PASSWORD_MANAGER_EVIDENCEAUTO_UPDATES_EVIDENCEHARD_DRIVE_ENCRYPTION_EVIDENCEANTIVIRUS_EVIDENCELOCK_SCREEN_EVIDENCE`
URL	`url`	`string`	The URL of the document file.
Filename	`filename`	`string`	The filename of the document file.
Extension	`extension`	`string`	Select a value from the drop down menu:`{ "label": ".pdf", "value": "application/pdf" }{ "label": ".doc", "value": "application/msword" }{ "label": ".docx", "value": "application/vnd.openxmlformats-officedocument.wordprocessingml.document" }{ "label": ".xls", "value": "application/vnd.ms-excel" }{ "label": ".xlsx", "value": "officedocument.spreadsheetml.sheet" }{ "label": ".png", "value": "image/png" }{ "label": ".jpeg", "value": "image/jpeg" }`

Action Authentication#

Drata uses API keys for authentication. When you connect your Drata account, Pipedream securely stores the keys so you can easily authenticate to Drata APIs in both code and no-code steps.

Make sure you're logged into the Drata UI, then see these docs to create a Drata API key. Enter it below.

About Drata#

Drata automates your compliance journey from start to audit-ready and beyond and provides support from the security and compliance experts who built it.

More Ways to Connect Drata + HTTP / Webhook#

Other Popular Integrations#

Create Asset with Drata API on New Requests from HTTP / Webhook API

HTTP / Webhook + Drata