已登录的表单和点击流程可能产生账户或商业副作用
原文依据:6 处该技能支持点击、输入、表单和多步骤流程,但没有要求在提交表单、修改设置、发送消息、下单或确认交易前获得用户确认。虽然它建议缩小流程范围,这并不能阻止生成的集成触发有副作用的控件。
在真实账户中,错误的目标识别或过宽的动作提示可能提交数据、改变账户设置,或触发用户并未打算执行的外部操作。
这是面向产品代码的主动页面操作指导,范围包括点击、输入、表单和登录后的多步骤流程。此类操作若命中提交、购买、发送或设置变更控件,可能改变账户或产生商业后果;源码虽要求缩小流程范围,却没有可见的提交前确认、只读限制或高风险动作禁止规则。具体副作用取决于生成的集成和目标页面,不能据此认定已经发生。用户可要求为有副作用的动作加入明确确认和允许列表。
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查看另外 5 个位置
- 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.