Scrape without JS with ScrapeNinja API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on

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

Next, do this

Scrape without JS with the ScrapeNinja 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 ScrapeNinja 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 Scrape without JS action
1. Connect your ScrapeNinja account
2. Configure URL
3. Optional- Configure Headers
4. Optional- Configure Retry Number
5. Optional- Configure Geo
6. Optional- Configure Proxy
7. Optional- Configure Follow Redirects
8. Optional- Configure Timeout
9. Optional- Configure Text Not Expected
10. Optional- Configure Status Not Expected
11. Optional- Configure Extractor
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#

Scrape without JS on ScrapeNinja

Description:Use high-performance web scraping endpoint with Chrome browser TLS fingerprint, but without JavaScript execution and real browser overhead. [See the documentation](https://scrapeninja.net/docs/api-reference/scrape/)

Version:0.0.1

Key:scrapeninja-scrape-without-js

View on GitHub

ScrapeNinja Overview#

ScrapeNinja API on Pipedream allows you to craft powerful serverless workflows for web scraping without the hassle of managing proxies or browsers. It's a tool that can extract data from websites, handling JavaScript rendering and anti-bot measures with ease. By integrating ScrapeNinja with Pipedream, you can automate data collection, collate and process the scraped data, and connect it to numerous other services for further analysis, alerting, or storage.

Action Code#

import { ConfigurationError } from "@pipedream/platform";
import { parseObject } from "../../common/utils.mjs";
import scrapeninja from "../../scrapeninja.app.mjs";

export default {
  key: "scrapeninja-scrape-without-js",
  name: "Scrape without JS",
  description: "Use high-performance web scraping endpoint with Chrome browser TLS fingerprint, but without JavaScript execution and real browser overhead. [See the documentation](https://scrapeninja.net/docs/api-reference/scrape/)",
  version: "0.0.1",
  type: "action",
  props: {
    scrapeninja,
    url: {
      propDefinition: [
        scrapeninja,
        "url",
      ],
    },
    headers: {
      propDefinition: [
        scrapeninja,
        "headers",
      ],
      optional: true,
    },
    retryNum: {
      propDefinition: [
        scrapeninja,
        "retryNum",
      ],
      optional: true,
    },
    geo: {
      propDefinition: [
        scrapeninja,
        "geo",
      ],
      optional: true,
    },
    proxy: {
      propDefinition: [
        scrapeninja,
        "proxy",
      ],
      optional: true,
    },
    followRedirects: {
      propDefinition: [
        scrapeninja,
        "followRedirects",
      ],
      optional: true,
    },
    timeout: {
      propDefinition: [
        scrapeninja,
        "timeout",
      ],
      optional: true,
    },
    textNotExpected: {
      propDefinition: [
        scrapeninja,
        "textNotExpected",
      ],
      optional: true,
    },
    statusNotExpected: {
      propDefinition: [
        scrapeninja,
        "statusNotExpected",
      ],
      optional: true,
    },
    extractor: {
      propDefinition: [
        scrapeninja,
        "extractor",
      ],
      optional: true,
    },
  },
  async run({ $ }) {
    try {
      const response = await this.scrapeninja.scrapeNonJs({
        $,
        data: {
          url: this.url,
          headers: parseObject(this.headers),
          retryNum: this.retryNum,
          geo: this.geo,
          proxy: this.proxy,
          followRedirects: this.followRedirects,
          timeout: this.timeout,
          textNotExpected: parseObject(this.textNotExpected),
          statusNotExpected: parseObject(this.statusNotExpected),
          extractor: this.extractor,
        },
      });
      $.export("$summary", "Successfully scraped the URL");
      return response;
    } catch ({ response: { data } }) {
      throw new ConfigurationError(data.message || data.stderr);
    }
  },
};

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
ScrapeNinja	`scrapeninja`	`app`	This component uses the ScrapeNinja app.
URL	`url`	`string`	The URL to scrape.
Headers	`headers`	`string[]`	Custom headers to send with the request. By default, regular Chrome browser headers are sent to the target URL.
Retry Number	`retryNum`	`integer`	Amount of attempts.
Geo	`geo`	`string`	Geo location for basic proxy pools (you can purchase premium ScrapeNinja proxies for wider country selection and higher proxy quality). Read more about ScrapeNinja proxy setup
Proxy	`proxy`	`string`	Premium or your own proxy URL (overrides `Geo` prop). Read more about ScrapeNinja proxy setup
Follow Redirects	`followRedirects`	`integer`	Whether to follow redirects.
Timeout	`timeout`	`integer`	Timeout per attempt, in seconds. Each retry will take [timeout] number of seconds.
Text Not Expected	`textNotExpected`	`string[]`	Text which will trigger a retry from another proxy address.
Status Not Expected	`statusNotExpected`	`integer[]`	HTTP response statuses which will trigger a retry from another proxy address.
Extractor	`extractor`	`string`	Custom JS function to extract JSON values from scraped HTML. Write&test your own extractor on https://scrapeninja.net/cheerio-sandbox/

Action Authentication#

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

Using ScrapingNinja in Pipedream

Create a RapidAPI Account: Begin by signing up for a RapidAPI account.
Access Your API Key:
- Once registered, you'll be able to interact with ScrapingNinja using your RapidAPI key.
- Open the ScrapingNinja documentation on RapidAPI and locate your API key labeled X-RapidAPI-Key.
- Copy this key and paste it into the rapid_api_key field below.
Subscribe to the API: Finally, click Subscribe to Test in the RapidAPI console to subscribe to the ScrapingNinja API.

About ScrapeNinja#

Extract Web Data on Scale

More Ways to Connect ScrapeNinja + HTTP / Webhook#

Other Popular Integrations#

Scrape with JS Rendering with ScrapeNinja API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + ScrapeNinja

Try it

Scrape with JS Rendering with ScrapeNinja API on New Requests from HTTP / Webhook API

HTTP / Webhook + ScrapeNinja

Try it

Scrape without JS with ScrapeNinja API on New Requests from HTTP / Webhook API

HTTP / Webhook + ScrapeNinja

Try it

Scrape with JS Rendering with ScrapeNinja API on New event when the content of the URL changes. from HTTP / Webhook API

HTTP / Webhook + ScrapeNinja

Try it

Scrape without JS with ScrapeNinja API on New event when the content of the URL changes. from HTTP / Webhook API

HTTP / Webhook + ScrapeNinja

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