Serper
Google Search API powered by Serper - web, image, video, news, shopping, places, scholar, autocomplete, maps, patents, lens search and webpage scraping via the Serper REST API. All nodes support two auth modes: a shared Connect session via client ID, or direct API key credentials per node.
| Namespace | Robomotion.Serper |
| Version | 1.1.0 |
| Category | Artificial Intelligence, Dev Tools |
| Nodes | 15 |
Nodes
| Node | Description |
|---|---|
| Connect | Opens a connection to Serper and returns a Client ID. |
| Disconnect | Closes a Serper connection. |
| Web Search | Web Search — see the properties below. |
| Image Search | Image Search — see the properties below. |
| Video Search | Video Search — see the properties below. |
| News Search | News Search — see the properties below. |
| Shopping Search | Shopping Search — see the properties below. |
| Places Search | Places Search — see the properties below. |
| Scholar Search | Scholar Search — see the properties below. |
| Autocomplete | Autocomplete — see the properties below. |
| Maps Search | Maps Search — see the properties below. |
| Patents Search | Patents Search — see the properties below. |
| Lens Search | Lens Search — see the properties below. |
| Scrape Webpage | Scrape Webpage — see the properties below. |
| Toolkit | Exposes this package's operations to an AI Agent as a single tool. |
Connecting
This package has a Connect node. Run it once at the start of your flow; it returns a Client ID that the other nodes take as input. Pair it with Disconnect so the connection is released when the flow ends.
Credentials belong in a Vault rather than typed into the node.
AI Agent tools
14 of these nodes are exposed as tools an AI Agent can call directly:
Connect, Disconnect, Web Search, Image Search, Video Search, News Search, Shopping Search, Places Search, Scholar Search, Autocomplete, Maps Search, Patents Search, Lens Search, Scrape Webpage.
Generated from the package spec that the Flow Designer itself loads, so the node list and every property below match the version above exactly.
It does not yet include worked examples or service-specific guidance — those are written by hand, and a plausible-sounding guess in a reference page is worse than an honest gap. If you build something useful with this package, the community is the place to share it.