Skip to content
Recued
Menu
← Back to recipes

Start a Firecrawl crawl

by recued-core v1

Approval-gated Firecrawl workflow for starting one crawl job. It maps a small URL preview first, calls recued-core.firecrawl.crawl.create for the explicit target URL, then reads the new crawl status. It does not register webhooks, use custom headers/cookies, run browser actions, bypass TLS verification, enable arbitrary proxy selection, or call arbitrary Firecrawl routes.

How it works 9 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (9 steps)
normalized_url trim
Trim whitespace from setting url
map_preview_raw ?
create_crawl ?
crawl_status ?
preview_links default
Apply default
preview_rows_raw map
Extract from each item
preview_rows slice
Take a subset of
preview_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 12 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

url setting =
limit setting = 100
prompt setting =
formats setting = markdown
firecrawl setting =
row limit setting = 20
exclude paths setting =
include paths setting =
allow subdomains setting = false
only main content setting = true
max discovery depth setting = 2
allow external links setting = false

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Firecrawl connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

firecrawl firecrawlcrawlscrapingapprovalpack:firecrawl

Details

9 steps 12 configurable settings recipe_id: start-firecrawl-crawl