> For the complete documentation index, see [llms.txt](https://water-strategy.gitbook.io/waterstrategy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://water-strategy.gitbook.io/waterstrategy/espanol/conceptos-basicos-de-modelado/node-types/water-transport/link-node.md).

# Link Node

## Descripción general

El **link node** representa un enlace en el sistema de agua u otro punto de interés donde se asigna una restricción de flujo máxima o mínima o una prioridad de asignación. Tenga en cuenta que en Pywr no se pueden asignar restricciones de flujo a los bordes (enlaces) y, por lo tanto, los nodos de enlace se utilizan con frecuencia para este propósito. [API Referencia](https://pywr.github.io/pywr-docs/master/api/generated/pywr.nodes.Link.html).

## Atributos principales

\_flujo

<table><thead><tr><th width="181.33333333333331">Nombre</th><th width="342">Descripción</th><th>Necesario</th><th></th><th></th></tr></thead><tbody><tr><td>penalización de asignación</td><td>El costo por unidad fluye a través del nodo</td><td>Opcional</td><td></td><td></td></tr><tr><td>máximo_</td><td></td><td></td><td></td><td></td></tr><tr><td>flow</td><td>La restricción de flujo máxima del nodo</td><td>Opcional min</td><td>La restricción de flujo mínima del nodo</td><td>Opcional</td></tr></tbody></table>

## Ejemplos

próximamente...


---

# 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://water-strategy.gitbook.io/waterstrategy/espanol/conceptos-basicos-de-modelado/node-types/water-transport/link-node.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.