> 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/integrations/external-collections-with-apis/magic-text-in-external-collections.md).

# Magic Text in External Collections

When setting up your external collections, you can use magic text in the base URL and/or as the value of any headers or query params.

![](https://3467607506-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LhGHkPsv15svPIU5I7C%2F-MRLQdRKoLka35IIGyp3%2F-MRLRyHRdWI_Xa0vlhYs%2Ftest%20\(7\).gif?alt=media\&token=d42e5f9b-52c4-4b60-a5f0-fb0a43cda03f)

Magic Text in external collections lets you choose any properties of the logged in user as part of the API request to your external collection.  This way, the external data that is displayed to your users when the log in to your app is just the data that is specific to them.

When you add Magic Text to your External Collections, you'll also need to give an example value.  The value only used during the final step of the External Collection set up, when Adalo tests the connection and determines the properties of the External Collection.


---

# 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://help.adalo.com/integrations/external-collections-with-apis/magic-text-in-external-collections.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.