← HTTP / Webhook + Vercel (OAuth) integrations

Create Deployment with Vercel (OAuth) API on New Requests (Payload Only) from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Vercel (OAuth), HTTP / Webhook and 1000+ other apps remarkably fast.

Trigger workflow on
New Requests (Payload Only) from the HTTP / Webhook API
Next, do this
Create Deployment with the Vercel (OAuth) API
No credit card required
Into to Pipedream
Watch us build a workflow
Watch us build a workflow
7 min
Watch now ➜
Trusted by 250,000+ developers from startups to Fortune 500 companies:
Trusted by 250,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

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

  1. Select this integration
  2. Configure the New Requests (Payload Only) trigger
    1. Connect your HTTP / Webhook account
  3. Configure the Create Deployment action
    1. Connect your Vercel (OAuth) account
    2. Configure Name
    3. Optional- Select a Project
    4. Configure Git Source Repository Id
    5. Configure Branch
    6. Optional- Select a Team
    7. Optional- Configure Public
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. Turn on the trigger

Details

This integration uses pre-built, open source 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

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

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.
LabelPropTypeDescription
N/AhttpInterface$.interface.httpThis 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 / WebhookhttpappThis 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

Description:Create a new deployment from a GitHub repository. [See the docs](https://vercel.com/docs/rest-api#endpoints/deployments/create-a-new-deployment)
Version:0.0.2
Key:vercel-create-deployment

Action Code

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

export default {
  key: "vercel-create-deployment",
  name: "Create Deployment",
  description: "Create a new deployment from a GitHub repository. [See the docs](https://vercel.com/docs/rest-api#endpoints/deployments/create-a-new-deployment)",
  version: "0.0.2",
  type: "action",
  props: {
    vercel,
    name: {
      type: "string",
      label: "Name",
      description: "A string with the project name used in the deployment URL",
    },
    project: {
      propDefinition: [
        vercel,
        "project",
      ],
      description: "The target project identifier in which the deployment will be created. When defined, this parameter overrides name",
    },
    repoId: {
      type: "string",
      label: "Git Source Repository Id",
      description: "Id of the source repository",
    },
    branch: {
      type: "string",
      label: "Branch",
      description: "Branch of repository to deploy to",
      default: "main",
    },
    team: {
      propDefinition: [
        vercel,
        "team",
      ],
    },
    public: {
      type: "boolean",
      label: "Public",
      description: "Whether a deployment's source and logs are available publicly",
      optional: true,
    },
  },
  async run({ $ }) {
    const data = {
      name: this.name,
      project: this.project,
      teamId: this.team,
      public: this.public,
      gitSource: {
        type: "github",
        repoId: this.repoId,
        ref: this.branch,
      },
    };
    const res = await this.vercel.createDeployment(data, $);
    $.export("$summary", "Successfully created new deployment");
    return res;
  },
};

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.

LabelPropTypeDescription
Vercel (OAuth)vercelappThis component uses the Vercel (OAuth) app.
Namenamestring

A string with the project name used in the deployment URL

ProjectprojectstringSelect a value from the drop down menu.
Git Source Repository IdrepoIdstring

Id of the source repository

Branchbranchstring

Branch of repository to deploy to

TeamteamstringSelect a value from the drop down menu.
Publicpublicboolean

Whether a deployment's source and logs are available publicly

Action Authentication

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

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

About Vercel (OAuth)

The easiest way to deploy websites

More Ways to Connect Vercel (OAuth) + HTTP / Webhook

Send any HTTP Request with HTTP / Webhook API on New Deployment from Vercel API
Vercel (OAuth) + HTTP / Webhook
 
Try it
Send GET Request with HTTP / Webhook API on New Deployment from Vercel API
Vercel (OAuth) + HTTP / Webhook
 
Try it
Send POST Request with HTTP / Webhook API on New Deployment from Vercel API
Vercel (OAuth) + HTTP / Webhook
 
Try it
Send PUT Request with HTTP / Webhook API on New Deployment from Vercel API
Vercel (OAuth) + HTTP / Webhook
 
Try it
Return HTTP Response with HTTP / Webhook API on New Deployment from Vercel API
Vercel (OAuth) + HTTP / Webhook
 
Try it
New Requests from the HTTP / Webhook API

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.

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

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

 
Try it
New event when the content of the URL changes. from the HTTP / Webhook API

Emit new event when the content of the URL changes.

 
Try it
New Deployment from the Vercel (OAuth) API

Emit new event when a deployment is created

 
Try it
Send any HTTP Request with the HTTP / Webhook API

Send an HTTP request using any method and URL. Optionally configure query string parameters, headers, and basic auth.

 
Try it
Send GET Request with the HTTP / Webhook API

Send an HTTP GET request to any URL. Optionally configure query string parameters, headers and basic auth.

 
Try it
Send POST Request with the HTTP / Webhook API

Send an HTTP POST request to any URL. Optionally configure query string parameters, headers and basic auth.

 
Try it
Send PUT Request with the HTTP / Webhook API

Send an HTTP PUT request to any URL. Optionally configure query string parameters, headers and basic auth.

 
Try it
Return HTTP Response with the HTTP / Webhook API

Use with an HTTP Source that uses Return a custom response from your workflow as its HTTP Response

 
Try it