feat(serply): add Serply web search tool and block - #6866
Conversation
Adds a Serply search tool and block following the existing serper/tavily pattern: GET https://api.serply.io/v1/search/ with an API key header, mapped to organic search results (title, link, snippet). Serply is optional; nothing changes for workflows that do not use it.
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryLow Risk Overview A matching Serply workflow block (query, result count, API key) wires to that tool and is registered in the block and tool registries. Existing workflows are unchanged unless they adopt this block; no global Serply env key is introduced. Reviewed by Cursor Bugbot for commit a4129fe. Bugbot is set up for automated code reviews on this repo. Configure here. |
Greptile SummaryAdds a Serply web-search integration and exposes it as a workflow block.
Confidence Score: 4/5The PR appears safe to merge, with only a non-blocking type-safety cleanup needed in the new integration and its test. The block and tool identifiers align and the request path is wired consistently with existing search integrations; the only accepted concern is explicit Files Needing Attention: apps/sim/tools/serply/search.ts, apps/sim/tools/serply/search.test.ts
|
| Filename | Overview |
|---|---|
| apps/sim/tools/serply/search.ts | Implements the Serply request and result mapping correctly at a high level, but uses an explicit any for response items. |
| apps/sim/blocks/blocks/serply.ts | Defines the Serply block with aligned inputs, outputs, credentials, and registered tool access. |
| apps/sim/tools/serply/search.test.ts | Covers the principal request and mapping behavior, with one explicit any weakening type safety. |
| apps/sim/tools/registry.ts | Registers the new tool under the matching serply_search identifier. |
| apps/sim/blocks/registry-maps.ts | Registers the Serply block and metadata consistently in both block maps. |
Reviews (1): Last reviewed commit: "feat(serply): add Serply web search tool..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| const results = Array.isArray(data.results) ? data.results : [] | ||
|
|
||
| const searchResults: SearchResult[] = results.map((item: any) => ({ | ||
| title: item.title || '', |
There was a problem hiding this comment.
The explicit any removes compiler checks from every Serply result mapping, allowing invalid response assumptions to pass type checking as the integration evolves. Model the response item or narrow it from unknown; the same explicit any pattern also appears in the URL-builder test.
Context Used: TypeScript conventions and type safety (source)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit a4129fe. Configure here.
| updateProjectTool, | ||
| } from '@/tools/sentry' | ||
| import { serperSearchTool } from '@/tools/serper' | ||
| import { searchTool as serplySearchTool } from '@/tools/serply/search' |
There was a problem hiding this comment.
Generated tool metadata left stale
Medium Severity
serply_search is registered in the live tool registry, but apps/sim/tools/generated/tool-ids.ts, tool-metadata.ts, and tool-outputs.ts were not regenerated. Client and serializer code resolve tools through those artifacts via hasToolId / getToolParams / getToolMetadata, so the new tool is treated as unknown and tool-metadata:check will fail.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit a4129fe. Configure here.
1 participant
Summary
Adds a Serply (https://serply.io) web search tool and block, following the existing serper/tavily integration pattern.
Closes #6865
serply_search(apps/sim/tools/serply/search.ts):GET https://api.serply.io/v1/search/withX-Api-Keyauth, mapped tosearchResults(title, link, snippet). Serply sits behind Cloudflare, so the request always sends an explicitUser-Agent.SerplyBlock(apps/sim/blocks/blocks/serply.ts) with query, number of results, and API key fields, mirroring the serper block's shape. Uses the sharedSearchicon from@sim/emcn/iconsrather than adding a hand-drawn brand SVG.tools/registry.tsandblocks/registry-maps.ts(BLOCK_REGISTRY+BLOCK_META_REGISTRY, alphabetical).Serply is fully optional. No existing behavior changes for workflows that do not use it, and no
SERPLY_API_KEYis required anywhere.More on the API: https://serply.io/docs
Type of Change
Testing
apps/sim/tools/serply/search.test.ts(4 tests: headers/User-Agent, URL building, result mapping, empty-results case). All pass.bun run type-checkinapps/sim: 0 errors.tools/serper,tools/index.test.ts(164 tests) and all ofblocks/(66 files, 938 tests) pass unchanged.bun run check:api-validationpasses.bunx biome checkclean on all touched files.Checklist
Screenshots/Videos
N/A (no bespoke UI; the block renders through the standard block UI generated from its config)
Disclosure: I work with Serply. Happy to adjust scope, naming, or drop this
entirely if it isn't a direction you want for the project.