Add Meeting Registrant with Zoom API on New Inbound Message Event from Trengo API

Pipedream makes it easy to connect APIs for Zoom, Trengo and 2,500+ other apps remarkably fast.

Trigger workflow on

New Inbound Message Event from the Trengo API

Next, do this

Add Meeting Registrant with the Zoom 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 Trengo trigger and Zoom action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Inbound Message Event trigger
1. Connect your Trengo account
Configure the Add Meeting Registrant action
1. Connect your Zoom account
2. Optional- Select a 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/Postal Code
11. Optional- Configure State/Province
12. Optional- Configure Phone
13. Optional- Configure Industry
14. Optional- Configure Organization
15. Optional- Configure Job Title
16. Optional- Configure Purchasing Time Frame
17. Optional- Configure Role in Purchase Process
18. Optional- Configure Number of Employees
19. Optional- Configure Comments
20. Optional- Configure Custom Questions
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 Inbound Message Event on Trengo

Description:Emit new events when an inbound message received. [See the docs here](https://developers.trengo.com/docs/webhooks)

Version:0.0.1

Key:trengo-new-inbound-message

View on GitHub

Trengo Overview#

The Trengo API provides programmatic access to Trengo's multi-channel communication platform, allowing for the streamlining of customer interactions across various channels such as email, SMS, social media, and chat. By leveraging the Trengo API on Pipedream, you can automate customer support workflows, sync communication data with CRM systems, and trigger alerts or actions based on specific customer queries or events.

Trigger Code#

import common from "../common/common.mjs";

export default {
  key: "trengo-new-inbound-message",
  name: "New Inbound Message Event",
  description: "Emit new events when an inbound message received. [See the docs here](https://developers.trengo.com/docs/webhooks)",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  ...common,
  methods: {
    ...common.methods,
    getMeta(event) {
      return {
        id: event?.body?.message_id ?
          parseInt(event?.body?.message_id) :
          Date.now(),
        ts: Date.now(),
        summary: `New inbound message event: ${event?.body?.message}`,
      };
    },
    getEvent() {
      return  "INBOUND";
    },
  },
};

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
Trengo	`app`	`app`	This component uses the Trengo app.
N/A	`http`	`$.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.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.

Trigger Authentication#

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

You need a personal access token to access the API and to perform actions on your behalf. Your personal access token needs to be send trough an Authorization Bearer request. See docs

About Trengo#

Customer service software

Action#

Add Meeting Registrant on Zoom

Description:Registers a participant for a meeting. [See the docs here](https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/meetingRegistrantCreate)

Version:0.3.3

Key:zoom-add-meeting-registrant

View on GitHub

Zoom Overview#

The Zoom API lets you tap into a rich set of functionalities to enhance the video conferencing experience within your own app or workflow. With the Zoom API on Pipedream, you can automatically create meetings, manage users, send meeting notifications, and more, orchestrating these actions within a broader automation. This allows for seamless integration with other services, enabling both data collection and action triggers based on Zoom events.

Pipedream workflows allow you to run any Node.js code that connects to the Zoom API. Just create a new workflow, then add prebuilt Zoom actions (create a meeting, send a chat message, etc.) or write your own code. These workflows can be triggered by HTTP requests, timers, email, or on any app-based event (new tweets, a Github PR, Zoom events, etc).

Action Code#

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

export default {
  key: "zoom-add-meeting-registrant",
  name: "Add Meeting Registrant",
  description: "Registers a participant for a meeting. [See the docs here](https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/meetingRegistrantCreate)",
  version: "0.3.3",
  type: "action",
  props: {
    app,
    meetingId: {
      propDefinition: [
        app,
        "meetingId",
      ],
    },
    occurrenceIds: {
      propDefinition: [
        app,
        "occurrenceIds",
      ],
    },
    email: {
      propDefinition: [
        app,
        "email",
      ],
    },
    firstName: {
      propDefinition: [
        app,
        "firstName",
      ],
    },
    lastName: {
      propDefinition: [
        app,
        "lastName",
      ],
    },
    address: {
      propDefinition: [
        app,
        "address",
      ],
    },
    city: {
      propDefinition: [
        app,
        "city",
      ],
    },
    country: {
      propDefinition: [
        app,
        "country",
      ],
    },
    zip: {
      propDefinition: [
        app,
        "zip",
      ],
    },
    state: {
      propDefinition: [
        app,
        "state",
      ],
    },
    phone: {
      propDefinition: [
        app,
        "phone",
      ],
    },
    industry: {
      propDefinition: [
        app,
        "industry",
      ],
    },
    org: {
      propDefinition: [
        app,
        "org",
      ],
    },
    jobTitle: {
      propDefinition: [
        app,
        "jobTitle",
      ],
    },
    purchasingTimeFrame: {
      propDefinition: [
        app,
        "purchasingTimeFrame",
      ],
    },
    roleInPurchaseProcess: {
      propDefinition: [
        app,
        "roleInPurchaseProcess",
      ],
    },
    noOfEmployees: {
      propDefinition: [
        app,
        "noOfEmployees",
      ],
    },
    comments: {
      propDefinition: [
        app,
        "comments",
      ],
    },
    customQuestions: {
      propDefinition: [
        app,
        "customQuestions",
      ],
    },
  },
  methods: {
    addMeetingRegistrant({
      meetingId, ...args
    } = {}) {
      return this.app.create({
        path: `/meetings/${meetingId}/registrants`,
        ...args,
      });
    },
  },
  async run({ $: step }) {
    const {
      meetingId,
      occurrenceIds,
      email,
      firstName,
      lastName,
      address,
      city,
      country,
      zip,
      state,
      phone,
      industry,
      org,
      jobTitle,
      purchasingTimeFrame,
      roleInPurchaseProcess,
      noOfEmployees,
      comments,
      customQuestions,
    } = this;

    const response = await this.addMeetingRegistrant({
      step,
      meetingId,
      params: {
        occurrence_ids: occurrenceIds,
      },
      data: {
        email,
        first_name: firstName,
        last_name: lastName,
        address,
        city,
        country,
        zip,
        state,
        phone,
        industry,
        org,
        job_title: jobTitle,
        purchasing_time_frame: purchasingTimeFrame,
        role_in_purchase_process: roleInPurchaseProcess,
        no_of_employees: noOfEmployees,
        comments,
        custom_questions: typeof(customQuestions) === "undefined"
          ? customQuestions
          : JSON.parse(customQuestions),
      },
    });

    step.export("$summary", `Successfully added registrant to meeting 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
Zoom	`app`	`app`	This component uses the Zoom app.
Meeting ID	`meetingId`	`integer`	Select a value from the drop down menu.
Occurrence IDs	`occurrenceIds`	`string`	Occurrence IDs. You can find these with the meeting get API. Multiple values separated by comma.
Email	`email`	`string`	A valid email address of the registrant.
First Name	`firstName`	`string`	Registrant's first name.
Last Name	`lastName`	`string`	Registrant's last name.
Address	`address`	`string`	Registrant's address.
City	`city`	`string`	Registrant's city.
Country	`country`	`string`	Registrant's country.
Zip/Postal Code	`zip`	`string`	Registrant's Zip/Postal code.
State/Province	`state`	`string`	Registrant's State/Province.
Phone	`phone`	`string`	Registrant's Phone number.
Industry	`industry`	`string`	Registrant's industry.
Organization	`org`	`string`	Registrant's Organization.
Job Title	`jobTitle`	`string`	Registrant's job title.
Purchasing Time Frame	`purchasingTimeFrame`	`string`	This field can be included to gauge interest of webinar attendees towards buying your product or service.
Role in Purchase Process	`roleInPurchaseProcess`	`string`	Role in Purchase Process.
Number of Employees	`noOfEmployees`	`string`	Number of Employees.
Comments	`comments`	`string`	A field that allows registrants to provide any questions or comments that they might have.
Custom Questions	`customQuestions`	`string`	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:

Add Meeting Registrant with Zoom API on New Inbound Message Event from Trengo API

Pipedream makes it easy to connect APIs for Zoom, Trengo and 2,500+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,500+apps by most popular

1
-
24
of
2,500+
apps by most popular