---
title: "screenshotbase Integration"
description: "screenshotbase is a website screenshot API. Workflows capture full-page or viewport screenshots with ad, cookie-banner, and chat blocking, save them to FlowRunner files or a hosted URL, and check the account quota."
url: https://flowrunner.ai/integrations/screenshotbase
date_modified: 2026-09-04T14:59:52-07:00
---
# screenshotbase
[Developer Tools](https://flowrunner.ai/integrations/category/developer-infrastructure)
screenshotbase is a website screenshot API. Workflows capture full-page or viewport screenshots with ad, cookie-banner, and chat blocking, save them to FlowRunner files or a hosted URL, and check the account quota.
[Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 4 actions · API key · available
[screenshotbase website](https://screenshotbase.com/) · [Platform Documentation](https://screenshotbase.com/) · Capability data verified 2026-08-25
1. A deploy finishes, or the weekly page check fires on a schedule
2. Get Account Status confirms quota remains, because an exhausted quota answers every capture with a 429
3. Save Screenshot To FlowRunner File renders each monitored page into workspace storage
4. Agent confirms the full page rendered rather than going blank below the fold on lazy-loaded sections
5. Each capture is compared against the same page's image from the previous run
6. Pages that changed are collected into one review message with the stored captures attached
7. The owner decides which captures leave the workspace, and by which of the three routes
## What This Integration Enables
screenshotbase renders a URL into an image, and the interesting part of this connector is not the render. It is that there are three genuinely different ways to receive the result, and they are not interchangeable. Save Screenshot To FlowRunner File puts the bytes in your own workspace storage. Take Screenshot puts the image on screenshotbase's CDN and hands back a public URL. Get Screenshot URL calls nothing at all: it builds a request URL that renders when the recipient loads it, which is what makes a live screenshot work inside an email or an `![]()
` tag.
Most screenshot APIs make that choice for you. This one makes you make it, which is honest, because the choice is about who can see the page you captured. FlowRunner agents handle the capture, the comparison, and the packaging at machine speed. The route the image travels by is a judgment about the content on it, and that is where [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) belongs in this workflow.
### Without FlowRunner
**Screenshots taken by hand**: Somebody opens a browser, resizes it, and dismisses a cookie banner before every capture
**Inconsistent evidence**: Two captures of the same page differ because one caught a chat widget and the other caught a promo bar
**Delivery decided by convenience**: The fastest way to get an image into a message becomes the default, whatever is on the screen
### With FlowRunner
**Capture as a workflow step**: Viewport, device scale, full-page mode, and blocking rules are set once and applied every run
**Comparable images**: Ad, cookie-banner, and chat blocking plus element hiding remove the parts that change on their own
**Delivery as a deliberate choice**: Confidential captures stay in workspace storage, and public ones go out on a route somebody picked
## Use Case Scenarios
### Visual checks that survive a deploy
A deploy completes on [Netlify](https://flowrunner.ai/integrations/netlify) and the agent captures the pages that matter most: pricing, signup, the top three landing pages. Each capture uses Save Screenshot To FlowRunner File with ad, cookie-banner, and chat blocking on, so the diff reflects the release rather than whichever overlay happened to load. Changed pages post to [Slack](https://flowrunner.ai/integrations/slack) with the before and after images attached. Two settings do most of the work here: Device Scale Factor at 2 produces a retina-quality image at the same layout, while doubling the viewport width instead renders a different, wider page. Full-page capture on a lazy-loading section needs a delay, or the bottom half comes back blank.
### A competitor page archive with dates on it
On a schedule the agent captures a set of competitor pricing and feature pages, stores each image in workspace storage, and logs the URL, capture time, and file reference to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) alongside a [Notion](https://flowrunner.ai/integrations/notion) entry. When a claim changes, the archive says what the page said and when. The blocking rules matter more than they look: a promotional banner rotating between four variants otherwise produces four different images of a page that never changed.
### A live screenshot inside a status email
An internal weekly email includes a current view of the customer dashboard. Get Screenshot URL is built for exactly this, because it renders on load rather than shipping a stale attachment, and it spends no quota when it is built. It also embeds the account API key in the URL as a query parameter. The agent assembles the message through [SendGrid](https://flowrunner.ai/integrations/sendgrid) and stops before sending it, because the recipient list decides whether that URL is a convenience or a leaked credential.
## Human-in-Loop Highlight
Get Screenshot URL is the operation this gate exists for. It carries the account's API key in the URL as the `apikey` parameter, so anyone who receives that message can render anything they like and spend your quota doing it. Take Screenshot has a quieter version of the same problem: its hosted image sits on screenshotbase's CDN and is reachable by anybody who learns the link, which is fine for a marketing page and wrong for a screenshot of an admin console with customer names on it. So the agent captures, packages, and then stops: "Weekly dashboard email is ready for 340 recipients. The embedded image is a Get Screenshot URL, which carries the account API key. Switch to a workspace file attachment, or send as built?" Neither the key nor the customer names can be recalled after the message goes. The capture was the agent's job. Choosing what leaves the workspace was not.
Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via email
Human decides
Agent resumes with decision
## Agent Capabilities
4 actions
### Screenshots
3
- **Take Screenshot** Renders a URL and stores the image on screenshotbase's CDN, returning its public URL. The right form when the image is going into a message, page, or document that references a URL, and the wrong one for anything confidential, because the hosted copy is reachable by anybody who has the link.
- **Save Screenshot To FlowRunner File** Renders a URL and stores the image in FlowRunner's own file storage. The default for anything with customer data, internal tooling, or an unreleased page on screen, and also the form whose response carries the vendor's cost header, because the binary route is the only one that sets it.
- **Get Screenshot URL** Builds a complete screenshotbase request URL with every capture option encoded into it, without calling the API or spending quota. This is the form that renders live inside an \`![]()
\` tag or an email, and it embeds the API key in the URL, so the result is a spendable credential and should be treated as one.
### Account
1
- **Get Account Status** Returns the monthly and grace quota with used and remaining figures. The vendor states this call does not count against the quota or the rate limit, which makes it free to poll on a schedule. Worth alerting on, because an exhausted quota shows up as a 429 on every capture with nothing else to warn you.
## Frequently Asked Questions
### What can FlowRunner do with screenshotbase?
FlowRunner agents can run Take Screenshot, Save Screenshot To FlowRunner File, and Get Screenshot URL in screenshotbase, plus 1 more action.
### Does connecting screenshotbase to FlowRunner require OAuth?
No. screenshotbase connects to FlowRunner with an API key, no OAuth flow required.
### Can screenshotbase trigger a FlowRunner workflow automatically?
screenshotbase doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
**Work at screenshotbase?** This integration exposes screenshotbase 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/screenshotbase. Site index: https://flowrunner.ai/llms.txt