Request Task with Runware API on Ticket Updated (Instant) from Zendesk API

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

Trigger workflow on

Ticket Updated (Instant) from the Zendesk API

Next, do this

Request Task with the Runware 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 Runware action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the Ticket Updated (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 Request Task action
1. Connect your Runware account
2. Select a Task Type
3. Optional- Select a Output Type
4. Optional- Select a Output Format
5. Optional- Configure Upload Endpoint
6. Optional- Configure Check NSFW
7. Optional- Configure Include Cost
8. Configure Positive Prompt
9. Optional- Configure Negative Prompt
10. Optional- Configure Seed Image
11. Optional- Configure Mask Image
12. Optional- Configure Strength
13. Configure Height
14. Configure Width
15. Configure Model
16. Optional- Configure Steps
17. Optional- Configure Scheduler
18. Optional- Configure Seed
19. Optional- Configure Number Of Results
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 Updated (Instant) on Zendesk

Description:Emit new event when a ticket has been updated

Version:0.2.2

Key:zendesk-ticket-updated

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 Updated (Instant)",
  key: "zendesk-ticket-updated",
  type: "source",
  description: "Emit new event when a ticket has been updated",
  version: "0.2.2",
  dedupe: "unique",
  methods: {
    ...common.methods,
    getWebhookName() {
      return "Ticket Updated Webhook";
    },
    getTriggerTitle() {
      return "Ticket Updated Trigger";
    },
    getTriggerConditions() {
      return {
        all: [
          {
            field: "update_type",
            value: "Change",
          },
        ],
      };
    },
  },
};

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#

Request Task on Runware

Description:Request one task to be processed by the Runware API. [See the documentation](https://docs.runware.ai/en/image-inference/api-reference).

Version:0.0.1

Key:runware-request-task

View on GitHub

Action Code#

import { v4 as uuid } from "uuid";
import app from "../../runware.app.mjs";

export default {
  key: "runware-request-task",
  name: "Request Task",
  description: "Request one task to be processed by the Runware API. [See the documentation](https://docs.runware.ai/en/image-inference/api-reference).",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    taskType: {
      propDefinition: [
        app,
        "taskType",
      ],
    },
    outputType: {
      propDefinition: [
        app,
        "outputType",
      ],
    },
    outputFormat: {
      propDefinition: [
        app,
        "outputFormat",
      ],
    },
    uploadEndpoint: {
      propDefinition: [
        app,
        "uploadEndpoint",
      ],
    },
    checkNSFW: {
      propDefinition: [
        app,
        "checkNSFW",
      ],
    },
    includeCost: {
      propDefinition: [
        app,
        "includeCost",
      ],
    },
    positivePrompt: {
      propDefinition: [
        app,
        "positivePrompt",
      ],
    },
    negativePrompt: {
      propDefinition: [
        app,
        "negativePrompt",
      ],
    },
    seedImage: {
      propDefinition: [
        app,
        "seedImage",
      ],
    },
    maskImage: {
      propDefinition: [
        app,
        "maskImage",
      ],
    },
    strength: {
      propDefinition: [
        app,
        "strength",
      ],
    },
    height: {
      propDefinition: [
        app,
        "height",
      ],
    },
    width: {
      propDefinition: [
        app,
        "width",
      ],
    },
    model: {
      propDefinition: [
        app,
        "model",
      ],
    },
    steps: {
      propDefinition: [
        app,
        "steps",
      ],
    },
    scheduler: {
      propDefinition: [
        app,
        "scheduler",
      ],
    },
    seed: {
      propDefinition: [
        app,
        "seed",
      ],
    },
    numberResults: {
      propDefinition: [
        app,
        "numberResults",
      ],
    },
  },
  async run({ $ }) {
    const {
      app,
      taskType,
      outputType,
      outputFormat,
      uploadEndpoint,
      checkNSFW,
      includeCost,
      positivePrompt,
      negativePrompt,
      seedImage,
      maskImage,
      strength,
      height,
      width,
      model,
      steps,
      scheduler,
      seed,
      numberResults,
    } = this;

    const response = await app.post({
      $,
      data: [
        {
          taskUUID: uuid(),
          taskType,
          outputType,
          outputFormat,
          uploadEndpoint,
          checkNSFW,
          includeCost,
          positivePrompt,
          negativePrompt,
          seedImage,
          maskImage,
          strength,
          height,
          width,
          model,
          steps,
          scheduler,
          seed: seed
            ? parseInt(seed)
            : undefined,
          numberResults,
        },
      ],
    });

    $.export("$summary", `Successfully requested task with UUID \`${response.data[0].taskUUID}\`.`);
    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
Runware	`app`	`app`	This component uses the Runware app.
Task Type	`taskType`	`string`	Select a value from the drop down menu:`{ "value": "imageInference", "label": "Image Inference" }{ "value": "imageControlNetPreProcess", "label": "Image Control Net Preprocess" }{ "value": "imageUpscale", "label": "Image Upscale" }{ "value": "imageBackgroundRemoval", "label": "Image Background Removal" }{ "value": "imageCaption", "label": "Image Caption" }{ "value": "promptEnhance", "label": "Prompt Enhance" }`
Output Type	`outputType`	`string`	Select a value from the drop down menu:`base64DatadataURIURL`
Output Format	`outputFormat`	`string`	Select a value from the drop down menu:`PNGJPGWEBP`
Upload Endpoint	`uploadEndpoint`	`string`	This parameter allows you to specify a URL to which the generated image will be uploaded as binary image data using the HTTP PUT method. For example, an S3 bucket URL can be used as the upload endpoint. When the image is ready, it will be uploaded to the specified URL.
Check NSFW	`checkNSFW`	`boolean`	This parameter is used to enable or disable the NSFW check. When enabled, the API will check if the image contains NSFW (not safe for work) content. This check is done using a pre-trained model that detects adult content in images. When the check is enabled, the API will return `NSFWContent: true` in the response object if the image is flagged as potentially sensitive content. If the image is not flagged, the API will return `NSFWContent: false`. If this parameter is not used, the parameter `NSFWContent` will not be included in the response object. Adds `0.1` seconds to image inference time and incurs additional costs. The NSFW filter occasionally returns false positives and very rarely false negatives.
Include Cost	`includeCost`	`boolean`	If set to `true`, the cost to perform the task will be included in the response object. Defaults to `false`.
Positive Prompt	`positivePrompt`	`string`	A positive prompt is a text instruction to guide the model on generating the image. It is usually a sentence or a paragraph that provides positive guidance for the task. This parameter is essential to shape the desired results. For example, if the positive prompt is `dragon drinking coffee`, the model will generate an image of a dragon drinking coffee. The more detailed the prompt, the more accurate the results. The length of the prompt must be between 4 and 2000 characters.
Negative Prompt	`negativePrompt`	`string`	A negative prompt is a text instruction to guide the model on generating the image. It is usually a sentence or a paragraph that provides negative guidance for the task. This parameter helps to avoid certain undesired results. For example, if the negative prompt is `red dragon, cup`, the model will follow the positive prompt but will avoid generating an image of a red dragon or including a cup. The more detailed the prompt, the more accurate the results. The length of the prompt must be between 4 and 2000 characters.
Seed Image	`seedImage`	`string`	When doing Image-to-Image, Inpainting or Outpainting, this parameter is required. Specifies the seed image to be used for the diffusion process. The image can be specified in one of the following formats: An UUID v4 string of a previously uploaded image or a generated image. A data URI string representing the image. The data URI must be in the format `data:<mediaType>;base64,` followed by the base64-encoded image. For example: `data:image/png;base64,iVBORw0KGgo...`. A base64 encoded image without the data URI prefix. For example: `iVBORw0KGgo...`. A URL pointing to the image. The image must be accessible publicly. Supported formats are: PNG, JPG and WEBP.
Mask Image	`maskImage`	`string`	When doing Inpainting or Outpainting, this parameter is required. Specifies the mask image to be used for the inpainting process. The image can be specified in one of the following formats: An UUID v4 string of a previously uploaded image or a generated image. A data URI string representing the image. The data URI must be in the format `data:<mediaType>;base64,` followed by the base64-encoded image. For example: `data:image/png;base64,iVBORw0KGgo...`. A base64 encoded image without the data URI prefix. For example: `iVBORw0KGgo...`. A URL pointing to the image. The image must be accessible publicly. Supported formats are: PNG, JPG and WEBP.
Strength	`strength`	`string`	When doing Image-to-Image, Inpainting or Outpainting, this parameter is used to determine the influence of the Seed Image image in the generated output. A higher value results in more influence from the original image, while a lower value allows more creative deviation. Min: `0` Max: `1` and Default: `0.8`.
Height	`height`	`integer`	Used to define the height dimension of the generated image. Certain models perform better with specific dimensions. The value must be divisible by 64, eg: `512`, `576`, `640` ... `2048`.
Width	`width`	`integer`	Used to define the width dimension of the generated image. Certain models perform better with specific dimensions. The value must be divisible by 64, eg: `512`, `576`, `640` ... `2048`.
Model	`model`	`string`	This identifier is a unique string that represents a specific model. You can find the AIR identifier of the model you want to use in our Model Explorer, which is a tool that allows you to search for models based on their characteristics. More information about the AIR system can be found in the Models page. Eg. `civitai:78605@83390`.
Steps	`steps`	`integer`	The number of steps is the number of iterations the model will perform to generate the image. The higher the number of steps, the more detailed the image will be. However, increasing the number of steps will also increase the time it takes to generate the image and may not always result in a better image (some schedulers work differently). When using your own models you can specify a new default value for the number of steps. Defaults to `20`.
Scheduler	`scheduler`	`string`	An scheduler is a component that manages the inference process. Different schedulers can be used to achieve different results like more detailed images, faster inference, or more accurate results. The default scheduler is the one that the model was trained with, but you can choose a different one to get different results. Schedulers are explained in more detail in the Schedulers page.
Seed	`seed`	`string`	A seed is a value used to randomize the image generation. If you want to make images reproducible (generate the same image multiple times), you can use the same seed value. When requesting multiple images with the same seed, the seed will be incremented by 1 (+1) for each image generated. Min: `0` Max: `9223372036854776000`. Defaults to `Random`.
Number Of Results	`numberResults`	`integer`	The number of images to generate from the specified prompt. If Seed is set, it will be incremented by 1 (+1) for each image generated.

Request Task with Runware API on Ticket Updated (Instant) from Zendesk API

Pipedream makes it easy to connect APIs for Runware, 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