Authenticated form and click flows may cause account or commercial side effects
Source references: 6The Skill supports clicks, typing, forms, and multi-step flows but does not require user confirmation before submitting forms, changing settings, sending messages, ordering, or confirming transactions. Its recommendation to keep workflows small does not prevent generated integration code from activating consequential controls.
On a live account, incorrect target selection or an overly broad action prompt could submit data, alter account settings, or trigger an external action the user did not intend.
This is active guidance for product code that clicks, types, submits forms, and performs authenticated multi-step flows. Such automation could change an account or cause commercial effects if it reaches submit, purchase, send, or settings controls. Although the Skill recommends narrow workflows, the visible source has no pre-submit confirmation, read-only constraint, or prohibition on high-impact actions. Actual effects depend on the generated integration and target page. Users can require explicit confirmation and an action allowlist.
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 scrapingShow 5 other places
- search forms and faceted filters- paginated result sets- login-gated dashboards or tools- flows where the page must be explored before extraction is complete- `/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.---name: firecrawl-build-interactdescription: 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.license: ISC- 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- 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.