AI-powered browser automation and web interaction agent. Enables AI to browse, interact with websites, and perform web tasks.
Cancels a running or pending automation run by its ID. Idempotent: if the run is already in a terminal state (COMPLETED, FAILED, CANCELLED), returns the current status without error. Only PENDING and RUNNING runs will be actively cancelled.
Discovers the currently running automation for this session. Returns runId if a run is active, or null if not yet started.
Retrieves details of a specific automation run by its ID. Returns status, result, error, and other metadata. IMPORTANT: Call this after run_web_automation errors or times out — the run is likely still executing. If you do not have a run_id, use list_runs to find it. Also use this to poll for completion after run_web_automation_async. Runs typically take a few minutes. Wait 30-60 seconds between polls.
Retrieves the steps taken during an automation run, including screenshots.
Lists automation runs with optional filtering by status and pagination support. Returns an array of runs with their details. Use this to find a recently created run when you do not have its run_id (e.g., after run_web_automation timed out before returning a run_id). Filter by status=RUNNING to find active runs.
Polls the current status of an automation run. Returns status, step, progress, and other metadata.
Executes web automation given a URL and a Natural Language description of the automation goal to be performed. Automation is mostly focused around navigating complex web pages and extracting data from web pages. Include _meta.progressToken in your request to receive progress notifications. WARNING: This tool may take several minutes. If it errors or times out, the run is STILL EXECUTING on the server. DO NOT call this tool again or call run_web_automation_async — both would create a duplicate run. Instead: if you have a run_id from progress notifications, call get_run. If you have no run_id, call list_runs to find it. Only create a new run after confirming the previous one finished.
Starts a NEW web automation run asynchronously and returns a run_id immediately without waiting for completion. WARNING: Do NOT use this to retry a failed run_web_automation call — that run is still executing. Use get_run or list_runs to check its status instead. Only use this tool for genuinely new tasks. Workflow: 1) Call this tool to get a run_id. 2) Wait 30-60 seconds. 3) Call get_run with the run_id to check status. 4) Repeat step 2-3 until status is COMPLETED, FAILED, or CANCELLED.
The TinyFish MCP integration connects your Dench AI CRM directly to TinyFish MCP, so agents can read and act on your TinyFish MCP data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
8 actions are available for agents to invoke on your behalf. Every call runs through TinyFish MCP's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find TinyFish MCP and click Connect — you'll authorize access through TinyFish MCP's own sign-in flow. No API keys or code required.
Ask an agent to use TinyFish MCP in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench TinyFish MCP integration connects your AI CRM to TinyFish MCP, so AI agents can work with your TinyFish MCP 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 MCP integration currently exposes 8 actions, including Cancel run, Discover run, Get run, Get steps, List runs, and Poll status. Agents invoke them on your behalf from chat or from automations.
No. You connect TinyFish MCP from your Dench workspace using TinyFish MCP's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through TinyFish MCP's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the TinyFish MCP connection from your workspace settings at any time.