> For the complete documentation index, see [llms.txt](https://docs.flexikanban.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flexikanban.ai/standard-kanban/howtos-and-best-practices/how-to-configure-communication-between-kanbans.md).

# How to configure communication between Kanbans

There are two ways for kanbans to communicate:

* initialize a kanban with input variables, styles, and filters
* call Kanban API methods

### Input variables, initial filters and styles

[Input variables](https://docs.flexikanban.ai/composite-kanban/howtos-and-best-practices/how-to-pass-variables-between-parent-and-child-kanbans.md#input-variables) can be set:

* to a child kanban from the parent (composite kanbans)
* to any kanban by calling "Navigate to Kanban" API method
* to any kanban by following a properly constructed link

Initial [filters](https://docs.flexikanban.ai/standard-kanban/using-kanban/how-to-work-with-filters-and-orders.md) can be set on a kanban by calling "Navigate to Kanban" API method.

Initial CSS Styles can be set on the kanban container by following the properly constructed link.

### Kanban API methods

Kanbans have API methods allowing interactions. The following [Kanban API methods](https://docs.flexikanban.ai/standard-kanban/using-kanban/how-to-use-kanban-api-actions.md) can work with kanbans specified by their IDs or API names:

* Refresh Kanbans
* Refresh Columns
* Show Columns
* Hide Columns
* Refresh Card Layout
* Open Kanban
* Update Variables


---

# 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://docs.flexikanban.ai/standard-kanban/howtos-and-best-practices/how-to-configure-communication-between-kanbans.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.
