Request Task with Runware API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on

New Requests (Payload Only) from the HTTP / Webhook 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 HTTP / Webhook 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 New Requests (Payload Only) trigger
1. Connect your HTTP / Webhook account
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#

New Requests (Payload Only) on HTTP / Webhook

Description:Get a URL and emit the HTTP body as an event on every request

Version:0.1.1

Key:http-new-requests-payload-only

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Trigger Code#

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

// Core HTTP component
// Returns a 200 OK response, emits the HTTP payload as an event
export default {
  key: "http-new-requests-payload-only",
  name: "New Requests (Payload Only)",
  // eslint-disable-next-line
  description: "Get a URL and emit the HTTP body as an event on every request",
  version: "0.1.1",
  type: "source",
  props: {
    // eslint-disable-next-line
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    http,
  },
  async run(event) {
    const { body } = event;
    this.httpInterface.respond({
      status: 200,
      body,
    });
    // Emit the HTTP payload
    this.$emit({
      body,
    });
  },
};

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
N/A	`httpInterface`	`$.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.
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

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.

Action Authentication#

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

About Runware#

Low Cost, Ultra-Fast Stable Diffusion API

More Ways to Connect Runware + HTTP / Webhook#

Other Popular Integrations#

Request Task with Runware API on New Requests from HTTP / Webhook API

HTTP / Webhook + Runware

Try it

Request Task with Runware API on New event when the content of the URL changes. from HTTP / Webhook API

HTTP / Webhook + Runware

Try it

Image Background Removal with Runware API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Runware

Try it

Image Background Removal with Runware API on New Requests from HTTP / Webhook API

HTTP / Webhook + Runware

Try it

Image Caption with Runware API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Runware

Try it

Popular Triggers#

New Requests from the HTTP / Webhook API

Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

Try it

New Requests (Payload Only) from the HTTP / Webhook API

Get a URL and emit the HTTP body as an event on every request

Try it

New event when the content of the URL changes. from the HTTP / Webhook API

Emit new event when the content of the URL changes.

Try it