Is your proposal related to a problem?
ToolJet ships data-source plugins for many external services, but none for a SERP or web-search API. A builder who wants live web search results (organic results, news, scholar, and similar) inside a ToolJet app currently has to fall back on a generic REST call and parse the raw response by hand.
Describe the solution you'd like
Add a Serply plugin as an optional marketplace data source. Serply is a SERP API (https://serply.io, docs at https://serply.io/docs). The plugin exposes a small set of query operations that return normalized JSON, so a builder can drop search results straight into a table or transform without writing HTTP glue.
It follows the existing plugin structure and is fully optional: it does nothing unless a user adds the plugin and supplies their own Serply API key. No existing behavior changes for anyone who does not use it.
Describe alternatives you've considered
Using the REST API plugin against a raw Serply endpoint works, but it leaves every builder to build the request and reshape the response themselves. A first-class plugin gives typed operations and a consistent result shape, matching how other data sources are exposed in ToolJet.
If the feature is approved, would you be willing to submit a PR?
Yes. I have a working implementation already open as #17552 and am happy to align it with this issue and your review.
Disclosure: I work with Serply.
Is your proposal related to a problem?
ToolJet ships data-source plugins for many external services, but none for a SERP or web-search API. A builder who wants live web search results (organic results, news, scholar, and similar) inside a ToolJet app currently has to fall back on a generic REST call and parse the raw response by hand.
Describe the solution you'd like
Add a Serply plugin as an optional marketplace data source. Serply is a SERP API (https://serply.io, docs at https://serply.io/docs). The plugin exposes a small set of query operations that return normalized JSON, so a builder can drop search results straight into a table or transform without writing HTTP glue.
It follows the existing plugin structure and is fully optional: it does nothing unless a user adds the plugin and supplies their own Serply API key. No existing behavior changes for anyone who does not use it.
Describe alternatives you've considered
Using the REST API plugin against a raw Serply endpoint works, but it leaves every builder to build the request and reshape the response themselves. A first-class plugin gives typed operations and a consistent result shape, matching how other data sources are exposed in ToolJet.
If the feature is approved, would you be willing to submit a PR?
Yes. I have a working implementation already open as #17552 and am happy to align it with this issue and your review.
Disclosure: I work with Serply.