Firecrawl Zapier integrationAutomate Firecrawl with Zapier.
The Firecrawl Zapier integration gives you 0 triggers, 7 actions and 3 searches. Firecrawl never starts a Zap by itself: another app hands it a URL or a prompt, and Firecrawl reads the page, crawls the site, maps its links or sends an AI agent to gather data.
Verified Trustpilot reviews · AI, automation & growth agency
What the Firecrawl Zapier integration actually does
Linking Firecrawl to Zapier means a web page, or a whole website, can be read and turned into clean text inside an automation, with nobody copying and pasting. Zapier is the tool that chains apps together. Firecrawl is the scraper: it visits pages and hands back their content in a format the next app can use.
Three results cover most uses. The content of one page, ready to store: /Scrape Page reads a URL and returns it as Markdown, HTML, a summary or a list of links. Every URL of a site in one list: /Map Data finds all the pages of a domain, and /Crawl Website goes further by reading those sub-pages too. Structured answers pulled from the web: /Extract Data and Run Agent take an instruction and come back with the data you asked for, which Get Data From /Extract and Get Agent Status collect.
What Zapier does not do here: Firecrawl has no trigger, so it cannot notice a change on a site and start a Zap by itself. The start always comes from another app, such as a sheet, a form or a CRM. And the heavier jobs (extract, agent) return an ID first; their results come back through a search step.
To weigh the alternatives, the Firecrawl Make integration covers the same app on Make, and the n8n vs Zapier comparison sets out the criteria.
Zapier vocabulary in one minute
Seven words come back on every Zapier page. Here they are in plain English, once.
- Zap
- The automation you build: one event that starts it, then one or more steps that run each time that event happens.
- Trigger
- The event in an app that starts the Zap. Firecrawl has none, so another app always plays this part.
- Action
- What the Zap does once it has started: the step that writes, sends or fetches something on your behalf.
- Task
- The unit Zapier bills. One task is one action that completes successfully; your plan's allowance counts those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant one is pushed by the app the moment the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it quietly otherwise.
- Search step
- A step that looks up something that already exists, so the steps after it can reuse what it found.
What a Firecrawl Zap really costs
Firecrawl is not a premium app, so it works from the free Zapier plan. Two meters run side by side, though.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps only
- Billed by ZapierEach successful action or search
- Not billedThe trigger, the checks, failed steps
On the Zapier side, the trigger from the other app never costs a task, and each Firecrawl action that succeeds counts as one. Failed actions are not billed. The free plan gives 100 tasks a month and two-step Zaps only: one trigger, one action. Scrape a page and then send the text somewhere, or add a search to fetch a job result, and the Zap becomes multi-step, which needs a paid plan. Firecrawl also bills its own credits, a cost that shows up clearly on PDFs.
Connect Firecrawl to Zapier in three steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Firecrawl account linked once, then reused by every Firecrawl step you add.
- 02
Pick Firecrawl
Type Firecrawl in the dialog's search box, select it from the list, then click Add connection. A new tab opens on the Firecrawl side so you can sign in.
- 03
Sign in and allow access
Log in to your Firecrawl account in that tab and grant Zapier access. Without a Firecrawl account the link cannot be made, so create one first if the team has none.
Your first Zap: competitor pages, scraped on arrival
GoalA teammate adds a competitor URL to a spreadsheet, Firecrawl scrapes the page, and the clean text lands in a team chat channel.
- 01
Create the Zap
In Zapier, start a new Zap. Firecrawl has no trigger, so the first step comes from another app: a new row in the sheet where URLs are collected.
- 02
Set the trigger
Pick the sheet and test the step. Zapier brings back the three most recent rows, so you map fields on a real URL rather than an empty example.
- 03
Add /Scrape Page
Add a step, choose Firecrawl and /Scrape Page. Map the URL column into Page URL, pick Markdown or Summary as the format, and switch on main content only.
- 04
Post to the team chat
Add a team chat step and drop the scraped text into the message. That third step makes the Zap multi-step, so it needs a paid plan.
- 05
Test, then publish
Run each step once and read what came back. When the chat message reads well, click Publish to switch the Zap on for good.
Firecrawl actions in Zapier
Firecrawl gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Cancel Agent
ActionIn Zapier“Cancel a running agent job by its ID”
Stops an agent job that is still running, identified by its ID. It is the brake for Run Agent, useful when a job is no longer needed.
/Crawl Website
ActionIn Zapier“Crawl a URL and return sub pages contents”
Starts from one URL and follows its links to read the sub-pages, then returns their content. It is the way to capture a whole help center or blog in one step.
/Extract Data
ActionIn Zapier“Extract structured information”
Pulls structured information from one or more URLs, written in glob format so example.com/* covers a whole site. It can also use web search to fill gaps and list its sources.
/Map Data
ActionIn Zapier“Input a website and get all the urls on the website - extremely fast”
Takes a website and returns the list of its URLs, quickly, without reading each page. A sitemap setting decides whether the sitemap is used, ignored or used alone.
/Scrape Page
ActionIn Zapier“Scrape a URL and return its contents”
Reads one page and returns its content in the formats you pick, with options to keep only the main content, block ads and cookie popups, or emulate a phone.
Run Agent
ActionIn Zapier“Use AI to search, navigate, and gather data from websites using natural language prompts”
Sends an AI agent to search, navigate and collect data from websites, guided by a plain-language prompt. You can keep it on a list of URLs with the strict option.
/Search Data
ActionIn Zapier“Search and optionally scrape search results”
Runs a web search and can scrape the results in the same step. One option drops URLs that other Firecrawl steps could not handle, which saves errors further down the Zap.
Firecrawl searches in Zapier
3 search steps look for data that already exists in Firecrawl, so a later step can use it.
In the editor, Firecrawl's three searches sit at the bottom of the action list, under the SEARCH heading of Action event. They fetch the status and results of jobs started earlier. Three settings decide what happens when the result is not the expected one.
Get Agent Status
SearchIn Zapier“Get the status and results of an agent job by its ID”
Reads where an agent job stands and, once it is done, the data it gathered. It is the second half of Run Agent.
Get Data From /Crawl
SearchIn Zapier“Get the status and data from a crawl”
Brings back the status of a crawl and the data it collected from the sub-pages. Handy when a large crawl is read in a later step.
Get Data From /Extract
SearchIn Zapier“Get the status and data from Extract”
Collects the status and the structured data of an extract job. Without it, /Extract Data starts work you never read.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and the dependent steps are skipped. Switched on, the Zap carries on with empty values.
- Create X if it doesn't exist yet?Turns a search into find-or-create. Firecrawl offers no such variant, so this box does not appear on its searches.
- If multiple search results are found?Three ways out: keep the first match (the default), stop the Zap, or pass every match on at once.
When a Firecrawl Zap breaks
Zapier attaches no help article to Firecrawl, and no Firecrawl-specific limit is documented. What breaks is what breaks on any Zap.
Four cases explain most surprises, and none of them is a Firecrawl bug. If one of them hits you, the Zapier troubleshooting guide walks through the fix step by step.
No catch-up on old rows
A Zap only reacts to what happens after it is switched on. URLs already in your sheet will not be scraped; handling that backlog is a separate job.The Zap that feeds itself
If the scraped text is written back into the very sheet the trigger watches, each write starts the Zap again and burns tasks fast.A bulk paste gets held back
Paste hundreds of URLs at once and Zapier's flood protection can hold the trigger back instead of sending everything to Firecrawl.Duplicates are filtered
On a polling trigger, Zapier remembers what it has already seen, so the same row does not get scraped twice by mistake.
Need help automating Firecrawl with Zapier?
A person reads every message.
