> 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/dashboard-interface/importing-graph-template.md).

# Importing Graph/Template

With the IDE, you can first create your graph and export it as .GLQ file, then, you can either select a template from the lists and deploy in on the dashboard interface or the .GLQ file that you generated with the graph IDE over `Save graph` in the `File` Menu.

![](/files/cTKx5l3UWeoHF7kZBQUr)

Once you are on the dashboard interface you just need to import your file and execute it over `Deploy a New Graph`: One unique hash and an alias name will be set to recognize your graph. You will then be in control of the graph state / cycle costs and be able to view logs of executions, also later on we will add stats with specific information of the execution.

![](/files/0KdiDhyeisClfK7V7nye)


---

# 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/dashboard-interface/importing-graph-template.md?ask=<question>&goal=<endgoal>
```

`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.