How to Automate Websites with Claude Using TinyFish

Claude can already work with websites in several ways, from searching and reading web content to taking browser actions through Claude in Chrome. But some workflows need a different execution path: searching across live sources, extracting page content, moving through multi-step websites, or working inside authenticated web apps as part of a larger task.

TinyFish is a Claude connector that gives Claude access to TinySearch, TinyFetch, and TinyAgent for those workflows. Claude handles the broader request and reasoning, while TinyFish carries out the web operation through its own execution layer.

This guide shows you how to connect TinyFish to Claude, start with a simple article summary, and then try forms, Google Sheets, and logged-in dashboards with clear instructions and review points.

TL;DR

• TinyFish gives Claude a web-execution layer for searching, reading, and operating live websites, including multi-step and authenticated workflows.
• Add TinyFish from Claude’s connector directory, sign in to your TinyFish account, and enable it in the conversation where you want to use it.
• Start with a read-only task, such as summarizing a public article. When a workflow changes data, define what may change and where the agent should stop for review.
• Keep consequential actions such as payments, publishing, deletions, and account changes behind an explicit review step.

What TinyFish adds to Claude’s web capabilities

TinyFish brings three tools into the conversation: TinySearch finds sources, TinyFetch retrieves page content, and TinyAgent operates websites through a cloud browser. Claude uses the returned information to summarize, compare, or continue the broader task.

That matters when the task moves from web research to website automation. TinyFish can work through multi-step website flows, log in to authorized sites, fill forms, navigate web applications, and return structured results from the workflow.

The division of work is straightforward: Claude handles the broader request and decides when the web task is needed; TinyFish handles the page-level web operation.

What you need before you start

• A Claude account with access to connectors.
• A TinyFish account.
• Sufficient Wallet balance for any metered TinyAgent actions you plan to run.
• Authorized access to any website or dashboard involved in the task.
• A low-risk first task that does not involve a payment, deletion, publication, or other irreversible action.

This guide uses the TinyFish connector in Claude on the web or Claude Desktop. TinyFish can also be used through MCP-compatible clients, but that setup is outside the scope of this walkthrough.

How to add the TinyFish connector to Claude

1. Open Claude’s connector directory

From a conversation, select the + menu, open Connectors, choose Manage connectors, then select the + button next to Connectors to browse the directory. You can also go to Customize → Connectors and select the + button next to Connectors.

2. Find TinyFish

Search for TinyFish in the directory, or open the official TinyFish connector for Claude directly.

3. Select Add to Claude

On the TinyFish connector page, select Add to Claude to start the connection flow.

4. Sign in to TinyFish

Follow the authentication flow to connect your TinyFish account. Review the requested access before approving it.

5. Enable TinyFish in your conversation

Open the + menu, select Connectors, and make sure TinyFish is enabled for the conversation where you want Claude to use it.

6. Check the connection with a read-only request

Once TinyFish is enabled for the conversation, ask Claude for a task that matches the connector’s capabilities. Claude can bring a connected service into the conversation automatically when it is relevant, so you do not need to name TinyFish in every prompt. For the first test, name TinyFish explicitly so you can confirm which connector Claude is using.

To check that the connection works, try this short request before moving on to the article summary:

Use TinyFish to open the TinyFish connector page for Claude. Find the support email shown on the page and return it with the page URL. Do not click or change anything.

The first time Claude calls a TinyFish tool, it may ask for permission to use it. Review the requested tool and action before continuing. For this test, select Allow once.

Once approved, Claude calls TinyFish and returns the result in the conversation.

Connecting TinyFish authorizes Claude to use the tools exposed by the TinyFish connector. It does not automatically grant access to every website. If a task requires a logged-in site, the TinyFish workflow still needs authorized session or credential access for that website.

Your first task: summarize an article

Start with a public article that you want to understand without reading the whole page. This is a simple, read-only task: TinyFish reads the page, and Claude turns the content into a short, structured summary.

For instance, we tried it with TinyFish’s “What is an AI agent?” article using this prompt:

Note: Use the article URL below to try the same example, or replace it with the public article you want summarized.

Example prompt:

Use TinyFish to read this article: https://www.tinyfish.ai/blog/what-is-an-ai-agent.
Give me a short summary, the key takeaways, and any action items mentioned. Include the source link.

Claude should return a summary, key takeaways, and any next steps mentioned in the article. If it suggests additional steps, it should distinguish those suggestions from what the article explicitly says. Check the source link and compare the main points with the original article.

In our test, Claude returned a summary, a list of key takeaways, and suggested action items. The TinyFish tool call shows how Claude accessed the page; the response shows how it organized the article’s content.

Prompt patterns that make web tasks easier to control

Once the article-summary task works, you can try workflows that interact with a website. Give Claude the page, the information it needs, and a clear boundary for the task. For actions that change data, specify what may change and when to stop for review. The patterns below show how to do this.

Note: Before using these patterns, replace [URL], [dashboard URL], and [Sheet URL] with your own links. Replace [criteria], [metric], [threshold], and [action] with your own selection rules, metric, target value, and intended action. Supply your own form information and adjust the reporting period where needed.

• Use a final-action checkpoint for forms. Open [URL], complete the form with the information I provide, and stop before clicking Submit. Report every field value and any warnings, then wait for my confirmation.
• Use read-only mode when checking a logged-in dashboard. Open [dashboard URL], review this week’s figures, and report the values with their page labels. Do not change filters, settings, records, or account information.
• Use a review checkpoint before editing Google Sheets. Open [Sheet URL], find the rows that match [criteria], and list the proposed cell changes. Do not edit the sheet until I approve them.
• Use a condition to limit when the agent proceeds. Check [dashboard URL] and proceed only if [metric] is above [threshold]. If the condition is true, prepare [action] but stop before submission. Otherwise, report the value and take no action.
• Require clarification when a form lacks required information. Fill every field supported by the information below. If a required field is missing or ambiguous, stop and ask me rather than guessing.

Example: filling out a Google Form

Forms are a good place to use a final-action checkpoint because TinyFish can complete the fields while leaving the submission under your control.

For a workshop registration, use the published responder link for a form you own or are authorized to complete. For a simple test, check that the form opens while signed out; if it requires a Google login, TinyFish needs its own authorized session.

Note: Replace [Google Form URL] with your form’s responder link, [Name] with your name, and the sample session and topics with your choices from the options available in your form.

If the form requires an email address or Google sign-in, make sure the necessary information or authorized session is available before running the task.

Example prompt:

Open [Google Form URL] and complete the registration form with the information below.
Full name: [Name]
Session: [Sample session]
Topics: [Topics]
Fill in only the fields supported by this information. If the form requires any information I have not provided, stop and ask me instead of guessing.
Do not submit the form. When every field supported by my information is complete, report each question and the answer you entered, along with any missing required information or validation warnings. Wait for my confirmation.

TinyFish can open the live form, identify the available fields, select the requested options, and prepare the completed response. If the form contains an unexpected required field, Claude should return that question rather than invent an answer.

Review the completed responses before continuing. If everything is correct, give Claude a narrow follow-up instruction.

Follow-up prompt:

Submit the form once and report the confirmation message shown after submission.

Example: updating a Google Sheet with TinyFish

Claude can already edit Google Sheets through Anthropic’s Google Workspace integrations. TinyFish is useful when the task also involves opening live webpages, gathering information, and entering verified values through the Google Sheets interface.

For example, suppose you want to audit the SEO metadata of several blog posts. Instead of opening each article and manually copying its details into a spreadsheet, you can ask Claude to use TinyFish to collect the information and prepare the updates.

To follow along, create a Google Sheet called Blog Metadata Audit with a tab named Blog Audit. Add these column headers in A1 through D1: Article URL, Page title, H1, and Meta description. Enter the following URLs in cells A2 through A4, leaving B2 through D4 empty:

• https://www.tinyfish.ai/blog/what-is-an-ai-agent
• https://www.tinyfish.ai/blog/how-to-win-a-hackathon-with-ai
• https://www.tinyfish.ai/blog/claude-code-context-window

Make sure TinyFish has authorized access to the spreadsheet before starting.

Note: Replace [Google Sheet URL] with your spreadsheet link. You can use your own article URLs and adjust the tab name and cell range.

Example prompt:

Use TinyFish to open [Google Sheet URL] and select the "Blog Audit" tab.
For each article URL in cells A2 through A4, open the live webpage and retrieve its HTML page title, primary H1 heading, and meta description.
Match the verified information to the correct URL and prepare updates for columns B, C, and D.
Show me the proposed changes in a table before editing the spreadsheet. If a page cannot be accessed or a field cannot be verified, mark it as unavailable rather than guessing.
Do not make any changes until I approve the proposed values.

Compare Claude’s proposed values with the original pages before approving the update.

Follow-up prompt:

Approved. Use TinyFish to update only cells B2 through D4 with the verified information. Leave unavailable values blank. Do not change any other cells, formulas, or formatting.
After updating, reopen the edited range and report the values saved in each cell. If any update cannot be completed or verified, tell me which cells remain unchanged.

After the run, open the spreadsheet and verify the populated cells against the source pages. Check that each value is in the correct row and that no unrelated cells were changed.

Judge the task by the resulting sheet state, not by whether the web-agent run completed.

Example: checking a logged-in dashboard

TinyFish can operate authorized logged-in websites as part of a web-agent workflow. For authenticated tasks, use a configured Browser Context Profile and Vault when credentials are required, rather than putting login details directly into the prompt.

For this example, use the Google Analytics 4 demo account for Google Merchandise Store to review ecommerce metrics without modifying dashboard data.

Open the Google Analytics 4 demo account, sign in with your Google account, and select the Google Merchandise Store (web data) property. Before starting, make sure TinyFish has access through an authorized Browser Context Profile; signing in to Google inside Claude does not automatically give TinyFish access to that session.

Note: Open https://support.google.com/analytics/answer/6367342 to access the demo account. Replace [GA4 dashboard URL] with the relevant GA4 property or report link. You can also use another dashboard you are authorized to access.

Example prompt:

Use TinyFish to open [GA4 dashboard URL] using my configured Browser Context Profile.
In the Google Merchandise Store GA4 property, review website performance for the last seven complete calendar days, excluding today. Compare the results with the preceding seven days.
Retrieve total users, sessions, purchases, and total revenue.
Return a table showing each metric, its value for both periods, and the percentage change. Include the exact date ranges, property reporting time zone, and report used for each metric.
If the previous period’s value is zero, mark the percentage change as not applicable. If a metric is unavailable, report that rather than estimating it.
You may adjust temporary reporting filters. Do not save changes, modify settings, create reports, export customer records, or alter any data.
If the authorized session is unavailable, stop and explain what access is needed rather than requesting my password.

Claude should return a comparison of the two reporting periods, along with the date ranges and sources used. Check the reported figures against the original dashboard before relying on the results.

Permission and credential boundaries

Connecting TinyFish gives Claude access to the tools exposed through the connector. It does not expand the permissions of the website account used in the workflow; the agent can only act within the access available to that authenticated session.

For logged-in workflows, keep credentials separate from the natural-language task. TinyFish uses Vault for credential handling and Browser Context Profiles for reusable authenticated session state, so passwords do not need to be written into the prompt.

The prompt defines the intended scope of the individual task. Name the website, the records or pages involved, what the agent may change, what it must leave untouched, and where it should stop before a consequential action.

When a task fails or stalls

Do not immediately repeat the same prompt when a run stalls. First identify whether the blocker is website access, missing information, or an interaction the agent could not complete. If the task stops at a login or access check, confirm that the correct authorized account or Browser Context Profile is available. A CAPTCHA, MFA prompt, unsupported login method, or site restriction may require user intervention or prevent the workflow from continuing.

If the blocker is missing information instead, provide the required value or explain which option to select. Do not ask the agent to infer required information that was never provided.

Review a partial result before retrying. For a reading task, check which pages or sections were accessible and whether the summary is supported by them. For a task that changes data, check the entered values and changed records, and confirm whether the final action occurred. Resume from the specific point where the task stopped.

Note: Adapt the follow-up prompt below to the question or step where your run stopped, and provide the missing or corrected information in the conversation before asking TinyFish to continue.

Follow-up prompt:

Use TinyFish to continue from the unanswered registration question, use the additional information I provided, and stop before submission.

What Claude can do on websites without TinyFish

On supported Claude surfaces, Claude can operate websites without TinyFish. Claude in Chrome works in your existing browser session and can read pages, click, type, navigate, fill forms, work across tabs, and use existing browser logins. Claude also offers a built-in browser through supported Claude workflows, allowing it to handle web tasks in a separate browser environment.

TinyFish uses a different execution path. Its connector gives Claude access to TinySearch, TinyFetch, and TinyAgent, with website execution running through TinyFish’s cloud browser infrastructure.

A practical way to choose:

• Use Claude in Chrome when the task is already in a browser session you have open.
• Use Claude’s built-in browser when you want Claude to handle a web task in its own browser environment.
• Use TinyFish with Claude when you want Claude to delegate the web step to TinySearch, TinyFetch, or TinyAgent.

These approaches overlap in browser interaction. The difference is not whether Claude can click or fill a form without TinyFish; it is which execution layer handles the web task.

Get started

Add the TinyFish connector to Claude and try the article-summary prompt above. Check the source and the result, then choose a form, spreadsheet, or dashboard workflow when you need Claude to take the next step on a website.

Add TinyFish to Claude