> For the complete documentation index, see [llms.txt](https://docs.graphlinq.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graphlinq.io/dev-tooling/blocks/common/entry-point.md).
# Entry Point
The Entry Point block is the starting point of every graph in the GraphLinq IDE. When a graph is executed, the flow of execution begins at the Entry Point block. This block serves as the entryway into the graph's logic and acts as the initial trigger for the entire workflow.
In the example below, the Entry Point block is connected to other blocks, creating a sequence of operations that will be executed when the graph starts:
When the graph is run, the execution starts at the Entry Point block, and the logic flows through the connected blocks in the order they are linked. The Entry Point block allows us to define the sequence of actions and operations to be performed when the graph is executed.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.graphlinq.io/dev-tooling/blocks/common/entry-point.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
