Turn any prompt into structured web data. Send a POST request with a natural language prompt and an optional JSON schema, and get back clean, structured results scraped from the web by an AI agent powered by Firecrawl. Use Cases - Data Enrichment: Feed company names or URLs from your CRM and get back structured firmographic data (industry, funding, team size, tech stack). - Lead Generation: Ask the agent to find pricing, contact pages, or product details for a list of competitors. - Market Research: Extract structured pricing plans, feature comparisons, or product catalogs from any website. - Content Aggregation: Pull structured news, events, or job postings from across the web on a schedule. - Sales Intelligence: Enrich prospect lists with company info, recent news, or tech stack details before outreach. How It Works 1. Receive Scrape Request receives a POST request with prompt and an optional outputschema. 2. Validate Output Schema checks the schema. If none is provided, it falls back to a permissive default. If the schema is malformed, it returns a clear error via Return Schema Error. 3. Research & Extract Web Data takes the prompt and uses the full Firecrawl toolkit to research the web: - Search (/search): Finds relevant pages and sources across the web. - Scrape (/scrape): Extracts clean, structured content from any URL. - Interact (interactContext, interact, interactStop): Lets the agent interact with scraped pages in a live session. After scraping a page, the agent can click buttons, fill forms, navigate dynamic content, and extract data that static scraping cannot reach, all without managing sessions manually. This combination gives the AI agent complete web navigation capabilities. It can discover sources, read pages, and interact with dynamic content autonomously. 4. Format Response to Schema (Structured Output Parser) formats the agent's response to match the provided (or default) schema. 5. Return Structured Results sends the structured JSON back to the caller. Setup Requirements - Firecrawl API Key: Sign up at firecrawl.dev and grab your API key. Connect it in the Firecrawl credential nodes. - LLM Provider: Configure your Primary Chat Model and Fallback Chat Model nodes (e.g., OpenRouter, OpenAI, Anthropic). The template uses two model nodes for reliability, plus a separate Parser Chat Model for the output parser. - n8n Instance: Self-hosted or cloud. Make sure the webhook node is set to accept POST requests. API Reference Endpoint Request Body | Field | Type | Required | Description | |-------|------|----------|-------------| | prompt | string | Yes | Natural language instruction for the agent | | outputschema | object | No | JSON Schema defining the desired output structure | Response Returns a JSON object matching the provided schema, or a flexible object if no schema was given. --- Testing Examples 1. Basic Request (No Schema) The agent decides the output structure on its own. Expected output: A JSON object with whatever structure the agent finds most appropriate for the data. Since no schema was provided, the internal default ({ "type": "object", "additionalProperties": true }) is used. 2. Request With a Custom Schema You define exactly the shape of data you want back. Expected output: 3. Invalid Schema (String Instead of Object) Expected output: 4. Invalid Schema (Array Instead of Object) Expected output: Same error response as above. 5. Invalid Schema (Missing type Property) Expected output: Same error response as above. 6. Invalid Schema (Invalid type Value) Expected output: Same error response as above. --- Workflow Architecture Schema Validation Logic The Validate Output Schema node runs this validation before passing data to the agent: - If outputschema is missing or null, the default permissive schema is used: { "type": "object", "additionalProperties": true }. - If outputschema is present, it must be a JSON object (not a string, array, or primitive). - It must have a type property with a valid value: object, array, string, number, or boolean. - If validation fails, the workflow returns an error response with a helpful message and example schema. Notes - The Format Response to Schema node (Structured Output Parser) requires the schema to be passed as a JSON string. The expression {{ JSON.stringify($('Validate Output Schema').item.json.outputschema) }} handles this conversion. - The agent has access to Firecrawl's full toolkit: search, scrape, and interact. With all three connected, the agent has complete web navigation powers. It can discover sources via search, extract content via scrape, and interact with dynamic JavaScript-heavy pages via interact. The interact tools let the agent scrape a page first and then continue working with it in a live session, clicking buttons, filling forms, and navigating deeper, all without manual session management. The agent autonomously decides which tools to use based on the prompt. - Response times vary depending on the complexity of the prompt and how many pages the agent needs to visit. Simple lookups take a few seconds; deep research can take longer.
