Get Technologies with Wappalyzer API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on

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

Next, do this

Get Technologies with the Wappalyzer 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 Wappalyzer 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 Get Technologies action
1. Connect your Wappalyzer account
2. Configure URLs
3. Optional- Configure Live
4. Optional- Configure Recursive
5. Optional- Configure Callback URL
6. Optional- Configure Denoise
7. Optional- Configure Min Age
8. Optional- Configure Max Age
9. Optional- Configure Squash
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#

Get Technologies on Wappalyzer

Description:Returns the details of technologies used on a specific URL. [See the documentation](https://www.wappalyzer.com/docs/api/v2/lookup/)

Version:0.0.1

Key:wappalyzer-get-technologies

View on GitHub

Wappalyzer Overview#

The Wappalyzer API lets you uncover the technology stack of any website. On Pipedream, you can integrate this capability into workflows to automate tech stack detection. Here's what you can do: identify the software used by your competitors, track technology adoption, and get insights into your target market's tech preferences. By leveraging Pipedream's robust platform, you can connect Wappalyzer with other services to create custom workflows that trigger actions based on the tech stack data you collect.

Action Code#

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

export default {
  key: "wappalyzer-get-technologies",
  name: "Get Technologies",
  description: "Returns the details of technologies used on a specific URL. [See the documentation](https://www.wappalyzer.com/docs/api/v2/lookup/)",
  version: "0.0.1",
  type: "action",
  props: {
    wappalyzer,
    urls: {
      type: "string[]",
      label: "URLs",
      description: "Between one and ten website URLs. Example: `https://example.com,https://example.org`. Multiple URLs are not supported with `recursive=false`.",
    },
    live: {
      type: "boolean",
      label: "Live",
      description: "Scan websites in real-time. Defaults to `false` to return cached results from our database (faster and more complete). If no record is found, `live=true` is automatically used instead. Use `recursive=false` to get live results in the same request.",
      optional: true,
    },
    recursive: {
      type: "boolean",
      label: "Recursive",
      description: "Index multiple pages (follows internal website links for increased coverage). Defaults to `true` for best results. If no record is found or `live=true` is used, using `recursive=true` causes the request to be completed asynchronously, meaning technologies will not be included in the initial response and the website is being crawled. To get the results when they become available, use `callback_url` or repeat the request at a later time (free for up to one hour). A crawl can take up to 15 minutes. We recommend using `callback_url` or repeating the request up to three times every five minutes. When using both `live=true` and `recursive=true`, `callback_url` is required and requests cost two credits instead of one.",
      optional: true,
    },
    callbackUrl: {
      type: "string",
      label: "Callback URL",
      description: "When an asynchronous request completes, a POST request is made to the callback URL with the results. A callback URL is an public endpoint hosted on your own server. Example: `https://yourdomain.com/wappalyzer`. Required when using both `live=true` and `recursive=true`.",
      optional: true,
    },
    denoise: {
      type: "boolean",
      label: "Denoise",
      description: "Exclude low confidence results. Defaults to `true`. Setting this to `false` yields more results but is more likely to include false positives.",
      optional: true,
    },
    minAge: {
      type: "integer",
      label: "Min Age",
      description: "Return results that have been verified at least once before `min_age` months ago. Defaults to 0 for most recent results. Use a higher value in combination with `squash=false` and `max_age` for historic results grouped by month (up to 12 months per request).",
      optional: true,
    },
    maxAge: {
      type: "integer",
      label: "Max Age",
      description: "Return results that have been verified at least once in the last `max_age` months. Defaults to 2 for best results. To get the most up-to-date but fewer results, use `max_age=1`. For real-time results, use `live=true` instead. Use a higher value to get more but less recently verified results. These results are more likely to include websites that no longer use the technology. Use a higher value in combination with `squash=false` and optionally `min_age` for historic results grouped by month (up to 12 months per request).",
      optional: true,
    },
    squash: {
      type: "boolean",
      label: "Squash",
      description: "Merge monthly results into a single set. Defaults to `true`. Set to `false` to group results by month.",
      optional: true,
    },
  },
  async run({ $ }) {
    const response = await this.wappalyzer.getTechnologies({
      $,
      params: {
        urls: this.urls.join(),
        live: this.live,
        recursive: this.recursive,
        callback_url: this.callbackUrl,
        denoise: this.denoise,
        min_age: this.minAge,
        max_age: this.maxAge,
        squash: this.squash,
      },
    });

    $.export("$summary", `Successfully retrieved technologies for ${this.urls.length} URL${this.urls.length === 1
      ? ""
      : "s"}.`);

    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
Wappalyzer	`wappalyzer`	`app`	This component uses the Wappalyzer app.
URLs	`urls`	`string[]`	Between one and ten website URLs. Example: `https://example.com,https://example.org`. Multiple URLs are not supported with `recursive=false`.
Live	`live`	`boolean`	Scan websites in real-time. Defaults to `false` to return cached results from our database (faster and more complete). If no record is found, `live=true` is automatically used instead. Use `recursive=false` to get live results in the same request.
Recursive	`recursive`	`boolean`	Index multiple pages (follows internal website links for increased coverage). Defaults to `true` for best results. If no record is found or `live=true` is used, using `recursive=true` causes the request to be completed asynchronously, meaning technologies will not be included in the initial response and the website is being crawled. To get the results when they become available, use `callback_url` or repeat the request at a later time (free for up to one hour). A crawl can take up to 15 minutes. We recommend using `callback_url` or repeating the request up to three times every five minutes. When using both `live=true` and `recursive=true`, `callback_url` is required and requests cost two credits instead of one.
Callback URL	`callbackUrl`	`string`	When an asynchronous request completes, a POST request is made to the callback URL with the results. A callback URL is an public endpoint hosted on your own server. Example: `https://yourdomain.com/wappalyzer`. Required when using both `live=true` and `recursive=true`.
Denoise	`denoise`	`boolean`	Exclude low confidence results. Defaults to `true`. Setting this to `false` yields more results but is more likely to include false positives.
Min Age	`minAge`	`integer`	Return results that have been verified at least once before `min_age` months ago. Defaults to 0 for most recent results. Use a higher value in combination with `squash=false` and `max_age` for historic results grouped by month (up to 12 months per request).
Max Age	`maxAge`	`integer`	Return results that have been verified at least once in the last `max_age` months. Defaults to 2 for best results. To get the most up-to-date but fewer results, use `max_age=1`. For real-time results, use `live=true` instead. Use a higher value to get more but less recently verified results. These results are more likely to include websites that no longer use the technology. Use a higher value in combination with `squash=false` and optionally `min_age` for historic results grouped by month (up to 12 months per request).
Squash	`squash`	`boolean`	Merge monthly results into a single set. Defaults to `true`. Set to `false` to group results by month.

Action Authentication#

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

About Wappalyzer#

Identify technologies on websites.

More Ways to Connect Wappalyzer + HTTP / Webhook#

Other Popular Integrations#

Get Technologies with Wappalyzer API on New Requests from HTTP / Webhook API

HTTP / Webhook + Wappalyzer

Try it

Get Technologies with Wappalyzer API on New event when the content of the URL changes. from HTTP / Webhook API

HTTP / Webhook + Wappalyzer

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