Delete User with Zoom API on New Inbound Message Event from Trengo API

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

Trigger workflow on

New Inbound Message Event from the Trengo API

Next, do this

Delete User with the Zoom API

No credit card required

▶

Watch us build a workflow

7 min

Watch now ➜

Trusted by 500,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 Delete User action
1. Connect your Zoom account
2. Configure user_id
3. Optional- Select a action
4. Optional- Configure transfer_email
5. Optional- Configure transfer_meeting
6. Optional- Configure transfer_webinar
7. Optional- Configure transfer_recording
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#

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.

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#

Delete User on Zoom

Description:Disassociates (unlinks) a user from the associated account or permanently deletes a user.

Version:0.2.1

Key:zoom-delete-user

View on GitHub

Zoom Overview#

Connecting Zoom to any app using Pipedream

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

Getting Started

First, sign up for Pipedream at https://pipedream.com.
Visit https://pipedream.com/accounts.
Click the button labeled Click Here to Connect an App.
Search for "Zoom" and select either Zoom or Zoom Admin (see the differences below):

This will open up a new window prompting you to authorize Pipedream's access to your Zoom account. Once you authorize access, you should see your Zoom account listed among your apps.

Create a new workflow, add a new step, search for "Zoom" or "Zoom Admin". Once you've selected either app, you can choose to either "Run Node.js code" or select one of the prebuilt actions for performing common API operations.
At this stage, you'll be asked to link the Zoom account you connected above, authorizing the request to the Zoom API with your credentials:

Zoom vs Zoom Admin app

Zoom users can be classified into two groups: non-admins and admins. Admins have account-level permissions that users do not, and Zoom has corresponding admin-level scopes that aren't relevant for normal users. Therefore, Pipedream exposes two apps — Zoom and Zoom Admin — to serve the two groups.

In the Zoom Marketplace, these apps are named Pipedream, and Pipedream for Zoom Admins, respectively.

Non-admins have permissions to manage standard Zoom resources in their account: meetings, webinars, recordings, and more. If you're a non-admin, you'll want to use the Zoom app.

Zoom admins have permissions to manage account-level resources, like users and reports. They can also manage webinars and meetings across their organization. If you're an admin and need to manage these resources via API, you'll want to use the Zoom Admin app.

The Zoom API docs on permissions provide detailed information on these permissions and their associated OAuth scopes.

Action Code#

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

export default {
  key: "zoom-delete-user",
  name: "Delete User",
  description: "Disassociates (unlinks) a user from the associated account or permanently deletes a user.",
  version: "0.2.1",
  type: "action",
  props: {
    zoom: {
      type: "app",
      app: "zoom",
    },
    user_id: {
      type: "string",
      description: "The user ID or email address of the user.",
    },
    action: {
      type: "string",
      description: "Delete action options:<br>`disassociate` - Disassociate a user.<br>`delete`-  Permanently delete a user.<br>Note: To delete pending user in the account, use `disassociate",
      optional: true,
      options: [
        "disassociate",
        "delete",
      ],
    },
    transfer_email: {
      type: "string",
      description: "Transfer email.",
      optional: true,
    },
    transfer_meeting: {
      type: "boolean",
      description: "Transfer meeting.",
      optional: true,
    },
    transfer_webinar: {
      type: "boolean",
      description: "Transfer webinar.",
      optional: true,
    },
    transfer_recording: {
      type: "boolean",
      description: "Transfer recording.",
      optional: true,
    },
  },
  async run({ $ }) {
  //See the API docs here: https://marketplace.zoom.us/docs/api-reference/zoom-api/users/userdelete
    const config = {
      method: "delete",
      url: `https://api.zoom.us/v2/users/${this.user_id}`,
      params: {
        action: this.action,
        transfer_email: this.transfer_email,
        transfer_meeting: this.transfer_meeting,
        transfer_webinar: this.transfer_webinar,
        transfer_recording: this.transfer_recording,
      },
      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.

Label	Prop	Type	Description
Zoom	`zoom`	`app`	This component uses the Zoom app.
user_id	`user_id`	`string`	The user ID or email address of the user.
action	`action`	`string`	Select a value from the drop down menu:`disassociatedelete`
transfer_email	`transfer_email`	`string`	Transfer email.
transfer_meeting	`transfer_meeting`	`boolean`	Transfer meeting.
transfer_webinar	`transfer_webinar`	`boolean`	Transfer webinar.
transfer_recording	`transfer_recording`	`boolean`	Transfer recording.

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: