> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/component-basics/inserting-dynamic-text.md).

# Magic Text

Magic Text allows you to pull information directly from your Adalo Database dynamically.

## Learn About Magic Text

Magic Text is a foundational aspect of Adalo that you must understand in order to create a dynamic and engaging app that is designed well & performant. Magic Text pulls data from the database to display in the app without replicating designs for each record item in the database.

Magic Text is truly :sparkles:Magic:sparkles:

{% embed url="<https://youtu.be/JBqBt_0Kb80>" %}

In components that display text, in the toolbar below the text box, you will see the Magic Text icon:<img src="https://3467607506-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LhGHkPsv15svPIU5I7C%2F-LmeRAFvPkKA_NboUmjo%2F-LmeTTt160m0ufbLUoTL%2FScreenshot%202019-08-19%20at%2010.23.11%20AM.png?alt=media&amp;token=43c117e9-653b-4df1-a482-f08ca2a374d4" alt="" data-size="line"> Clicking this will show you what Magic Text you can add to your component.

Magic Text will automatically be replaced with text from your App's Database.  For example, if your screen is showing details for a Trip, you can use Magic Text to show the Trip's Name.

You can display Magic Text for the Logged in User, any item in a list, or any list item that links to the screen you're on.

For example, if you have a travel app that displays options for trips, and you want the user to be able to click on a particular trip and open a screen with more detailed information on that trip:&#x20;

1. Insert text boxes, images, or other components
2. Select the Magic Text icon from your text box's toolbar
3. Choose the database Collection and the Property you want to add as Magic Text
4. Click on 'Preview' to make sure the Magic Text works

![](https://3467607506-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LhGHkPsv15svPIU5I7C%2F-MRvBLyL8upQkm5Yj3sk%2F-MRvDM8r85NdOmhijfZp%2FTrip%20Example.gif?alt=media\&token=c629153a-71f0-4551-82ff-92253d308f37)

![Step 4](https://3467607506-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LhGHkPsv15svPIU5I7C%2F-Lio6BAF4oHQCerWDo4_%2F-LioAWe66HytJ5Ri3T6V%2FFinal%20GIf%202%20Magic%20Text.gif?alt=media\&token=3e4f1b62-4c9c-4078-8b0a-ce17d89caf35)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.adalo.com/component-basics/inserting-dynamic-text.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 `build a script that syncs our docs to a CMS` 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.
