目标网址和页面内容会交给托管的 Firecrawl 服务处理
原文依据:3 处技能要求提供 Firecrawl API 密钥,并说明该密钥用于托管请求;随后通过 Firecrawl 抓取所给网址的内容、图片和截图。非公开页面地址、查询参数中的令牌或页面中的敏感内容可能因此交给第三方服务处理。
第三方可能接收到目标网址及其可访问的页面内容;如果网址含秘密参数或页面本不应外传,可能造成敏感信息披露。
该技能明确要求用于托管 Firecrawl 请求的 API 密钥,并要求把用户提供的网址提交给 Firecrawl,抓取品牌数据、图片和整页截图。这支持第三方服务会处理目标 URL 及返回页面数据的风险;若 URL 含查询令牌,或页面需授权且包含敏感信息,可能造成额外暴露。源码未说明私有页面认证如何传递,因此不能断言此类数据一定会被发送。用户可限制为公开、无敏感参数的网址,并向作者确认 Firecrawl 的数据保留和访问政策。
source: https://github.com/firecrawl/firecrawl-workflowsinputs: - name: FIRECRAWL_API_KEY description: Firecrawl API key for hosted Firecrawl requests when the workflow runs through the CLI or API. required: true---查看另外 2 个位置
Use Firecrawl through the CLI or equivalent tool surface. Always start with two parallel scrapes of the supplied URL:1. The `branding` and `images` formats together for structured design tokens and the full set of page images.2. A full-page screenshot for visual context.Use the structured `branding` output as the primary source for colors, typography, components, brand assets (logo, favicon, ogImage), personality, and confidence notes. Use the `images` list as the source of truth for the page's content imagery — hero photography, product shots, carousels, feature visuals, illustrations, and decorative graphics. Use the screenshot as the primary visual reference for layout, hierarchy, and overall feel. Add supplemental formats only when these are insufficient for the final artifact.