# n8n

> Add web search, agentic search, news, page retrieval, sitemap discovery and trending topics to n8n workflows with the verified n8n-nodes-search1api community node.

Canonical URL: https://s1.dev/docs/integrations/n8n

`n8n-nodes-search1api` is a [verified n8n community node](https://n8n.io/integrations/) that gives n8n workflows live web access through Search1API — web search, agentic search, news search, readable page retrieval, sitemap discovery, and trending topics, all through the native n8n node interface.

> **info:** **Verified status:** `n8n-nodes-search1api` has passed n8n's automated and manual review and is listed in the [official n8n community node catalog](https://n8n.io/integrations/).

## Install

In n8n, install the community node `n8n-nodes-search1api` from **Settings → Community Nodes**, or from the command line:

```bash
npm install n8n-nodes-search1api
```

Then restart n8n. The node appears under **Search1API** in the node panel.

## Credentials

1. Create a key in the [Search1API dashboard](https://app.s1.dev).
2. In n8n, create a **Search1API API** credential and paste the key.
3. Test the credential — the test calls the read-only `/usage` endpoint and does not run a search.

Keep API keys in n8n credentials, never in workflow fields or exported workflow JSON.

## Operations

| Operation | What it does |
| --- | --- |
| **Web Search: Search** | Search the live web with Google, Bing, DuckDuckGo, Reddit, GitHub, YouTube, arXiv, Wikipedia and other sources |
| **Agentic Search: Ask** | Describe the research task with only Query; Search1API chooses sources and filters (five credits, 45-second timeout) |
| **News Search: Search** | Search current news from Bing, Google, DuckDuckGo, Yahoo, Hacker News or Reuters |
| **Page: Retrieve** | Retrieve readable content from a public URL |
| **Sitemap: Discover** | Discover a site's sitemap URLs or all public links |
| **Trending Topic: Get Many** | Get current GitHub or Hacker News trends |
| **Usage: Get** | Inspect API-key usage over a selected period |

The Search1API node can also be used as an n8n AI tool inside AI-agent workflows.

Agentic Search sends only **Query**, including when switching an existing Web
Search node with saved filters. Its response preserves `intent`, result `source`
and `relevance`, and optional `errors`. See [Ask](https://s1.dev/docs/basic/ask).

## Tips

For a focused lookup use **Web Search** with five to ten results. For deeper research, increase the result count and set **Crawl Results** to retrieve the full text of the most relevant results.

Use a vertical source when the workflow has a clear target:

- **GitHub** for repositories and code projects
- **Reddit** for community discussions
- **ArXiv** for research papers
- **YouTube** for videos
- **WeChat** or **Bilibili** for Chinese-language content

Every operation is read-only. Search results include source URLs that can be passed to later workflow steps.

## Credits

Search and news requests cost one credit each; crawling a page costs one additional credit per successfully crawled page. Agentic search costs five credits per request. New accounts receive 100 credits without a credit card. See [Credits and limits](https://s1.dev/docs/essentials/credits-and-limits) for current rates.

## Search filters and result fields

Version **0.2.0** supports all 19 [search engines](https://s1.dev/docs/basic/search) and all six
[news sources](https://s1.dev/docs/basic/news), including Bing China, Yandex, Grokipedia, and Reuters.
`time_range` supports `day`, `week`, `month`, and `year`; `page` supports search
pagination. These filters apply to search/news; agentic search accepts only `query`.

Engine-specific result fields live in optional `metadata`: GitHub search exposes
`metadata.kind`, `metadata.stars`, `metadata.language`, and `metadata.num_comments`;
Hacker News search exposes `metadata.story_url`, `metadata.points`, and
`metadata.num_comments`. Optional `published_date` stays at the result top level.
The response-level `searchParameters` describes the executed request. These paths
apply to search/news; [trending](https://s1.dev/docs/advanced/trending) keeps its separate response shape.

## Source

[github.com/superagents-lab/n8n-nodes-search1api](https://github.com/superagents-lab/n8n-nodes-search1api)
· [npm](https://www.npmjs.com/package/n8n-nodes-search1api)
· [n8n community nodes](https://docs.n8n.io/integrations/community-nodes/)