Talordata SERP Dify Plugin

Talordata SERP Dify Plugin exposes Talordata SERP API as Dify tools.

Credentials

Configure a Talordata SERP API Key in the plugin provider settings.

Use an API key with this shape:

Do not use a Talordata login JWT token. Login JWT is only for Talordata dashboard APIs such as quota, token management, statistics, and Playground schema.

Actions

This plugin exposes one Dify action for each enabled SERP engine in
, plus a raw request action
for advanced use.

Generated actions include:

Google: , , , , , , , , and the other enabled Google engines in the schema directory
Bing: , , , , ,
Other engines: ,
Advanced:

is not exposed because its source schema is currently disabled. is exposed separately for the engine.

SERP Engine Actions

Calls:

Each generated action fixes its own parameter, validates the schema
query field, and exposes the common SERP parameters directly in the Dify node.
Use when you need to pass a custom override
object for advanced request parameters.

Image actions return normalized image result fields when possible. Web/news
actions return normalized web result fields when possible. Complex engines such
as hotels, flights, finance, maps, and product details return the raw upstream
payload in a stable wrapper.

Bing Image Search Compatibility

The original action name is preserved for existing Dify
workflows.

Fixed parameter:

Supported parameters:

Raw SERP Request

Use this for advanced engines and parameters.

Input example:

Usage

Install the plugin package in Dify.
Configure the provider credentials with a Talordata SERP API key.
Add a search tool, such as Bing Search or Google Search, to a workflow or agent.
Map the user query to the tool's query field, for example .
Run the workflow and consume the returned structured JSON results.

Example Bing Search input:

Use when advanced engine-specific parameters are required:

Limitations

Search availability, freshness, latency, quota, and rate limits depend on the Talordata SERP API and the user's Talordata account plan.
Some vertical engines return complex upstream payloads. The plugin wraps those responses in a stable JSON object instead of flattening every field.
The plugin does not store Talordata dashboard login JWT tokens and does not require them for SERP requests.
Avoid placing unnecessary sensitive personal data in search queries.

Support

For issues with the Dify plugin package, report an issue in the GitHub repository where this plugin package is maintained.

For Talordata SERP API account, quota, or API key issues, contact Talordata support through the support channel listed in your Talordata account or dashboard.

Development

Install dependencies:

Run tests:

Regenerate schema-backed actions after SERP schema changes:

Package:

GitHub Release Installation

Dify's "Install from GitHub" flow discovers formal plugin versions from GitHub
Releases. After packaging, publish a release whose tag matches the plugin
version in , and attach the generated file as a
release asset.

For version , this creates or updates the release in
with attached. The script
requires or in the current PowerShell session.

Development Notes

The generated tools are based on Talordata SERP schema files. The internal
Talordata services that define or consume those schemas include: