SearchAPI
SearchAPI.io integration for web search and SERP data. Provides Google Search, Google Images, Google News, Google Videos, Google Maps, Google Shopping, Google Scholar, Google Jobs, Google Trends, Google Autocomplete, YouTube Search, and Bing Search. All nodes require a Connect session with a SearchAPI.io API key.
| Namespace | Robomotion.SearchAPI |
| Version | 1.1.0 |
| Category | Analytics, Dev Tools |
| Nodes | 15 |
Nodes
| Node | Description |
|---|---|
| Connect | Opens a connection to SearchAPI and returns a Client ID. |
| Disconnect | Closes a SearchAPI connection. |
| Google Search | Google Search — see the properties below. |
| Google Images | Google Images — see the properties below. |
| Google News | Google News — see the properties below. |
| Google Videos | Google Videos — see the properties below. |
| Google Maps | Google Maps — see the properties below. |
| Google Shopping | Google Shopping — see the properties below. |
| Google Scholar | Google Scholar — see the properties below. |
| Google Jobs | Google Jobs — see the properties below. |
| Google Trends | Google Trends — see the properties below. |
| Google Autocomplete | Google Autocomplete — see the properties below. |
| YouTube Search | YouTube Search — see the properties below. |
| Bing Search | Bing Search — 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, Google Search, Google Images, Google News, Google Videos, Google Maps, Google Shopping, Google Scholar, Google Jobs, Google Trends, Google Autocomplete, YouTube Search, Bing Search.
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.