Overview
This node enables searching various types of content using the Naver Search API. It supports multiple search categories such as news articles, blog posts, web documents, images, shopping items, books, and local places. Users can specify their search query, control the number of results returned, set the starting position for pagination, and choose sorting options where applicable.
Common scenarios include:
- Retrieving the latest news or blog posts about a topic.
- Searching for images related to a keyword.
- Finding shopping items or books matching a query.
- Looking up local places by region name.
Practical example: A marketing team could use this node to gather recent news articles and blog posts about their brand or competitors, helping them monitor public sentiment and trends.
Properties
| Name | Meaning |
|---|---|
| Search Type | The category of content to search. Options: News, Blog, Web, Image, Shopping, Book, Local. |
| Query | The search term or phrase. For most types, enter keywords; for Local, enter a region name. |
| Display Count | Number of results to return (minimum 1, maximum 100). |
| Start Position | Starting index for search results pagination (minimum 1, maximum 1000). |
| Sort | Sorting order of results (only for News and Blog): Sim (Similarity) or Date (most recent). |
Output
The node outputs an array of JSON objects, each representing the search result for one input item. Each output JSON contains:
searchType: The type of search performed (e.g., "news", "image").query: The original search query string.total: Total number of results available from the API.start: The starting position of the current batch of results.display: Number of results returned in this response.items: An array of result items, structure varies depending on the search type but generally includes metadata like title, link, description, etc.
No binary data is output by this node.
Dependencies
- Requires an API key credential with client ID and client secret for authenticating requests to the Naver Search API.
- Uses the Axios HTTP client library to make REST API calls.
- Network access to
https://openapi.naver.commust be available.
Troubleshooting
- Authentication errors: If the API credentials are invalid or missing, the node will fail. Ensure that valid client ID and secret are configured.
- Rate limiting: The Naver API may limit the number of requests per time period. If you receive errors indicating rate limits, reduce request frequency or check your API quota.
- Invalid parameters: Providing unsupported values for properties like
searchType,sort, or out-of-range numbers fordisplayandstartmay cause errors. Validate inputs before execution. - Empty results: If no items are returned, verify the query terms and ensure the selected search type supports the query format.