Send A Message with Trengo API on Custom Events from Zoom API

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

Trigger workflow on

Custom Events from the Zoom API

Next, do this

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

Select this integration
Configure the Custom Events trigger
1. Connect your Zoom account
2. Select one or more Zoom Events
3. Configure zoomApphook
Configure the Send A Message action
1. Connect your Trengo account
2. Select a Channel ID
3. Configure Identifier
4. Configure Name
5. Configure Message
6. Optional- Configure Email Subject
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#

Custom Events on Zoom

Description:Listen for any events tied to your Zoom user or resources you own

Version:0.0.4

Key:zoom-custom-events

View on GitHub

Trigger Code#

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

export default {
  key: "zoom-custom-events",
  name: "Custom Events",
  description:
    "Listen for any events tied to your Zoom user or resources you own",
  version: "0.0.4",
  props: {
    zoom,
    eventNameOptions: {
      label: "Zoom Events",
      type: "string[]",
      async options() {
        return [
          "meeting.alert",
          "meeting.created.by_me",
          "meeting.created.for_me",
          "meeting.updated",
          "meeting.deleted.by_me",
          "meeting.deleted.for_me",
          "meeting.started",
          "meeting.ended",
          "meeting.registration_created",
          "meeting.registration_approved",
          "meeting.registration_cancelled",
          "meeting.registration_denied",
          "meeting.sharing_started.host",
          "meeting.sharing_started.participant",
          "meeting.sharing_ended.host",
          "meeting.sharing_ended.participant",
          "meeting.participant_jbh_joined",
          "meeting.participant_jbh_waiting",
          "meeting.participant_joined",
          "meeting.participant_left",
          "meeting.participant_joined_waiting_room",
          "meeting.participant_admitted",
          "meeting.participant_put_in_waiting_room",
          "meeting.participant_left_waiting_room",
          "recording.started",
          "recording.paused",
          "recording.resumed",
          "recording.stopped",
          "recording.completed",
          "recording.trashed.by_me",
          "recording.trashed.for_me",
          "recording.deleted.by_me",
          "recording.deleted.for_me",
          "recording.recovered.by_me",
          "recording.recovered.for_me",
          "recording.transcript_completed",
          "recording.registration_created",
          "recording.registration_approved",
          "recording.registration_denied",
          "user.updated",
          "user.settings_updated",
          "user.signed_in",
          "user.signed_out",
          "webinar.created.by_me",
          "webinar.created.for_me",
          "webinar.updated",
          "webinar.started",
          "webinar.ended",
          "webinar.alert",
          "webinar.sharing_started.host",
          "webinar.sharing_started.participant",
          "webinar.sharing_ended",
          "webinar.registration_created",
          "webinar.registration_approved",
          "webinar.registration_denied",
          "webinar.registration_cancelled",
          "webinar.participant_joined",
          "webinar.participant_left",
        ];
      },
    },
    zoomApphook: {
      type: "$.interface.apphook",
      appProp: "zoom",
      async eventNames() {
        return this.eventNameOptions;
      },
    },
  },
  async run(event) {
    console.log(event);
    this.$emit(event, {
      summary: event.event,
    });
  },
};

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
Zoom	`zoom`	`app`	This component uses the Zoom app.
Zoom Events	`eventNameOptions`	`string[]`	Select a value from the drop down menu.
	`zoomApphook`	`$.interface.apphook`

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

Action#

Send A Message on Trengo

Description:This action can be used to easily send a message or an email without having to think about contacts or tickets, [See the docs](https://developers.trengo.com/reference/send-a-message-1)

Version:0.0.1

Key:trengo-send-a-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.

Action Code#

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

export default {
  type: "action",
  key: "trengo-send-a-message",
  version: "0.0.1",
  name: "Send A Message",
  description: "This action can be used to easily send a message or an email without having to think about contacts or tickets, [See the docs](https://developers.trengo.com/reference/send-a-message-1)",
  props: {
    app,
    channelId: {
      propDefinition: [
        app,
        "channelId",
      ],
    },
    contactIdentifier: {
      propDefinition: [
        app,
        "contactIdentifier",
      ],
      description: "The destination of the message. Based on the `Channel ID` this must be en email address or phone number.",
    },
    contactName: {
      propDefinition: [
        app,
        "contactName",
      ],
      description: "The name of the contact. Only used when the contact does not already exists.",
    },
    message: {
      propDefinition: [
        app,
        "message",
      ],
    },
    emailSubject: {
      propDefinition: [
        app,
        "emailSubject",
      ],
    },
  },
  async run ({ $ }) {
    const resp = await this.app.sendMessage({
      $,
      data: {
        channel_id: this.channelId,
        contact_identifier: this.contactIdentifier,
        contact_name: this.contactName,
        message: this.message,
        email_subject: this.emailSubject,
      },
    });
    $.export("$summary", "The message has been sent");
    return resp;
  },
};

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
Trengo	`app`	`app`	This component uses the Trengo app.
Channel ID	`channelId`	`integer`	Select a value from the drop down menu.
Identifier	`contactIdentifier`	`string`	The destination of the message. Based on the `Channel ID` this must be en email address or phone number.
Name	`contactName`	`string`	The name of the contact. Only used when the contact does not already exists.
Message	`message`	`string`	The message send to the receiver.
Email Subject	`emailSubject`	`string`	The subject of the message. Only used when the message is an email.

Send A Message with Trengo API on Custom Events from Zoom API

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

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

Developers ♥ Pipedream

1-12of1000+apps by most popular

1
-
12
of
1000+
apps by most popular