Cancel Profile Setup Session
Cancel a Browser Context Profile setup session and permanently discard its unsaved cookies and browser storage.
TinyFish provides web automation, live search, content extraction, research, browser sessions, reusable browser profiles, and run management through native REST APIs.
Cancel a Browser Context Profile setup session and permanently discard its unsaved cookies and browser storage.
Cancel one running TinyFish research run using a connected TinyFish account. Cancellation is irreversible but idempotent: terminal runs return their current status with cancelled=false.
Idempotently cancel one or up to 100 asynchronous or SSE runs. Active cancellation is irreversible; synchronous runs cannot be cancelled, and already-terminal runs are returned with their actual status.
Create an isolated TinyFish remote browser session and return its CDP connection URL. This action starts billable browser infrastructure: TinyFish meters Browser usage until the session ends or becomes inactive. You must call Terminate Browser Session with the returned session_id immediately after browser work finishes, including after failures, to stop further usage charges. Creation can return before startup navigation completes.
Create a scheduled Page or Topic Monitor and immediately capture its paid baseline using a connected TinyFish account. Each completed baseline costs $0.005, failed runs are not charged, and an account can hold at most 50 Monitors; a timeout or server error can leave the Monitor created.
Create a reusable Browser Context Profile for cookies and browser storage; this changes persistent account state.
Permanently delete a TinyFish Monitor and its schedule using a connected TinyFish account. Its Monitor run history becomes unavailable and this action cannot be undone; verify an ambiguous outcome before another delete.
Permanently delete a Browser Context Profile and all browser state saved in it. This action cannot be undone.
Permanently remove saved cookies and browser storage for one domain from a Browser Context Profile. This action cannot be undone.
Render and extract content from 1-10 URLs in one provider-native batch. Always inspect both results and errors because HTTP 200 can contain successful pages and per-URL failures together.
Get one TinyFish Page or Topic Monitor by ID using a connected TinyFish account, including its target config, schedule, lifecycle status, webhook, and last error.
Get one Browser Context Profile and its saved-domain metadata.
Read one saved TinyFish research run using a connected TinyFish account, including status, partial or final reports, plan, evidence, and iteration count. Inspect status before treating any report as complete; unsuccessful runs can retain partial results.
Get summary records for 1-100 TinyFish automation run IDs in one request. The response separately reports IDs that were not found or are not owned.
Get the TinyFish wallet balance, auto-reload and pending-top-up state, and current Agent and Browser rates. Monetary values are returned as exact decimal strings. Legacy-credit accounts report FEATURE_NOT_AVAILABLE rather than an authentication failure.
List Page and Topic Monitors owned by a connected TinyFish account, including their IDs for management and run operations.
List Browser Context Profiles available to the connected TinyFish account. Use the returned IDs when attaching or managing reusable browser state.
List saved TinyFish research runs with optional status, query, date, and sort filters, returning one cursor-controlled page.
List automation runs with optional status, goal, date, and sort filters, returning one cursor-controlled page.
List one page of Search, Fetch, or Browser usage history. Search and Fetch usage reads are free; Browser usage requires the paid Browser service.
List display-safe metadata for password-manager vaults connected to TinyFish. Credentials and secret values are excluded.
List display-safe metadata for items synchronized from password-manager vaults connected to TinyFish. Secret field values are never returned.
Run an existing Page or Topic Monitor immediately and save its result; managed Instant users must connect their own TinyFish account. Each completed run costs $0.005 and sends no webhook or email notification; a timeout or server error leaves creation uncertain.
Persist cookies and browser storage from a completed setup session into a Browser Context Profile, then clean up the temporary session. Persisted state and successful session cleanup cannot be undone. The response retains domain-level skips and failures plus cleanup status so partial success remains visible.
Search live web pages, news, or research papers with domain and time filters, optionally fetching result pages inline, and return exactly one caller-selected zero-based result page.
Start a billable temporary remote browser session for establishing login state in a Browser Context Profile. The returned browser state is not saved automatically: after setup, always call Save Profile Setup Session to persist it or Cancel Profile Setup Session to discard it and tear down the session.
Start a paid TinyFish research run in the background and return its run ID; managed Instant users must connect their own TinyFish account. A timeout does not prove rejection, so avoid automatically submitting the same research again.
Refresh display-safe item metadata from all password-manager vaults already connected to TinyFish. Synchronization can add, update, or remove mirrored items. Returns synchronization counts and allowlisted item metadata without credential or secret values.
Idempotently terminate a remote TinyFish browser session to stop further browser usage charges. Already-ended sessions are also successful.
Pause or resume a TinyFish Monitor, or edit its schedule and delivery metadata, using a connected TinyFish account. Status changes cannot be combined with other edits, and schedule or metadata edits require a schedule; type and target config are immutable.
Rename a Browser Context Profile or change its default and proxy-country settings. Omitted fields remain unchanged.
Upload cookies and local or session storage directly into a Browser Context Profile. This changes persistent login state and may transmit authentication secrets; call it only with the credential owner's explicit authorization. TinyFish provides no rollback endpoint, so restoring prior state requires a caller-held copy or deleting the affected domains.
The TinyFish integration connects your Dench AI CRM directly to TinyFish, so agents can read and act on your TinyFish data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
32 actions are available for agents to invoke on your behalf. Every call runs through TinyFish's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find TinyFish and click Connect — you'll authorize access through TinyFish's own sign-in flow. No API keys or code required.
Ask an agent to use TinyFish in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench TinyFish integration connects your AI CRM to TinyFish, so AI agents can work with your TinyFish data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The TinyFish integration currently exposes 32 actions, including Cancel Profile Setup Session, Cancel Research Run, Cancel Runs, Create Browser Session, Create Monitor, and Create Profile. Agents invoke them on your behalf from chat or from automations.
No. You connect TinyFish from your Dench workspace using TinyFish's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through TinyFish's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the TinyFish connection from your workspace settings at any time.