--- title: "Testomato Integration" description: "Testomato monitors websites with checks that assert things about your pages. Workflows create projects, run checks on demand, read results, uptime, and response-time history, and manage notification settings." url: https://flowrunner.ai/integrations/testomato date_modified: 2026-09-04T14:59:52-07:00 --- # Testomato [Developer Tools](https://flowrunner.ai/integrations/category/developer-infrastructure) Testomato monitors websites with checks that assert things about your pages. Workflows create projects, run checks on demand, read results, uptime, and response-time history, and manage notification settings. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 21 actions · Session · available [Testomato website](https://testomato.com/) · [Platform Documentation](https://testomato.com/) · Capability data verified 2026-08-25 1. A new site or marketing property is handed over as live 2. Create Project registers the site and generates a starting set of checks from a crawl 3. Get Check reads each generated assertion and what it actually tests 4. The agent compares the generated set against the pages and elements that carry revenue 5. Get Project Permissions confirms the connection can read and run what it just created 6. The agent posts the assertions that exist and the ones it believes are missing 7. The site owner authors the missing checks in Testomato, because this API cannot create one ## What This Integration Enables Uptime monitoring answers a question almost nobody actually has. Sites rarely go dark. They go wrong: a price renders as zero, a phone number reverts to the old one, the consent banner swallows the call to action, the analytics tag disappears in a template change. Every one of those pages returns 200, and every uptime dashboard stays green through all of it. Testomato is built around a different unit, the check, which is a rule that asserts something specific about a page. That is what makes it worth wiring into a flow. FlowRunner agents run those checks on demand rather than waiting for the next scheduled interval, poll the job until every expected result is present, and read the outcome into whatever comes next: a release hold, a ticket, a page to whoever is on call. They also read uptime history and the phase-by-phase response time breakdown that says where a slow page is slow. What agents cannot do here is author a check, and that is not a gap in this connector. Testomato reads checks through the API and writes them only in its own interface. That constraint shapes how the integration should be used, and it is the honest reason the human step on this page sits where it does. ### Without FlowRunner **Green means reachable, not correct**: A page that returns 200 with the wrong price, a dead checkout button, or a missing tracking tag still counts as up **Breakage is discovered by customers**: The first report of a broken form arrives through support, hours after the release that caused it **Slowness has no address**: A page is known to be slow, and nobody can say whether it is DNS, TLS, the server, or the payload ### With FlowRunner **Monitoring asserts specific facts**: Checks test the things the business depends on being on the page, not just that a server answered **Releases verify themselves**: The check run is part of the pipeline, so a broken page is caught within seconds of shipping **Slow pages come with a phase breakdown**: Response time is returned split into lookup, connection, TLS, waiting, and download ## Use Case Scenarios ### A new property is not live until somebody says what it must be true about A site goes live and someone asks for monitoring. The agent calls Create Project against the URL with preset checks enabled, so Testomato crawls the site and generates a starting inventory. It then walks that inventory with List Project Groups and Get Check, and writes a plain summary of what is actually being asserted. Alongside it, the agent lists the pages the business cares about that carry no assertion at all: the pricing page, the checkout confirmation, the lead form's thank-you state. That summary goes to the site owner as a ticket in [Linear](https://flowrunner.ai/integrations/linear). The owner adds the missing checks in Testomato, the agent re-reads the inventory, and only then is the project marked as covered. ### The release pipeline verifies the site instead of hoping A deploy completes on [Netlify](https://flowrunner.ai/integrations/netlify), or a workflow finishes in [GitHub](https://flowrunner.ai/integrations/github). The agent calls Run Project Checks, or Run Group Checks when the release touched one section of the site, and polls Get Job Results. Because an unfinished job returns what it has so far rather than an error, the agent verifies every expected check is present before it decides anything. If assertions failed, the details post to the release channel in [Slack](https://flowrunner.ai/integrations/slack) and an incident is raised in [PagerDuty](https://flowrunner.ai/integrations/pagerduty) with the failing rules named. The site is verified in seconds rather than at the next scheduled interval, and the person who shipped it finds out first. ### Telling a real regression apart from a settings change A weekly job calls Get Uptime and Get Response Times for each property and appends the results to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for trend reporting. When a page slows down, the agent reports the phase that grew rather than the total, so a TLS handshake problem is never mistaken for a slow application. It also carries the context that stops a false alarm: a project's checks run from a chosen location and with a chosen user agent, and changing either can make a passing check start failing for reasons that have nothing to do with the site. The agent states which of those settings changed since the last comparable run, so the team debugs the right thing. ## Human-in-Loop Highlight A Testomato project created without preset checks is an empty project, and checks cannot be created, edited, or deleted through this API at all. Get Check reads them; nothing writes them. So an agent given the job of setting up monitoring can produce something worse than no monitoring: a project that reports green forever because it asserts nothing, sitting on a dashboard the team has started to trust. That is a [digital andon cord](https://flowrunner.ai/concepts/digital-andon-cord) moment in the most literal sense, because the line should not be declared running until someone has confirmed what is being watched. The agent creates the project, reads back every generated assertion, names the revenue-carrying pages that have none, and stops there. It posts: "Project created for shop.example.com. 18 checks generated, covering the homepage, the category pages, and the contact form. No check asserts anything about the cart total, the checkout confirmation page, or the payment provider script. Add those in Testomato before this is marked as covered?" The owner writes the missing checks, because only a person can. Deleting a project is left to a person for the same reason: it takes the check history with it and stops the watch immediately, with nothing left to tell anyone the site broke afterwards. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 21 actions ### Authentication 2 - **Get API Token** Exchanges an email and password for an API token, optionally with a chosen lifetime. Testomato's token is a JWT that expires, which is why a token pasted into a connection eventually starts failing with no visible change. - **Verify API Token** Checks the current token and returns the user it belongs to. The connection test, and the way to tell an expired token apart from a permissions problem. ### Projects 7 - **Create Project** Creates a monitoring project from a URL. Whether preset checks are generated decides whether the project asserts anything at all, which is why this operation is the subject of this page's human gate. - **Get Project** Returns a project's configuration, including the separate project-scoped key Testomato's own settings page exposes. - **Update Project** Changes a project's settings, including the check interval and the uptime poll interval. Both use an explicit off value rather than an absence, so leaving a field empty changes nothing. - **Delete Project** Permanently deletes a project with its checks and its history. Monitoring stops immediately and nothing afterwards reports that the site broke. - **Get Project Status** Returns the project's full current state: every check, its last result, and any failures. The detailed view, which grows with the project. - **Get Simple Project Status** Returns a compact pass or fail summary. The one to poll on a schedule, because it stays small however many checks the project holds. - **Get Project Permissions** Returns what the token's user may do in this project. Worth reading before a write in any flow running as somebody other than the project owner. ### Checks 5 - **Run Project Checks** Starts the project's checks and returns a job id. The deployment hook: called at the end of a release, it verifies the site in seconds instead of at the next interval. - **Run Group Checks** Starts only the checks in one group, which is how a post-deploy test stays fast when the release touched a single section of the site. - **Get Job Results** Returns the results of a check run. An unfinished job returns what it has so far rather than an error, so a flow confirms every expected check is present before deciding the site passed. - **List Project Groups** Returns the project's groups, which is how Testomato organizes a site by section. Their ids are what a group run needs. - **Get Check** Returns one check's definition and its rules. Checks are authored in the Testomato interface and this operation reads them only. ### Monitoring 2 - **Get Uptime** Returns uptime percentages for a period, overall and day by day. A project with uptime monitoring switched off returns a valid-looking body with no data, which the flow reads explicitly rather than treating as perfect uptime. - **Get Response Times** Returns response-time history split into its phases, including lookup, connection, TLS, request, waiting, and download. The breakdown is what says where a slow page is actually slow. ### Users 3 - **List Project Users** Returns the users with access to a project and their roles. Read before any update that rewrites the access list, because that update replaces the whole list rather than adding to it. - **Add Project User** Grants somebody access to a project by email. The role is a bare numeric id, so the available roles are read first rather than guessed. - **List Project Roles** Returns the roles available in a project with their numeric ids. The only thing that says which number means what on a given account. ### Notifications 2 - **Get Notification Settings** Returns the notification settings for the current user. They are per user rather than per project. - **Update Notification Settings** Changes which channels the token's own account is alerted on and at what severity. It cannot configure alerting for anybody else, which is why team-wide routing belongs in the flow rather than here. ## Frequently Asked Questions ### What can FlowRunner do with Testomato? FlowRunner agents can run Get API Token, Verify API Token, and Create Project in Testomato, plus 18 more actions. ### Does connecting Testomato to FlowRunner require OAuth? No. Testomato connects to FlowRunner with session-based authentication, no OAuth flow required. ### Can Testomato trigger a FlowRunner workflow automatically? Testomato doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Testomato?** This integration exposes Testomato to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/testomato. Site index: https://flowrunner.ai/llms.txt