Select Files with Microsoft Sharepoint API on New Requests from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Microsoft Sharepoint, HTTP / Webhook and 3,000+ other apps remarkably fast.

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Select Files with the Microsoft Sharepoint 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 Microsoft Sharepoint 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
6. Optional- Configure Summary
Configure the Select Files action
1. Connect your Microsoft Sharepoint account
2. Select a Site
3. Select a Drive ID
4. Optional- Select a Folder
5. Select one or more Files or Folders
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.2

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.2",
  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,
    summary: {
      propDefinition: [
        http,
        "summary",
      ],
    },
  },
  async run(event) {
    const summary = this.summary
      ? this.http.interpolateSummary(this.summary, event)
      : `${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.
Summary	`summary`	`string`	An optional summary. This will be emitted as the `summary` metadata for the event. Use dot notation to reference nested values. Example: `New item with ID: ${body.id}` or `User: ${body.user.name}`

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#

Select Files on Microsoft Sharepoint

Description:A file picker action that allows browsing and selecting one or more files from SharePoint. Returns the selected files' metadata including pre-authenticated download URLs. [See the documentation](https://learn.microsoft.com/en-us/graph/api/driveitem-get)

Version:0.0.1

Key:sharepoint-select-files

View on GitHub

Microsoft Sharepoint Overview#

The Microsoft SharePoint Online API opens up a world of possibilities for integrating your SharePoint content with other services and automating tasks. With Pipedream, you can harness this API to create powerful workflows that trigger on events in SharePoint, manipulate data, and connect with countless other apps. Create custom automations for document management, team notifications, content moderation, and more, without the need to manage infrastructure.

Action Code#

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

export default {
  key: "sharepoint-select-files",
  name: "Select Files",
  description: "A file picker action that allows browsing and selecting one or more files from SharePoint. Returns the selected files' metadata including pre-authenticated download URLs. [See the documentation](https://learn.microsoft.com/en-us/graph/api/driveitem-get)",
  version: "0.0.1",
  type: "action",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: true,
  },
  props: {
    sharepoint,
    siteId: {
      propDefinition: [
        sharepoint,
        "siteId",
      ],
      withLabel: true,
      reloadProps: true,
    },
    driveId: {
      propDefinition: [
        sharepoint,
        "driveId",
        (c) => ({
          siteId: c.siteId?.__lv?.value || c.siteId,
        }),
      ],
      withLabel: true,
      reloadProps: true,
    },
    folderId: {
      propDefinition: [
        sharepoint,
        "folderId",
        (c) => ({
          siteId: c.siteId?.__lv?.value || c.siteId,
          driveId: c.driveId?.__lv?.value || c.driveId,
        }),
      ],
      label: "Folder",
      description: "The folder to browse. Leave empty to browse the root of the drive.",
      optional: true,
      withLabel: true,
      reloadProps: true,
    },
    fileOrFolderIds: {
      propDefinition: [
        sharepoint,
        "fileOrFolderId",
        (c) => ({
          siteId: c.siteId?.__lv?.value || c.siteId,
          driveId: c.driveId?.__lv?.value || c.driveId,
          folderId: c.folderId?.__lv?.value || c.folderId,
        }),
      ],
      type: "string[]",
      label: "Files or Folders",
      description: "Select one or more files, or select a folder and click 'Refresh Fields' to browse into it",
      withLabel: true,
    },
  },
  methods: {
    resolveValue(prop) {
      if (!prop) return null;
      if (typeof prop === "object" && prop.__lv) {
        return prop.__lv.value;
      }
      return prop;
    },
    parseFileOrFolder(value) {
      if (!value) return null;
      const resolved = this.resolveValue(value);
      try {
        return JSON.parse(resolved);
      } catch {
        return {
          id: resolved,
          isFolder: false,
        };
      }
    },
    parseFileOrFolderList(values) {
      if (!values) return [];
      const list = Array.isArray(values)
        ? values
        : [
          values,
        ];
      return list.map((v) => this.parseFileOrFolder(v)).filter(Boolean);
    },
  },
  async run({ $ }) {
    const selections = this.parseFileOrFolderList(this.fileOrFolderIds);

    if (selections.length === 0) {
      throw new Error("Please select at least one file or folder");
    }

    const siteId = this.resolveValue(this.siteId);
    const driveId = this.resolveValue(this.driveId);

    // Separate files and folders
    const folders = selections.filter((s) => s.isFolder);
    const files = selections.filter((s) => !s.isFolder);

    // If only folders selected, return folder info
    if (files.length === 0 && folders.length > 0) {
      const folderNames = folders.map((f) => f.name).join(", ");
      $.export("$summary", `Selected ${folders.length} folder(s): ${folderNames}. Set one as the Folder ID and refresh to browse its contents.`);
      return {
        type: "folders",
        folders: folders.map((f) => ({
          id: f.id,
          name: f.name,
        })),
        message: "To browse a folder, set it as the folderId and reload props",
      };
    }

    // Fetch metadata for all selected files in parallel, handling individual failures
    const settledResults = await Promise.allSettled(
      files.map(async (selected) => {
        const file = await this.sharepoint.getDriveItem({
          $,
          siteId,
          driveId,
          fileId: selected.id,
        });

        const downloadUrl = file["@microsoft.graph.downloadUrl"];

        return {
          ...file,
          downloadUrl,
          _meta: {
            siteId,
            driveId,
            fileId: selected.id,
          },
        };
      }),
    );

    // Separate successful and failed results
    const fileResults = [];
    const errors = [];

    settledResults.forEach((result, index) => {
      if (result.status === "fulfilled") {
        fileResults.push(result.value);
      } else {
        const selected = files[index];
        const errorMessage = result.reason?.message || String(result.reason);
        console.error(`Failed to fetch file ${selected.id} (${selected.name}): ${errorMessage}`);
        errors.push({
          fileId: selected.id,
          fileName: selected.name,
          error: errorMessage,
        });
      }
    });

    // If all files failed, throw an error
    if (fileResults.length === 0 && errors.length > 0) {
      throw new Error(`Failed to fetch all selected files: ${errors.map((e) => e.fileName).join(", ")}`);
    }

    // If single file, return it directly for backwards compatibility
    if (fileResults.length === 1 && folders.length === 0 && errors.length === 0) {
      $.export("$summary", `Selected file: ${fileResults[0].name}`);
      return fileResults[0];
    }

    // Multiple files: return as array
    const fileNames = fileResults.map((f) => f.name).join(", ");
    const summaryParts = [
      `Selected ${fileResults.length} file(s): ${fileNames}`,
    ];
    if (errors.length > 0) {
      summaryParts.push(`Failed to fetch ${errors.length} file(s): ${errors.map((e) => e.fileName).join(", ")}`);
    }
    $.export("$summary", summaryParts.join(". "));

    return {
      files: fileResults,
      ...(errors.length > 0 && {
        errors,
      }),
      ...(folders.length > 0 && {
        folders: folders.map((f) => ({
          id: f.id,
          name: f.name,
        })),
      }),
    };
  },
};

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
Microsoft Sharepoint	`sharepoint`	`app`	This component uses the Microsoft Sharepoint app.
Site	`siteId`	`string`	Select a value from the drop down menu.
Drive ID	`driveId`	`string`	Select a value from the drop down menu.
Folder	`folderId`	`string`	Select a value from the drop down menu.
Files or Folders	`fileOrFolderIds`	`string[]`	Select a value from the drop down menu.

Action Authentication#

Microsoft Sharepoint uses OAuth authentication. When you connect your Microsoft Sharepoint account, Pipedream will open a popup window where you can sign into Microsoft Sharepoint and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Microsoft Sharepoint API.

Pipedream requests the following authorization scopes when you connect your account:

offline_accessemailopenidSites.Manage.AllSites.Read.AllSites.ReadWrite.AllUser.Read.AllGroup.Read.AllSites.FullControl.All

About Microsoft Sharepoint#

Share and manage content, knowledge, and applications to empower teamwork, quickly find information, and seamlessly collaborate across the organization.

More Ways to Connect Microsoft Sharepoint + HTTP / Webhook#

Other Popular Integrations#

Create Item with Microsoft Sharepoint API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Microsoft Sharepoint