Firecrawl API SOP

Appearance

Firecrawl + Make (Integromat) Integration ​

Updated Feb 2026

Firecrawl integrates with Make (formerly Integromat) to enable visual web scraping automation. Connect Firecrawl modules to 1,500+ apps using Make's scenario builder -- no code required.

Setup ​

  1. Log in to Make and create a new scenario
  2. Click the + button to add a module
  3. Search for Firecrawl in the module directory
  4. Click Add to insert the Firecrawl module into your scenario
  5. When prompted, create a new connection by entering your Firecrawl API key
  6. Test the connection and configure your first module

Available Modules ​

Action Modules ​

ModuleDescription
Scrape a WebsiteExtract content from a single page in markdown, HTML, or structured format
Crawl a WebsiteRecursively scrape multiple pages from a domain with depth control
Extract a WebsiteExtract structured data from pages using LLM-powered prompts
Map a WebsiteDiscover all URLs on a domain without extracting content
Search a WebsiteFull-page content retrieval for any search query
Get Crawl StatusMonitor the progress of an active crawl operation
Get Extract StatusMonitor the progress of an extraction job

Advanced Module ​

ModuleDescription
Make an API CallSend custom requests to any Firecrawl API endpoint for advanced use cases

Data Mapping ​

Make uses a visual data-mapping interface. After a Firecrawl module executes, its output fields become available as variables in downstream modules.

Common output fields from Scrape:

FieldDescription
markdownPage content as clean markdown
htmlRaw HTML of the page
metadata.titlePage title from the <title> tag
metadata.descriptionMeta description content
metadata.sourceURLThe URL that was scraped
linksArray of links found on the page

Mapping example -- Scrape to Google Sheets:

Column A: {{metadata.title}}
Column B: {{metadata.sourceURL}}
Column C: {{markdown}}
Column D: {{now}}

Example Scenarios ​

Scenario 1: Daily Competitor Price Tracker ​

Modules: Schedule --> Firecrawl (Scrape) --> Google Sheets (Add Row)

  1. Schedule trigger: Runs daily at 8:00 AM
  2. Firecrawl Scrape: Target the competitor product page, use JSON mode with a schema for price, title, availability
  3. Google Sheets: Append a new row with the extracted fields plus timestamp

Scenario 2: Content Change Monitor ​

Modules: Schedule --> Firecrawl (Scrape) --> Router --> Slack / Google Sheets

  1. Schedule trigger: Runs every 6 hours
  2. Firecrawl Scrape: Extract the target page as markdown
  3. Router: Branch based on whether content has changed since last run
  4. Slack: Send alert if content changed
  5. Google Sheets: Log all results for historical comparison

Scenario 3: Lead Enrichment Pipeline ​

Modules: Webhook --> Firecrawl (Scrape) --> Firecrawl (Extract) --> HubSpot (Update Contact)

  1. Webhook: Receives a company URL from your CRM or form
  2. Firecrawl Scrape: Pull the company homepage content
  3. Firecrawl Extract: Use an LLM prompt to extract company size, industry, services, and tech stack
  4. HubSpot: Update the contact record with enrichment data

Scenario 4: Multi-Site Search Aggregation ​

Modules: Schedule --> Firecrawl (Search) --> Iterator --> Firecrawl (Scrape) --> Airtable (Create Record)

  1. Schedule trigger: Weekly on Monday
  2. Firecrawl Search: Query "AI regulation" site:reuters.com OR site:techcrunch.com
  3. Iterator: Loop through each search result
  4. Firecrawl Scrape: Get full content of each result page
  5. Airtable: Store the title, URL, content, and date
CategoryApps
Data StorageGoogle Sheets, Airtable, Notion, monday.com
CommunicationSlack, Telegram, Gmail, Microsoft Teams
CRMHubSpot, Pipedrive, Salesforce
AI / LLMOpenAI (ChatGPT), Google Gemini, Perplexity
Project ManagementAsana, Trello, ClickUp

Configuration Best Practices ​

Scrape vs. Crawl ​

  • Use Scrape for individual pages -- faster execution and predictable credit usage
  • Use Crawl only when you need content from multiple linked pages on the same domain
  • Set explicit page limits on crawl operations to control costs

Error Handling ​

  • Add an Error Handler module after Firecrawl nodes to catch failures
  • Use Resume directives for non-critical scrapes that can be skipped
  • Add a Rollback directive when downstream data integrity matters

Rate Limiting ​

  • Insert Sleep modules between Firecrawl calls if processing many URLs in a loop
  • Use Batch Scrape instead of iterating individual scrapes for better performance
  • Schedule intensive scenarios during off-peak hours

Cost Optimization ​

  • Use Map first to discover URLs, then selectively scrape only the pages you need
  • Apply includePaths and excludePaths filters on crawl operations
  • Use JSON mode with a schema to extract only relevant fields instead of full page content

TIP

Make's Scenario History shows the input and output of every module execution. Use it to debug data mapping issues and verify that Firecrawl is returning the expected content.

Resources ​