Labsco
firecrawl logo

firecrawl-interact

✓ Official★ 507

by firecrawl · part of firecrawl/cli

Interact with scraped pages in a live browser session. Scrape a page first, then use natural language prompts or code to click, fill forms, navigate, and extract data.

🔥🔥🔥✓ VerifiedFreeQuick setup
#email#automation#scraping#git#search
🧰 Not standalone. This skill ships with firecrawl/cli and only works together with that tool — install the tool first, then add this skill.

Interact with scraped pages in a live browser session. Scrape a page first, then use natural language prompts or code to click, fill forms, navigate, and extract data.

Inspect the full instructions your agent will receiveExpand

This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.

by firecrawl

Interact with scraped pages in a live browser session. Scrape a page first, then use natural language prompts or code to click, fill forms, navigate, and extract data. npx skills add https://github.com/firecrawl/cli --skill firecrawl-interact Download ZIPGitHub507

firecrawl interact

Interact with scraped pages in a live browser session. Scrape a page first, then use natural language prompts or code to click, fill forms, navigate, and extract data.

When to use

  • Content requires interaction: clicks, form fills, pagination, login

  • scrape failed because content is behind JavaScript interaction

  • You need to navigate a multi-step flow

  • Last resort in the workflow escalation pattern: search → scrape → map → crawl → interact

  • Never use interact for web searches — use search instead

Options

Option Description --prompt <text> Natural language instruction (use this OR --code) --code <code> Code to execute in the browser session --language <lang> Language for code: bash, python, node --timeout <seconds> Execution timeout (default: 30, max: 300) --scrape-id <id> Target a specific scrape (default: last scrape) -o, --output <path> Output file path

Profiles

Use --profile on the scrape to persist browser state (cookies, localStorage) across scrapes:

Copy & paste — that's it
# Session 1: Login and save state
firecrawl scrape "https://app.example.com/login" --profile my-app
firecrawl interact --prompt "Fill in email with [email protected] and click login"

# Session 2: Come back authenticated
firecrawl scrape "https://app.example.com/dashboard" --profile my-app
firecrawl interact --prompt "Extract the dashboard data"

Read-only reconnect (no writes to profile state):

Copy & paste — that's it
firecrawl scrape "https://app.example.com" --profile my-app --no-save-changes

Tips

  • Always scrape first — interact requires a scrape ID from a previous firecrawl scrape call

  • The scrape ID is saved automatically, so you don't need --scrape-id for subsequent interact calls

  • Use firecrawl interact stop to free resources when done

  • For parallel work, scrape multiple pages and interact with each using --scrape-id

See also