Skip to content
Nappai Documentation

Google Serper API

The Google Serper API component lets you ask Google for up-to‑date information directly from your Nappai dashboard. You type a question or keyword, choose how many results you want, and the component returns a list of short snippets that you can use in your workflow.

How it Works

When you run the component, it sends your query to the Serper.dev Google Search API. Serper handles the actual Google search and returns the top results. The component then takes those results, keeps only the “organic” (normal search) items, and packages each one as a Data object that contains the full result and a short snippet of text. It also creates a Tool that can be used by other parts of Nappai to perform the same search automatically.

Inputs

This component requires a Google Serper Api credential.

  1. Configure the credential in Nappai’s credentials section.
  2. Select that credential in the component’s “Credential” field.

Input Fields

  • Input: The search query you want to ask Google.
  • Number of results: How many search results you want to retrieve (default is 4).

Outputs

  • Data: A list of Data objects, each containing a search result and its snippet.
  • Tool: A reusable tool that can perform the same Google search from other components.

Usage Example

  1. Drag the Google Serper API component onto your workflow.
  2. In the Credential field, choose the Google Serper Api credential you set up.
  3. Enter a query in the Input field, e.g., “latest AI trends”.
  4. Set Number of results to 4.
  5. Run the workflow.
  6. The component will output a list of 4 Data objects you can feed into a text summarizer, a notification, or any other downstream component.
  • Google Custom Search API – Search Google using your own custom search engine.
  • Bing Search API – Retrieve results from Microsoft Bing instead of Google.
  • Web Scraper – Pull data from a specific webpage instead of a search query.

Tips and Best Practices

  • Keep the API key secure; never expose it in public workflows.
  • Use concise queries to get the most relevant results.
  • Limit the number of results to avoid unnecessary API calls and keep response times fast.
  • Combine the Data output with a summarizer to create quick briefs for stakeholders.

Security Considerations

  • Store the Serper API key in Nappai’s credential store, not in the workflow itself.
  • Ensure that only authorized users can edit the component’s credential field.
  • Monitor API usage to detect any unexpected spikes that could indicate misuse.