> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/data/collections/automatic-links.md).

# Automatic Links

An automatic link can be added to any non-Noloco data source, such as Google Sheets or Airtable.

It allows you to add a custom link to another table/record from an existing record and then automatically sync that value with a lookup value.

For example:

If you have two spreadsheets, one named `Software` and one named `Suppliers`

The `Software` sheet has a `Supplier Name` column and the `Supplier` sheet has a `Name` column. But there's no link between them (because it's a spreadsheet)

You can define a new Automatic link field on the `Software` table: `Supplier` Then you can make it automatically link when `Supplier Name` = `Supplier`

![Automatic link between Supplier and Supplier Name](/files/lHtv2eVLJZE7kVkCkYY4)

Automatic links are bi-directional, so if you then update the linked field on a record (say the Supplier field), Noloco will automatically prefil the `Supplier Name` field in your spreadsheet with the correct value.

This makes it much easier to work with, as it introduces better filters, better views and better permissions.


---

# 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://guides.noloco.io/data/collections/automatic-links.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.