Resources · Make integration

Firecrawl Make integrationAutomate Firecrawl with Make.

Need web pages turned into data your other tools can use, without writing a scraper? The Firecrawl Make integration gives you 9 modules: 8 actions and 1 search. This guide connects your account, builds a first scenario with you and explains when each module earns its place.

Try the Firecrawl integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Firecrawl Make integration do for you?

The Firecrawl Make integration lets a Make scenario (the automation you build, a chain of modules) send a website to Firecrawl and get its content back as data. Each module is one brick: scrape a page, crawl a whole site, map its URLs, search the web or pull structured data with an LLM. No code is involved: you pick modules and fill in fields.

A research sheet that fills itself. A sales rep pastes a prospect's homepage into a spreadsheet. Extract a Website reads the page with an LLM and returns structured data you can map into the next columns, so nobody copies company details by hand.

Content for your AI steps. A content marketer wants a whole documentation site as input for a writing assistant. Map a Website lists the URLs first, Crawl a Website collects the pages, and Get Crawl Status tells you where that crawl stands before you pass anything on.

Search results you can actually read. Search a Website runs a web search and returns the full page content for each result, not only a title and a link. Handy for a watch list of topics your team follows.

Firecrawl has no trigger module in Make, so a Firecrawl scenario starts from a schedule or from another app's trigger. When a listed module falls short, Make an API Call reaches any endpoint of the Firecrawl API with the same connection. Still weighing tools? The n8n vs Make comparison lays out the criteria, and the Make pricing guide explains how operations are counted. To learn the editor properly, see Make training.

Connect

How do you connect Firecrawl to Make?

  1. 01

    Create an API key in Firecrawl

    Log in to Firecrawl, click API Keys in the left sidebar, then + Create. Give the key a name, click Create Key and copy the value somewhere safe. Make needs this key, not your password.

  2. 02

    Open a connection from a Firecrawl module

    In Make, add any Firecrawl module to your scenario and click Create a connection. A connection is your Firecrawl account linked to Make once, then reused by every Firecrawl module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the key into the API Key field and click Save. If Make asks you to authenticate and confirm access, do it. The module is now ready and every other Firecrawl module will offer the same connection.

First scenario

Your first scenario: scrape each new URL from a sheet

GoalWhen a new URL lands in your spreadsheet, Make has Firecrawl scrape that page and hands its content to the next module.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since Firecrawl has no trigger, the first module comes from the app that holds your list of URLs, such as your spreadsheet tool.

  2. 02

    Add Scrape a Website

    Click the + on the right of that first module, search Firecrawl and pick Scrape a Website. First Firecrawl module in your account? Click Create a connection and paste the API key you copied earlier, so every later Firecrawl module can reuse it.

  3. 03

    Map the URL

    In the Scrape module, map the URL coming from the first module instead of typing one. Each bundle (one item passed between modules, here one row) then sends its own page to Firecrawl.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received. Check that the scraped content looks like the page you expected.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What each Firecrawl module does

Firecrawl gives you 9 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

7 modules
Firecrawl1

Crawl a Website

Action

In Make“Used to crawl a URL and get its content”

Hand Crawl a Website a starting URL and Firecrawl walks through the site to return its content, page after page, instead of stopping at one address.

When to use it
you want a whole help center or blog as source material, not a single article.
Watch out
a crawl is tracked by an event ID, so plan a Get Crawl Status step before you rely on the result.
Firecrawl2

Extract a Website

Action

In Make“Extract structured data from pages using LLMs”

You get structured data instead of raw text: Extract a Website uses an LLM to read the pages and pull out structured data, ready to map into a database or CRM.

When to use it
a lead form gives you a company site and you want its key facts in separate fields.
Watch out
extractions have their own event ID and status module, so pair it with Get Extract Status.
Firecrawl3

Get Crawl Status

Action

In Make“Get the status of a given crawl event ID”

This one answers a simple question: where does a given crawl stand? Give Get Crawl Status the crawl event ID and it returns the status of that crawl.

When to use it
right after Crawl a Website, before any module that needs the crawled pages.
Watch out
it only reads a status. It never starts a crawl, so map the crawl event ID from an earlier module rather than typing it.
Firecrawl4

Get Extract Website

ActionIn the docs only

Get Extract Website sits in the Firecrawl actions of the Make doc, but neither the doc nor the directory describes what it returns, so treat it as a module to test before you build on it.

When to use it
only once a Run once shows you bundles that match what your scenario needs.
Watch out
for extraction progress, Get Extract Status is the documented choice.
Firecrawl5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call”

With Make an API Call you reach any endpoint of the Firecrawl API from your scenario, using the connection you already created, so a missing module never blocks you.

When to use it
the eight other modules do not cover the request you need.
Watch out
you write the request yourself, so keep the Firecrawl API documentation open and test it with Run once before switching the scenario on.
Firecrawl6

Map a Website

Action

In Make“Map multiple URLs based on options”

Map a Website gives you the list of URLs a site contains, based on the options you set, so you know what is there before collecting any content.

When to use it
you want to pick a handful of pages to scrape rather than crawl an entire domain.
Watch out
it returns addresses, not page content. Pass the URLs you keep to Scrape a Website afterwards.
Firecrawl7

Scrape a Website

Action

In Make“Used to scrape a URL and get its content”

Point Scrape a Website at one URL and it brings back that page's content, ready for the next module in your scenario.

When to use it
a single known page matters, such as a pricing page or an article your team shares.
Watch out
it covers one address per bundle. For a full site, Crawl a Website is the better fit, and Map a Website helps you choose pages first.

Searches

1 module

Other modules

1 module
Firecrawl9

Get Extract Status

Action

In Make“Get the status of a given extraction event ID”

Get Extract Status tells you how a given extraction is going. Feed it the extraction event ID and it returns the status of that job.

When to use it
after Extract a Website, when the next step needs the structured data to be ready.
Watch out
the doc files it outside the Actions group, so look for it by name when you search the Firecrawl modules.
Need help

Need help automating Firecrawl with Make?

A person reads every message.

FAQ

Firecrawl and Make: common questions

01Is the Firecrawl Make integration free?
Yes, on the Make side. Firecrawl is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations. You still need your own Firecrawl account, whose pricing is outside the scope of this page.
02What do you need to connect Firecrawl to Make?
A Firecrawl account and an API key created in it. In Firecrawl, open API Keys in the left sidebar, click + Create, name the key and click Create Key, then copy the value. In Make, add a Firecrawl module, click Create a connection, paste the key into the API Key field and click Save. If Make asks you to authenticate and confirm access, accept. Naming the connection is optional, and every Firecrawl module in your scenarios reuses it.
03Can a Firecrawl scenario start on its own in Make?
Not from Firecrawl itself, because the app has no trigger module. You have two ways in. Put another app's trigger first, for example a spreadsheet or form module that fires when a new URL arrives, then add Firecrawl after it. Or place a Firecrawl module first and let the schedule start the scenario: every 15 minutes by default, with a 15 minute minimum on the Free plan and 1 minute on paid plans. Either way, test with Run once before switching the scenario on.
04What if a Firecrawl module you need is missing in Make?
Use Make an API Call. It is one of the 9 Firecrawl modules and can call any endpoint of the Firecrawl API with the connection you already set up, so you are not limited to the 8 listed actions and the search. You build the request yourself, which takes a look at the Firecrawl API documentation. The Make doc gives no numeric limits for this app, so test each new call with Run once and read the bundles before relying on it.
05Should you use Make or n8n for Firecrawl?
It depends on where your team already builds. In Make you get 9 Firecrawl modules, a guided editor and Make an API Call for the rest of the API. Many apps also have an n8n node, so check whether one exists for Firecrawl and covers the same requests before you compare. Weigh the modules each tool offers for your case, how your team prefers to work and how each platform counts usage, rather than a general ranking of the two.
Same platform

Other docs you might need on this stack.

Browse all integrations