> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/external-search.md).

# External Search

## Description

Applications can include the ability to look for all occurences of a search term in the application's Knowledge Center or an external website. Two LogicNets parts support the retrieval and presentation of this information:

* freetextsearch part is used with a LogicNets KnowledgeCenter database application. See [KC Search](https://support.logicnets.com/kc/logicnets.lns?_=KC\&topic_id=422) article for more information.
* external\_search part is used with an external source, such as a website built in Wordpress, or Wikipedia.

## Detailed Configuration/Visualization Documentation

The attached External Search pdf document provides detailed information about setting up the external search part.

## Example Project

The set up and use of these parts has many possible options both in terms of configuration and visualization of results. Download and install the [example project](/release-9/example-gallery/example-projects-for-parts/external-search-example-project.md) here.

## Attachments

* [External Search Configuration Visualization PDF.pdf](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/36lp2k-External-Search-Configuration-Visualization-PDF.pdf)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/external-search.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.