Create Ingress From URL with LiveKit API on Ticket Solved (Instant) from Zendesk API

Pipedream makes it easy to connect APIs for LiveKit, Zendesk and 2,400+ other apps remarkably fast.

Trigger workflow on

Ticket Solved (Instant) from the Zendesk API

Next, do this

Create Ingress From URL with the LiveKit 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 Zendesk trigger and LiveKit action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the Ticket Solved (Instant) trigger
1. Connect your Zendesk account
2. Select a Trigger Category ID
3. Optional- Configure Custom Subdomain
4. Optional- Select one or more Fields
5. Optional- Configure JSON Body
Configure the Create Ingress From URL action
1. Connect your LiveKit account
2. Optional- Configure Ingress Name
3. Select a Room Name
4. Configure Participant Identity
5. Optional- Configure Participant Name
6. Optional- Configure Participant Metadata
7. Optional- Configure Bypass Transcoding
8. Optional- Configure Enable Transcoding
9. Configure URL
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#

Ticket Solved (Instant) on Zendesk

Description:Emit new event when a ticket has changed to solved status

Version:0.2.2

Key:zendesk-ticket-solved

View on GitHub

Zendesk Overview#

The Zendesk API enables seamless integration of Zendesk's customer service platform with your existing business processes and third-party applications. By leveraging this API with Pipedream, you can automate ticket tracking, sync customer data, escalate issues, and streamline communication across multiple channels. This can significantly increase efficiency, accelerate response times, and enhance the overall customer experience. Automations can range from simple notifications to complex workflows involving data transformation and multi-step actions across various services.

Trigger Code#

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

export default {
  ...common,
  name: "Ticket Solved (Instant)",
  key: "zendesk-ticket-solved",
  type: "source",
  description: "Emit new event when a ticket has changed to solved status",
  version: "0.2.2",
  dedupe: "unique",
  methods: {
    ...common.methods,
    getWebhookName() {
      return "Ticket Solved Webhook";
    },
    getTriggerTitle() {
      return "Ticket Solved Trigger";
    },
    getTriggerConditions() {
      return {
        all: [
          {
            field: "update_type",
            value: "Change",
          },
          {
            field: "status",
            operator: "value",
            value: "solved",
          },
        ],
      };
    },
  },
};

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
Zendesk	`app`	`app`	This component uses the Zendesk app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
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.
Trigger Category ID	`categoryId`	`string`	Select a value from the drop down menu.
Custom Subdomain	`customSubdomain`	`string`	For Enterprise Zendesk accounts: optionally specify the subdomain to use. This will override the subdomain that was provided when connecting your Zendesk account to Pipedream. For example, if you Zendesk URL is https://examplehelp.zendesk.com, your subdomain is `examplehelp`
Fields	`fields`	`string[]`	Select a value from the drop down menu.
JSON Body	`jsonBody`	`string`	Custom JSON Body of the incoming payload. Setting `jsonBody` will overwrite the `fields` prop

Trigger Authentication#

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

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

triggers:writewebhooks:writereadtickets:writetickets:readusers:writeorganizations:readorganizations:write

About Zendesk#

Zendesk is award-winning customer service software trusted by 200K+ customers. Make customers happy via text, mobile, phone, email, live chat, social media.

Action#

Create Ingress From URL on LiveKit

Description:Create a new ingress from url in LiveKit. [See the documentation](https://docs.livekit.io/home/ingress/overview/#url-input-example).

Version:0.0.1

Key:livekit-create-ingress-from-url

View on GitHub

Action Code#

import { IngressInput } from "livekit-server-sdk";
import app from "../../livekit.app.mjs";

export default {
  key: "livekit-create-ingress-from-url",
  name: "Create Ingress From URL",
  description: "Create a new ingress from url in LiveKit. [See the documentation](https://docs.livekit.io/home/ingress/overview/#url-input-example).",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    name: {
      type: "string",
      label: "Ingress Name",
      description: "The name of the ingress",
      optional: true,
    },
    roomName: {
      description: "The name of the room to send media to",
      propDefinition: [
        app,
        "room",
      ],
    },
    participantIdentity: {
      type: "string",
      label: "Participant Identity",
      description: "Unique identity of the participant",
    },
    participantName: {
      type: "string",
      label: "Participant Name",
      description: "Participant display name",
      optional: true,
    },
    participantMetadata: {
      type: "string",
      label: "Participant Metadata",
      description: "Metadata to attach to the participant",
      optional: true,
    },
    bypassTranscoding: {
      type: "boolean",
      label: "Bypass Transcoding",
      description: "Whether to skip transcoding and forward the input media directly. Only supported by WHIP",
      optional: true,
    },
    enableTranscoding: {
      type: "boolean",
      label: "Enable Transcoding",
      description: "Whether to enable transcoding or forward the input media directly. Transcoding is required for all input types except WHIP. For WHIP, the default is to not transcode.",
      optional: true,
    },
    url: {
      type: "string",
      label: "URL",
      description: "URL of the media to pull for ingresses of type URL",
    },
  },
  async run({ $ }) {
    const {
      app,
      name,
      roomName,
      participantIdentity,
      participantName,
      participantMetadata,
      bypassTranscoding,
      enableTranscoding,
      url,
    } = this;

    const response = await app.createIngress({
      inputType: IngressInput.URL_INPUT,
      name,
      roomName,
      participantIdentity,
      participantName,
      participantMetadata,
      bypassTranscoding,
      enableTranscoding,
      url,
    });
    $.export("$summary", `Successfully created ingress with ID \`${response.ingressId}\`.`);
    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
LiveKit	`app`	`app`	This component uses the LiveKit app.
Ingress Name	`name`	`string`	The name of the ingress
Room Name	`roomName`	`string`	Select a value from the drop down menu.
Participant Identity	`participantIdentity`	`string`	Unique identity of the participant
Participant Name	`participantName`	`string`	Participant display name
Participant Metadata	`participantMetadata`	`string`	Metadata to attach to the participant
Bypass Transcoding	`bypassTranscoding`	`boolean`	Whether to skip transcoding and forward the input media directly. Only supported by WHIP
Enable Transcoding	`enableTranscoding`	`boolean`	Whether to enable transcoding or forward the input media directly. Transcoding is required for all input types except WHIP. For WHIP, the default is to not transcode.
URL	`url`	`string`	URL of the media to pull for ingresses of type URL

Action Authentication#

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

To retrieve your API Key, Secret Key and Project URL,

Navigate to your LiveKit account and sign in
Go to “Settings” > "Project" for Project URL
Go to “Settings” > "Keys" for API Key and Secret Key

Create Ingress From URL with LiveKit API on Ticket Solved (Instant) from Zendesk API

Pipedream makes it easy to connect APIs for LiveKit, Zendesk and 2,400+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,400+apps by most popular

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