FetchSERP

Interact with the FetchSERP API

Actions20

Overview

This node integrates with the FetchSERP API to retrieve various types of search engine results and domain-related data. Specifically, the "Get Domain Info" operation fetches detailed information about a given domain, such as its metrics or attributes available via the API.

Common scenarios for this node include:

  • SEO analysis workflows where users want to gather domain insights automatically.
  • Marketing automation pipelines that enrich leads or prospects with domain data.
  • Competitive research setups to monitor domain statistics regularly.

For example, a user can input a domain name like "example.com" in the query parameters, and the node will return structured information about that domain from the FetchSERP service.

Properties

Name Meaning
Query Parameters (JSON) JSON object containing query parameters for the API call. For "Get Domain Info", typically includes the "domain" key with the domain name as value. Example: {"domain":"example.com"}

Output

The node outputs an array of items, each with a json property containing the response from the FetchSERP API for the requested operation.

For the "Get Domain Info" operation, the json output contains detailed domain information as returned by the API. This may include domain metrics, registration details, traffic estimates, or other domain-specific data depending on the API's response structure.

No binary data is output by this node.

Dependencies

  • Requires an API key credential for the FetchSERP service to authorize requests.
  • The base URL defaults to https://www.fetchserp.com but can be overridden in credentials.
  • The node makes HTTP GET requests to the /api/v1/domain_infos endpoint with the provided query parameters.

Troubleshooting

  • Invalid or missing API token: If the API key is incorrect or missing, the node will throw an authorization error. Ensure the API key credential is correctly configured.
  • Malformed JSON in Query Parameters: The "Query Parameters (JSON)" field must contain valid JSON. Invalid JSON will cause parsing errors.
  • Unknown operation error: If the operation parameter is set incorrectly, the node throws an error indicating the operation is unknown.
  • API request failures: Network issues or API downtime can cause request failures. The node supports continuing on fail if enabled, returning error messages in the output JSON.

Links and References

Discussion