Library
Scrapers
3 prebuilt collectors, sorted by what they collect from. Fill in a form, pick the proxy the requests leave through, and the rows land in a table of their own — with no browser window anywhere.
On this page
What a scraper is
A scraper has one job and a very small contract: input in, one table out, and no browser at all. You point it at something public — a search, an account, a place — and the rows are the whole deliverable.
That is what separates it from an automation, which drives a real browser window on one of your profiles and can do anything. A workflow that operates your own accounts is an automation. A collector pointed at somebody else's public page is a scraper, and it runs over plain HTTP with a real browser's TLS fingerprint — which is why a Google Maps search that used to take eight minutes in a window now takes about six seconds in none.
Scrapers cost none of your plan's automation slots, and they run signed out, always. Nothing here holds a session, and nothing here can be made to.
The 3 scrapers
One card per service. Everything below is read from the app's own catalogue, so this list is what ships rather than a description of it.
Places
Businesses and locations off the maps and directories that list them.
Google Maps
Every place a Maps search returns, filed as rows with no browser window: name, category, full postal address, phone, website, rating, reviews and — when you ask for it — the email address off the business’s own site.
- You give it
- What to find
- You get back
- 45 columns
- Browser
- Not needed
Social
Public profiles and the posts they have published.
Instagram Profiles
Proxy advisedThe full header behind any public account — bio, follower and post counts, verification, business category and the link in the bio — and, when you ask for it, the email address off the site that link points at.
- You give it
- Accounts
- You get back
- 33 columns
- Browser
- Not needed
Instagram Posts
Proxy advisedEverything a public account has posted — posts, carousels and reels — with captions, timestamps, likes, comments, views and the media links, filed newest first with a row per post.
- You give it
- Accounts
- You get back
- 23 columns
- Browser
- Not needed
Running one
Open the Scrapers tab, pick a card, fill in its form and press Start. Every run makes a new table, named after what you searched for and when, filed in a folder named after the scraper — so two runs of the same card never overwrite each other. Check first if you like: it collects one page, writes nothing, and reports which columns came back filled.
You can also run one without opening the app at all. The assistant has the whole catalogue, so “collect the dentists in Rotterdam” is a sentence rather than a form; the same tools are on the MCP server for outside agents; and a Run scraper step puts a collector inside a workflow, handing the new table's name to whatever comes next.
What they do not do
A scraper will not sign in to anything, and cannot be made to. That rules out whatever a site shows only to a logged-in visitor — on Instagram, that means comments, followers and the posts an account is tagged in. Those are not missing because they are hard: collecting them would need a session, and a session is the thing that turns a settled legal question into an open one.
There is also no “scrape this URL for me”. A scraper is a card for a named service, written and measured against that service's own replies. For a site no card covers, build an automation instead.