Create File Upload with Notion API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on

New Requests (Payload Only) from the HTTP / Webhook API

Next, do this

Create File Upload with the Notion 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 Notion 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 (Payload Only) trigger
1. Connect your HTTP / Webhook account
Configure the Create File Upload action
1. Connect your Notion account
2. Optional- Select a Mode
3. Optional- Configure Filename
4. Optional- Configure Content Type
5. Optional- Configure Number of Parts
6. Optional- Configure External URL
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 (Payload Only) on HTTP / Webhook

Description:Get a URL and emit the HTTP body as an event on every request

Version:0.1.1

Key:http-new-requests-payload-only

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
// Returns a 200 OK response, emits the HTTP payload as an event
export default {
  key: "http-new-requests-payload-only",
  name: "New Requests (Payload Only)",
  // eslint-disable-next-line
  description: "Get a URL and emit the HTTP body as an event on every request",
  version: "0.1.1",
  type: "source",
  props: {
    // eslint-disable-next-line
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    http,
  },
  async run(event) {
    const { body } = event;
    this.httpInterface.respond({
      status: 200,
      body,
    });
    // Emit the HTTP payload
    this.$emit({
      body,
    });
  },
};

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.
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#

Create File Upload on Notion

Description:Create a file upload. [See the documentation](https://developers.notion.com/reference/create-a-file-upload)

Version:0.0.1

Key:notion-create-file-upload

View on GitHub

Notion Overview#

Notion's API allows for the creation, reading, updating, and deleting of pages, databases, and their contents within Notion. Using Pipedream's platform, you can build workflows that connect Notion with various other services to automate tasks such as content management, task tracking, and data synchronization. With Pipedream's serverless execution, you can trigger these workflows on a schedule, or by external events from other services, without managing any infrastructure.

Action Code#

import notion from "../../notion.app.mjs";
import base from "../common/base-page-builder.mjs";

export default {
  ...base,
  key: "notion-create-file-upload",
  name: "Create File Upload",
  description: "Create a file upload. [See the documentation](https://developers.notion.com/reference/create-a-file-upload)",
  version: "0.0.1",
  type: "action",
  props: {
    notion,
    mode: {
      type: "string",
      label: "Mode",
      description: "How the file is being sent. Use `Multi Part` for files larger than 20MB. Use `External URL` for files that are temporarily hosted publicly elsewhere.",
      options: [
        {
          label: "Single Part",
          value: "single_part",
        },
        {
          label: "Multi Part",
          value: "multi_part",
        },
        {
          label: "External URL",
          value: "external_url",
        },
      ],
      optional: true,
    },
    filename: {
      type: "string",
      label: "Filename",
      description: "Name of the file to be created. Required when mode is multi_part or external_url. Otherwise optional, and used to override the filename. Must include an extension.",
      optional: true,
    },
    contentType: {
      type: "string",
      label: "Content Type",
      description: "MIME type of the file to be created. Recommended when sending the file in multiple parts. Must match the content type of the file that's sent, and the extension of the `filename` parameter if any.",
      optional: true,
    },
    numberOfParts: {
      type: "integer",
      label: "Number of Parts",
      description: "When mode is `Multi Part`, the number of parts you are uploading. Must be between 1 and 1,000. This must match the number of parts as well as the final part_number you send.",
      optional: true,
    },
    externalUrl: {
      type: "string",
      label: "External URL",
      description: "When mode is `External URL`, provide the HTTPS URL of a publicly accessible file to import into your workspace.",
      optional: true,
    },
  },
  async run({ $ }) {
    const response = await this.notion.createFileUpload({
      mode: this.mode,
      filename: this.filename,
      content_type: this.contentType,
      number_of_parts: this.numberOfParts,
      external_url: this.externalUrl,
    });

    $.export("$summary", `Successfully created file upload with ID ${response.id}`);
    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
Notion	`notion`	`app`	This component uses the Notion app.
Mode	`mode`	`string`	Select a value from the drop down menu:`{ "label": "Single Part", "value": "single_part" }{ "label": "Multi Part", "value": "multi_part" }{ "label": "External URL", "value": "external_url" }`
Filename	`filename`	`string`	Name of the file to be created. Required when mode is multi_part or external_url. Otherwise optional, and used to override the filename. Must include an extension.
Content Type	`contentType`	`string`	MIME type of the file to be created. Recommended when sending the file in multiple parts. Must match the content type of the file that's sent, and the extension of the `filename` parameter if any.
Number of Parts	`numberOfParts`	`integer`	When mode is `Multi Part`, the number of parts you are uploading. Must be between 1 and 1,000. This must match the number of parts as well as the final part_number you send.
External URL	`externalUrl`	`string`	When mode is `External URL`, provide the HTTPS URL of a publicly accessible file to import into your workspace.

Action Authentication#

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

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

About Notion#

Notion is a new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team.

More Ways to Connect Notion + HTTP / Webhook#

Other Popular Integrations#

Append Block to Parent with Notion API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Notion