← HTTP / Webhook + Zoom integrations

Add Meeting Registrant with Zoom API on New Requests from HTTP / Webhook API

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

Trigger workflow on
New Requests from the HTTP / Webhook API
Next, do this
Add Meeting Registrant with the Zoom 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 Zoom 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 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
  3. Configure the Add Meeting Registrant action
    1. Connect your Zoom account
    2. Configure meeting_id
    3. Optional- Configure occurrence_ids
    4. Configure email
    5. Configure first_name
    6. Configure last_name
    7. Optional- Configure address
    8. Optional- Configure city
    9. Optional- Configure country
    10. Optional- Configure zip
    11. Optional- Configure state
    12. Optional- Configure phone
    13. Optional- Configure industry
    14. Optional- Configure org
    15. Optional- Configure job_title
    16. Optional- Configure purchasing_time_frame
    17. Optional- Configure role_in_purchase_process
    18. Optional- Configure no_of_employees
    19. Optional- Configure comments
    20. Optional- Configure custom_questions
  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 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

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.
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.
Body OnlyemitBodyOnlyboolean

This source emits an event representing the full HTTP request by default. Select true to emit the body only.

Response Status CoderesStatusCodestring

The status code to return in the HTTP response

Response Content-TyperesContentTypestring

The Content-Type of the body returned in the HTTP response

Response BodyresBodystring

The body to return in the HTTP response

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:Registers a participant for a meeting.
Version:0.2.1
Key:zoom-add-meeting-registrant

Action Code

// legacy_hash_id: a_zNiweO
import { axios } from "@pipedream/platform";

export default {
  key: "zoom-add-meeting-registrant",
  name: "Add Meeting Registrant",
  description: "Registers a participant for a meeting.",
  version: "0.2.1",
  type: "action",
  props: {
    zoom: {
      type: "app",
      app: "zoom",
    },
    meeting_id: {
      type: "string",
      description: "The meeting ID.",
    },
    occurrence_ids: {
      type: "string",
      description: "Occurrence IDs. You can find these with the meeting get API. Multiple values separated by comma.",
      optional: true,
    },
    email: {
      type: "string",
      description: "A valid email address of the registrant.",
    },
    first_name: {
      type: "string",
      description: "Registrant's first name.",
    },
    last_name: {
      type: "string",
      description: "Registrant's last name.",
    },
    address: {
      type: "string",
      description: "Registrant's address.",
      optional: true,
    },
    city: {
      type: "string",
      description: "Registrant's city.",
      optional: true,
    },
    country: {
      type: "string",
      description: "Registrant's country.",
      optional: true,
    },
    zip: {
      type: "string",
      description: "Registrant's Zip/Postal code.",
      optional: true,
    },
    state: {
      type: "string",
      description: "Registrant's State/Province.",
      optional: true,
    },
    phone: {
      type: "string",
      description: "Registrant's Phone number.",
      optional: true,
    },
    industry: {
      type: "string",
      description: "Registrant's industry.",
      optional: true,
    },
    org: {
      type: "string",
      description: "Registrant's Organization.",
      optional: true,
    },
    job_title: {
      type: "string",
      description: "Registrant's job title.",
      optional: true,
    },
    purchasing_time_frame: {
      type: "string",
      description: "This field can be included to gauge interest of webinar attendees towards buying your product or service.",
      optional: true,
    },
    role_in_purchase_process: {
      type: "string",
      description: "Role in Purchase Process.",
      optional: true,
    },
    no_of_employees: {
      type: "string",
      description: "Number of Employees.",
      optional: true,
    },
    comments: {
      type: "string",
      description: "A field that allows registrants to provide any questions or comments that they might have.",
      optional: true,
    },
    custom_questions: {
      type: "any",
      description: "Custom questions.",
      optional: true,
    },
  },
  async run({ $ }) {
  //See the API docs here: https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingregistrantcreate
    const config = {
      method: "post",
      url: `https://api.zoom.us/v2/meetings/${this.meeting_id}/registrants`,
      params: {
        occurrence_ids: this.occurrence_ids,
      },
      data: {
        email: this.email,
        first_name: this.first_name,
        last_name: this.last_name,
        address: this.address,
        city: this.city,
        country: this.country,
        zip: this.zip,
        state: this.state,
        phone: this.phone,
        industry: this.industry,
        org: this.org,
        job_title: this.job_title,
        purchasing_time_frame: this.purchasing_time_frame,
        role_in_purchase_process: this.role_in_purchase_process,
        no_of_employees: this.no_of_employees,
        comments: this.comments,
        custom_questions: typeof this.custom_questions == "undefined"
          ? this.custom_questions
          : JSON.parse(this.custom_questions),
      },
      headers: {
        "Authorization": `Bearer ${this.zoom.$auth.oauth_access_token}`,
        "Content-Type": "application/json",
      },
    };
    return await axios($, config);
  },
};

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
ZoomzoomappThis component uses the Zoom app.
meeting_idmeeting_idstring

The meeting ID.

occurrence_idsoccurrence_idsstring

Occurrence IDs. You can find these with the meeting get API. Multiple values separated by comma.

emailemailstring

A valid email address of the registrant.

first_namefirst_namestring

Registrant's first name.

last_namelast_namestring

Registrant's last name.

addressaddressstring

Registrant's address.

citycitystring

Registrant's city.

countrycountrystring

Registrant's country.

zipzipstring

Registrant's Zip/Postal code.

statestatestring

Registrant's State/Province.

phonephonestring

Registrant's Phone number.

industryindustrystring

Registrant's industry.

orgorgstring

Registrant's Organization.

job_titlejob_titlestring

Registrant's job title.

purchasing_time_framepurchasing_time_framestring

This field can be included to gauge interest of webinar attendees towards buying your product or service.

role_in_purchase_processrole_in_purchase_processstring

Role in Purchase Process.

no_of_employeesno_of_employeesstring

Number of Employees.

commentscommentsstring

A field that allows registrants to provide any questions or comments that they might have.

custom_questionscustom_questionsany

Custom questions.

Action Authentication

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

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

About Zoom

Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webinars.

More Ways to Connect Zoom + HTTP / Webhook