Serper Google Search: Serper action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Query q	string	Required	Query (required)
Country gl	string	Optional	us, in, uk
Language hl	string	Optional	Language
Num Results num	string	Optional	Num Results

Sample request

{
  "q": "{{trigger.q}}",
  "gl": "us, in, uk",
  "hl": "{{trigger.hl}}",
  "num": "{{trigger.num}}"
}

Returns

{
  "organic": [
    {
      "link": "https://example.com",
      "title": "Title",
      "snippet": "..."
    }
  ],
  "answerBox": {
    "answer": "..."
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Serper Google Search.

What does the Serper Google Search action do in Serper?

Standard Google SERP — organic results, knowledge panels, people-also-ask, related searches, ads. For RAG-style "agent grounds answer in current search results" workflows.

What inputs does Serper Google Search require?

Required: Query. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Serper returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Serper Google Search support batch operations?

Yes. Run Serper Google Search inside a Loop node to process arrays. Tiny Command handles Serper's rate limits automatically so you don't have to throttle manually.

More actions