← Trengo + Zoom integrations

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 1000+ 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
Into to Pipedream
Watch us build a workflow
Watch us build a workflow
7 min
Watch now ➜

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

Adyen logo
Brex logo
Carta logo
Checkr logo
Chameleon logo
DevRev logo
LinkedIn logo
Netflix logo
New Relic logo
OnDeck logo
Replicated logo
Scale AI logo
Teamwork logo
Warner Bros. logo
Xendit logo

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.

  1. Select this integration
  2. Configure the New Inbound Message Event trigger
    1. Connect your Trengo account
  3. 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
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. 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

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

Trengo Overview

You can build amazing customer service experiences by using the Trengo API.
It's the platform to help teams work better together, and offers features to
optimize your customer conversation. For example, you can use Trengo to:

  • Improve customer service by leveraging automation for fast and personalized
    responses
  • Increase efficiency by optimizing operational workflows
  • Gather insights from customer conversations to improve customer service
  • Automate conversations like welcome messages and error notifications
  • Filter and manage incoming conversations to make sure the right person
    provides the right answers

These are just some of the examples of what you can do with the Trengo API.
With the Trengo platform, you can make sure your customer conversations deliver
the best possible outcomes, consistently.

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.
LabelPropTypeDescription
TrengoappappThis component uses the Trengo app.
N/Ahttp$.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.
N/Adb$.service.dbThis 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

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.0
Key:zoom-add-meeting-registrant

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.0",
  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.

LabelPropTypeDescription
ZoomappappThis component uses the Zoom app.
Meeting IDmeetingIdintegerSelect a value from the drop down menu.
Occurrence IDsoccurrenceIdsstring

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 NamefirstNamestring

Registrant's first name.

Last NamelastNamestring

Registrant's last name.

Addressaddressstring

Registrant's address.

Citycitystring

Registrant's city.

Countrycountrystring

Registrant's country.

Zip/Postal Codezipstring

Registrant's Zip/Postal code.

State/Provincestatestring

Registrant's State/Province.

Phonephonestring

Registrant's Phone number.

Industryindustrystring

Registrant's industry.

Organizationorgstring

Registrant's Organization.

Job TitlejobTitlestring

Registrant's job title.

Purchasing Time FramepurchasingTimeFramestring

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

Role in Purchase ProcessroleInPurchaseProcessstring

Role in Purchase Process.

Number of EmployeesnoOfEmployeesstring

Number of Employees.

Commentscommentsstring

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

Custom QuestionscustomQuestionsstring

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 + Trengo

Add Webinar Registrant with Zoom API on New Inbound Message Event from Trengo API
Trengo + Zoom
 
Try it
Create Meeting with Zoom API on New Inbound Message Event from Trengo API
Trengo + Zoom
 
Try it
Create User with Zoom API on New Inbound Message Event from Trengo API
Trengo + Zoom
 
Try it
Delete User with Zoom API on New Inbound Message Event from Trengo API
Trengo + Zoom
 
Try it
Get Meeting Details with Zoom API on New Inbound Message Event from Trengo API
Trengo + Zoom
 
Try it
New Inbound Message Event from the Trengo API

Emit new events when an inbound message received. See the docs here

 
Try it
New Internal Note Event from the Trengo API

Emit new events when a internal note added. See the docs here

 
Try it
New Outbound Message Event from the Trengo API

Emit new events when an outbound message sent. See the docs here

 
Try it
New Phone Call Ended Event from the Trengo API

Emit new events when an phone call ended. See the docs here

 
Try it
New Phone Call Missed Event from the Trengo API

Emit new events when an phone call missed. See the docs here

 
Try it
Create Contact with the Trengo API

Creates a contact. If a contact with given identifier already exists, returns it. See the docs

 
Try it
Find Contacts with the Trengo API

Finds contacts with the given term. See the docs

 
Try it
Log A Voice Call with the Trengo API

Logs a phone call from external VOIP applications, See the docs

 
Try it
Send A Message with the Trengo API

This action can be used to easily send a message or an email without having to think about contacts or tickets, See the docs

 
Try it
Send A Team Chat Message with the Trengo API

Send a message as a bot in the Team Chat, See the docs

 
Try it