GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||
GeezerVison is showing github.com — feat(piloterr): add Piloterr integration by josselinlbe · Pull Request #9837 · simstudioai/sim ConversationSummaryAdds a Piloterr integration: tools, block, icon and generated docs page. I work on Piloterr, so this PR comes from the Piloterr team. Fetch or render any web page, take screenshots, detect a website's technologies, search Google, Amazon and eBay, and get structured LinkedIn and Crunchbase company profiles and Zillow properties, with proxies and anti-bot handling included. Operations:
Credentials are a Piloterr API key on the block ( Product update (if relevant)Sales, e-commerce and research teams can scrape pages, monitor marketplace prices, and enrich accounts with LinkedIn and Crunchbase data. The block appears in the integrations catalog with 7 templates and grounded skills; the docs page is Type of Change
Testing
Checklist
Screenshots/Videos
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Add a Piloterr block for web scraping and structured data: - Fetch a page's HTML, render a JavaScript page, or take a screenshot - Detect the technologies a website runs - Search Google, Amazon and eBay - Get LinkedIn and Crunchbase company profiles by page, name or website domain - Get an eBay listing or a Zillow home Outputs follow the documented OpenAPI schemas and were checked against live responses. Credentials are a Piloterr API key sent in the x-api-key header.
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
|
There was an error while loading. Please reload this page.
[Medium impact] Piloterr adds external data lookups to workflows that choose to use the new integration. The PR appears safe to merge, with non-blocking fixes for agent number checks and the Google Search description. FindingsSummaryAdds Piloterr with eleven tools for web scraping, screenshots, search, and company and property research.
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| params: (params) => { | ||
| const result: Record<string, unknown> = {} | ||
| if (params.operation === 'render_html') { |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Agent tools skip number checks
tools.config.params checks params.operation, but agent tools keep the selected operation separately and pass it through the second callback argument. After switching a Piloterr agent tool to a search or screenshot operation, its numeric inputs skip this mapper. Saved short-input strings stay strings, and blank values are sent instead of being omitted. Read context?.operation ?? params.operation before choosing which numbers to parse.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 56dcdf7. tools.config.params now reads context?.operation ?? params.operation, so an agent tool switched to a search or screenshot operation parses its numeric inputs and drops blank values like the block does.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| id: 'piloterr_google_search', | ||
| name: 'Piloterr Google Search', | ||
| description: | ||
| 'Search Google and get organic results with their position, title, link and snippet, the knowledge graph and the estimated total.', |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Knowledge graph output is missing
piloterr_google_search promises a knowledge graph, but its response mapper and output fields expose only results, totalResults, and hasNextPage. Workflows and agents cannot read the advertised company or entity details. Expose the knowledge graph, or remove that promise from the tool description and generated docs and catalog.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 56dcdf7 by removing the knowledge-graph claim: piloterr_google_search now describes only what it returns (organic results, total results and whether a next page exists), and the docs and catalog were regenerated from it.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
- Describe Google Search without a knowledge graph, which it does not return - Read the operation from the mapper context so agent tools coerce numeric inputs too - Keep response mappers with a single caller in that tool's file - Document the PiloterrIcon export
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.