Reference · Tools

Gemini URL Context

Ground Gemini responses with URL content for accurate answers about web pages.

Action AI v1

Gemini URL Context sends your query to Gemini with URL grounding enabled, so the model reads the live pages you reference before answering — not its training data. Use it to build workflows that summarize articles, extract pricing from product pages, or compare multiple URLs in a single call. The node returns the generated answer, URL context metadata, the model name, and token usage counts.

Node type
Action
Parameters
7
Outputs
Output, Error
Credentials
Google AI

Gemini URL Context

Ground Gemini responses with URL content for accurate answers about web pages.

Overview

Gemini URL Context sends your query to Gemini with URL grounding switched on, so the model fetches and reads the pages you reference in the message before answering. The result is grounded in the live page content rather than in the model’s training data, which makes it suited to summarizing articles, extracting details from a product or pricing page, and comparing several pages at once. Alongside the answer the node returns URL context metadata, the model name and token usage. Optional file references can be sent as extra context.

Category: AI
Tool Name: gemini_url_context
Version: 1

Appearance: Icon: gemini | Color: #ffffff

Node Type

Action — processes input items and produces output

Input / Output

DirectionPort(s)
InputInput
OutputOutput, Error

Credentials

This tool requires Google AI credentials. See the Credentials Guide for setup instructions.

Parameters

ParameterTypeRequiredDefaultDescription
ModeloptionsNoThe Gemini model to use for URL-grounded generation. Pick a specific version — labels are pinned, not aliased to “latest”. The dropdown lists the models currently available for this node; leave it unset to use the default.
System PromptstringNoOptional system instruction that sets the behavior and context for the model. Supports expressions.
User MessagestringYesThe message to send, including one or more URLs for the model to fetch and analyze. Falls back to item.message or item.prompt if empty. Supports expressions.
File URIsstringNoOptional. fileUri value(s) from the Gemini File Upload tool. Pass a single URI or a JSON array for multiple files. Files are sent as multimodal context alongside the message. Falls back to item.fileUris if empty. Gemini File API retains uploads for 48 hours.
OptionscollectionNo{}Optional generation settings.
— TemperaturenumberNo1Controls randomness. Lower values are more deterministic, higher values more creative. Range: 0-2.
— Max Output TokensnumberNo8192Maximum number of tokens in the generated response.
— Response Field NamestringNoresponseThe key name in the output JSON where the generated text will be stored.
Include InputbooleanNofalseWhether to merge the input item JSON into the output item.
Max ConcurrencynumberNo10Maximum number of items to process concurrently.

Output Data

One output item per input item. Binary data arriving from upstream is forwarded untouched.

The output item’s JSON contains only the fields below. The input item’s JSON is merged in only when Include Input is on:

FieldDescription
responseThe grounded answer text. Renamed by Response Field Name.
urlContextMetadataWhat the model did with the URLs in your message — which ones it retrieved and how each retrieval went. Empty when the model reports nothing.
modelThe model that produced the response.
finishReasonWhy generation stopped.
usageToken usage metadata reported by the model.

Reference the result downstream by expression, e.g. {{ $json.response }}.

Usage Examples

  • Summarize the content of a web page URL
  • Extract key information from an article URL
  • Compare content across multiple web pages
  • Answer questions about a specific web page
  • Analyze product pages for pricing and features

Example Configuration

Summarize one page — put the URL directly in the message:

{
  "type": "gemini_url_context",
  "parameters": {
    "userMessage": "Summarize the main points of this article: {{ $json.url }}"
  }
}

Extract fields from a product page, deterministically:

{
  "type": "gemini_url_context",
  "parameters": {
    "systemPrompt": "You are a precise data extraction agent. Extract only the requested fields. Return nothing else.",
    "userMessage": "From the product page at {{ $json.productUrl }}, extract: product name, price, availability, and SKU.",
    "includeInput": true,
    "maxConcurrency": 5,
    "options": {
      "temperature": 0,
      "maxOutputTokens": 256,
      "responseFieldName": "productDetails"
    }
  }
}

Compare two pages in a single call:

{
  "type": "gemini_url_context",
  "parameters": {
    "systemPrompt": "You are a competitive analysis assistant. Compare products objectively.",
    "userMessage": "Compare the features and pricing of these two products: {{ $json.urlA }} and {{ $json.urlB }}. Which offers better value?",
    "maxConcurrency": 10,
    "options": {
      "temperature": 0.7,
      "maxOutputTokens": 2048,
      "responseFieldName": "comparison"
    }
  }
}

Error Handling

ModeBehavior
stopHalts workflow on first error
continueSkips failed items, passes successful ones through
errorPortRoutes failed items to Error output port

Tips

Gemini URL Context sends a user query to the Gemini generateContent API with URL context grounding enabled, allowing the model to fetch and analyze live web page content referenced in the message. Use this tool when your workflow requires answers grounded in specific web pages rather than relying on static training data alone. It returns a generated text response alongside URL context metadata, model information, and token usage counts.

Frequently asked questions

What credential does this node require?

It requires a Google AI credential (type: googleAi). You set this up once in BusyBot's credential store and select it when configuring the node. No other auth method is supported for this node.

How does URL grounding actually work here — does Gemini just read URLs I mention in my message?

Yes. When you include URLs in the message you send to this node, Gemini fetches and reads the content of those pages before generating its answer. This means the response reflects the live page at the time the workflow runs, not whatever Gemini learned about that domain during training. It's the core reason to choose this node over a plain Gemini text node.

What does the node actually return?

The node outputs the generated text response, URL context metadata (information about the pages Gemini retrieved and used), the model name, and token usage counts. These come through the Output path. If something goes wrong — bad credential, unreachable URL, API error — execution takes the Error path instead.

Can I send files alongside the URL references?

Yes. The node supports optional file references that are sent as additional context alongside your message and the URL content. This lets you combine a document you already have with live web content in a single Gemini call.

When should I use this node instead of a generic Gemini node?

Use Gemini URL Context specifically when accuracy depends on the current content of a web page — pricing pages that change frequently, news articles, documentation, or any source where Gemini's training data would be stale or incomplete. If your query doesn't reference a live URL, a standard Gemini node is simpler and doesn't incur the overhead of a page fetch.

Build with the Gemini URL Context node

Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need Google AI credentials first.

Open BusyBot

Last updated . Spotted something wrong? Tell us.