Get Resources with Cloudinary API on New Requests from HTTP / Webhook API

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

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Get Resources with the Cloudinary 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 Cloudinary 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 trigger
1. Optional- Configure Body Only
2. Optional- Configure Response Status Code
3. Optional- Configure Response Content-Type
4. Optional- Configure Response Body
5. Connect your HTTP / Webhook account
Configure the Get Resources action
1. Connect your Cloudinary account
2. Optional- Select a Resource Type
3. Optional- Select a Filter by Type
4. Optional- Configure Filter by Prefix
5. Optional- Configure Include Tags
6. Optional- Configure Include Context
7. Optional- Configure Include Metadata
8. Optional- Configure Include Moderation
9. Optional- Configure Max 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 on HTTP / Webhook

Description: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.

Version:0.1.1

Key:http-new-requests

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
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "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.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

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.
Body Only	`emitBodyOnly`	`boolean`	This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.
Response Status Code	`resStatusCode`	`string`	The status code to return in the HTTP response
Response Content-Type	`resContentType`	`string`	The `Content-Type` of the body returned in the HTTP response
Response Body	`resBody`	`string`	The body to return in the HTTP response
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#

Get Resources on Cloudinary

Description:Lists resources (assets) uploaded to your product environment. [See the documentation](https://cloudinary.com/documentation/admin_api#get_resources)

Version:0.1.1

Key:cloudinary-get-resources

View on GitHub

Cloudinary Overview#

The Cloudinary API empowers developers to manage media assets in the cloud with ease. It allows for uploading, storing, optimizing, and delivering images and videos with automated transformations to ensure the content is tailored for any device or platform. This API's versatility is key for automating workflows that require dynamic media handling, such as resizing images on-the-fly, converting video formats, or even extracting metadata for asset management.

Action Code#

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

export default {
  key: "cloudinary-get-resources",
  name: "Get Resources",
  description: "Lists resources (assets) uploaded to your product environment. [See the documentation](https://cloudinary.com/documentation/admin_api#get_resources)",
  version: "0.1.1",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: true,
  },
  type: "action",
  props: {
    cloudinary,
    resourceType: {
      propDefinition: [
        cloudinary,
        "resourceType",
      ],
    },
    type: {
      propDefinition: [
        cloudinary,
        "deliveryType",
      ],
    },
    prefix: {
      type: "string",
      label: "Filter by Prefix",
      description: "Find all assets with a public ID that starts with the specified prefix.",
      optional: true,
    },
    tags: {
      type: "boolean",
      label: "Include Tags",
      description: "Whether to include the list of tag names assigned to each asset.",
      default: false,
      optional: true,
    },
    context: {
      type: "boolean",
      label: "Include Context",
      description: "Whether to include key-value pairs of contextual metadata associated with each asset.",
      default: false,
      optional: true,
    },
    metadata: {
      type: "boolean",
      label: "Include Metadata",
      description: "Whether to include the structured metadata fields and values assigned to each asset.",
      default: false,
      optional: true,
    },
    moderation: {
      type: "boolean",
      label: "Include Moderation",
      description: "Whether to include the image moderation status of each asset.",
      default: false,
      optional: true,
    },
    maxResults: {
      type: "integer",
      label: "Max Results",
      description: "Maximum number of resources to return",
      default: 100,
      optional: true,
    },
  },
  async run({ $ }) {
    const options = {
      resource_type: this.resourceType,
      type: this.type,
      prefix: this.prefix,
      tags: this.tags,
      context: this.context,
      moderation: this.moderation,
    };

    const resources = [];
    try {
      let next;
      do {
        const response = await this.cloudinary.getResources(options);
        resources.push(...response.resources);
        next = response.next_cursor;
        options.next_cursor = next;
      } while (next && resources.length < this.maxResults);

      if (resources.length > this.maxResults) {
        resources.length = this.maxResults;
      }

      $.export("$summary", `Retrieved ${resources.length} resource${resources.length === 1
        ? ""
        : "s"}`);

      return resources;
    }
    catch (err) {
      throw new Error(`Cloudinary error response: ${err.error?.message ?? JSON.stringify(err)}`);
    }
  },
};

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
Cloudinary	`cloudinary`	`app`	This component uses the Cloudinary app.
Resource Type	`resourceType`	`string`	Select a value from the drop down menu:`imagerawvideo`
Filter by Type	`type`	`string`	Select a value from the drop down menu:`uploadprivateauthenticatedfetchfacebooktwittergravataryoutubehuluvimeoanimotoworldstarhiphopdailymotionlist`
Filter by Prefix	`prefix`	`string`	Find all assets with a public ID that starts with the specified prefix.
Include Tags	`tags`	`boolean`	Whether to include the list of tag names assigned to each asset.
Include Context	`context`	`boolean`	Whether to include key-value pairs of contextual metadata associated with each asset.
Include Metadata	`metadata`	`boolean`	Whether to include the structured metadata fields and values assigned to each asset.
Include Moderation	`moderation`	`boolean`	Whether to include the image moderation status of each asset.
Max Results	`maxResults`	`integer`	Maximum number of resources to return

Action Authentication#

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

Enter the cloud name, API key and API secret to connect your Cloudinary account. The API credentials are listed on the Programmable Media page of your Cloudinary console

cloudinary console with api credentials

About Cloudinary#

Create, manage and deliver digital experiences

More Ways to Connect Cloudinary + HTTP / Webhook#

Other Popular Integrations#

Get Account Usage Details with Cloudinary API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Cloudinary

Try it

Get Account Usage Details with Cloudinary API on New Requests from HTTP / Webhook API

HTTP / Webhook + Cloudinary

Try it

Image Transformation with Cloudinary API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Cloudinary

Try it

Image Transformation with Cloudinary API on New Requests from HTTP / Webhook API

HTTP / Webhook + Cloudinary

Try it

Resource Transformation with Cloudinary API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Cloudinary

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