Resources · Make integration

WebcrawlerAPI Make integrationAutomate WebcrawlerAPI with Make.

Need the content of a web page inside your automations? The WebcrawlerAPI Make integration gives you 1 action, Scrape Webpage, that pulls a page into your workflow. This guide shows how to link your API key, build a first scenario and pick the right starting point.

Try the WebcrawlerAPI integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the WebcrawlerAPI Make integration do for you?

The WebcrawlerAPI Make integration links your WebcrawlerAPI account to Make so a scenario (the automation you build, a chain of modules) can scrape a web page and hand its content to your other tools. It has one module (a brick of the scenario), an action called Scrape Webpage, and no trigger.

Enrich a lead list. A marketer adds a company website to a spreadsheet, another app's module passes it along, and Scrape Webpage fetches the page so the next module can store what it found next to the lead.

Keep an eye on a competitor page. A product manager runs a scenario on Make's schedule, Scrape Webpage reads the pricing or feature page, and the result lands in a document or a message for the team.

Feed content to another step. A content team sends the scraped page to a writing or analysis tool further down the chain, instead of copying text by hand.

What the integration does not do: it cannot start a scenario on its own, since WebcrawlerAPI has no trigger, and it has no Make an API Call module for requests beyond Scrape Webpage. The official documentation also warns that its text is AI-generated from the vendor docs, so check important details with WebcrawlerAPI. If you are weighing tools, the n8n vs Make comparison lays out the differences, and the Make training helps if scenarios are new to you. For help on a larger project, the Make agency team can step in.

Connect

How do you connect WebcrawlerAPI to Make?

  1. 01

    Copy your API key

    Log in to WebcrawlerAPI, open the dashboard, go to the API key section and copy the key shown on screen. You need an active WebcrawlerAPI account for this; the vendor's pricing page covers subscriptions.

  2. 02

    Add the module in Make

    In your scenario, add the WebcrawlerAPI module and click Create a connection. A connection is your WebcrawlerAPI account linked to Make once, then reused by every module of the app.

  3. 03

    Paste the key and save

    You can type a label in the Connection name field if you like. Then paste the API key you copied, or follow the instructions on screen, and save to finish the connection.

First scenario

Your first scenario with WebcrawlerAPI

GoalWhen a new website address shows up in another app, Make scrapes that page with WebcrawlerAPI and passes the content on.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since WebcrawlerAPI has no trigger, this first module comes from another app, such as a spreadsheet or a form.

  2. 02

    Set up the starting module

    Search that other app by name, pick its module, click Create a connection to link your account, and fill in its fields so Make knows where to find the website addresses.

  3. 03

    Add Scrape Webpage

    Click the + on the right of the first module, search WebcrawlerAPI and choose Scrape Webpage. Connect it with your API key, then map the address from the previous module into it.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module's bubble to read the bundles it received, a bundle being one item passed from one module to the next.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, which is every 15 minutes by default for a new scenario, then switch the scenario on. Each run of a module on a bundle counts as one operation on your plan.

Modules

What the WebcrawlerAPI module does

WebcrawlerAPI gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

WebcrawlerAPI1

Scrape Webpage

Action

In Make“Scrape webpage”

Scrape Webpage gets you the content of a web page inside your scenario, ready for the next module to store or send. It is the only WebcrawlerAPI module, so every flow with this app runs through it.

When to use it
a new company website arrives in your lead sheet and you want its page content saved next to the contact without opening a browser.
Watch out
it is an action, so it cannot start a scenario; put a trigger from another app or a schedule in front of it.
Need help

Need help automating WebcrawlerAPI with Make?

A person reads every message.

FAQ

Questions about the WebcrawlerAPI Make integration

01Is the WebcrawlerAPI Make integration free?
Yes on the Make side: WebcrawlerAPI is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the minimum interval to 1 minute and remove the cap on active scenarios. You still need an active WebcrawlerAPI account with an API key, and its subscription is set by WebcrawlerAPI, so check the vendor's pricing page for that part.
02What do you need to connect WebcrawlerAPI to Make?
An active WebcrawlerAPI account and its API key. Log in to WebcrawlerAPI, open the dashboard, go to the API key section and copy the key. In Make, add the WebcrawlerAPI module to a scenario, click Create a connection, optionally name it in the Connection name field, and paste the key. The connection is then reused by the module every time, so you set it up only once per account and every scenario can use it.
03Can WebcrawlerAPI start a Make scenario in real time?
No, because WebcrawlerAPI has no trigger module in Make. The scenario has to start somewhere else. You can open it with a trigger from another app, for instance a new row in a spreadsheet or a new form entry, and then call Scrape Webpage. Or you can run it on Make's own schedule, which is every 15 minutes by default and never under 15 minutes on the Free plan. Paid plans let the interval go down to 1 minute.
04What if the WebcrawlerAPI Make module you need is missing?
It depends on what you need. The app offers a single module, Scrape Webpage, and no Make an API Call module, so there is no generic way to reach other WebcrawlerAPI features from this app inside Make. If Scrape Webpage does not cover your case, look at whether another app in Make handles that step, or ask the Make agency team to study the flow with you. The WebcrawlerAPI documentation is also flagged as AI-generated, so confirm details with the vendor.
05Should you use Make or n8n for WebcrawlerAPI?
It depends on the tool your team already runs. On Make, WebcrawlerAPI gives you one action, Scrape Webpage, that works from the Free plan once your API key is connected, and a Run once test shows the bundles module by module. The same app often has an n8n node as well. The fair way to choose is to check which platform already hosts your other automations and whether the module you need exists there, rather than switching tools for a single step.
Same platform

Other docs you might need on this stack.

Browse all integrations