Scraping · Web

Firecrawl Interact

For pages a plain scrape cannot finish. Clicks, form fills, pagination and auth-aware flows wired into product code through Firecrawl's /interact, instead of giving up at the first button.

Skill name: firecrawl-build-interact
Triggers on: Integrate Firecrawl `/interact` into product code for dynamic pages and browser actions after scraping. Use when a feature needs clicks, form fills, pagination, authentication-aware flows, or other multi-step interactions that plain `/scrape` cannot complete.
Read time: 1 min · Markdown · free to use and edit

Download .md

Use it in your assistant

Claude Code — drop the file in your skills folder and it loads on the next session. Use ~/.claude/skills for every project, or .claude/skills inside a repo to keep it to that project.

mkdir -p ~/.claude/skills/firecrawl-build-interact
curl -L https://growsteady.io/skills/firecrawl-build-interact/download -o ~/.claude/skills/firecrawl-build-interact/SKILL.md

Claude apps (web and desktop) — Settings → Capabilities → Skills → add a skill. Upload the file as SKILL.md inside a folder named firecrawl-build-interact (zip the folder if an archive is asked for).

No install— paste the file into a Claude Project's custom instructions with “Copy as prompt”. Same behaviour, scoped to that project.

Use this when /scrape is not enough because the feature needs to act on the page.

Use This When

content appears only after clicks, typing, or navigation
the feature needs forms, pagination, filters, or multi-step flows
the product must stay in the same browser context after scraping

Default Recommendations

Start with /scrape, then escalate to /interact.
Keep /interact scoped to the smallest browser workflow that unlocks the data.
Use persistent profiles only when the feature truly needs authenticated state across sessions.

Common Product Patterns

search forms and faceted filters
paginated result sets
login-gated dashboards or tools
flows where the page must be explored before extraction is complete

Implementation Notes

/interact is the right tool when the page must be manipulated, not just read.
Keep prompts or action code specific to the product flow.
If the use case is fully open-ended browser automation, evaluate whether a browser sandbox is a better product fit.

Escalation Rules

If the page can be read directly, stay on firecrawl-build-scrape.

Docs (Source of Truth)

Read the source-of-truth page for your project language before writing integration code:

Node / TypeScript: docs.firecrawl.dev/agent-source-of-truth/node
Python: docs.firecrawl.dev/agent-source-of-truth/python
Rust: docs.firecrawl.dev/agent-source-of-truth/rust
Java: docs.firecrawl.dev/agent-source-of-truth/java
Elixir: docs.firecrawl.dev/agent-source-of-truth/elixir
cURL / REST: docs.firecrawl.dev/agent-source-of-truth/curl