> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/scrollytelling/features/tableau-actions.md).
# Tableau actions
Make your story interactive by adding Tableau actions. This is the core part of this extension with which you can make your dashboard stand out. Here you can create a custom button which can be configured to trigger a specific or a series of tableau actions, like a highlight, or a filter. You can also change the visual with the help of a parameter-based switch.
Here you can see a list of actions which you can customize. Animations are basically filter or highlight actions which is triggered on a predefined time interval.
You can also configure a tableau action on scroll without a button. If you press the hamburger menu for the sections (the blocks ) you can see a pane with a tableau action section. there you can configure similar actions scroll without the need for a button. It is also important to configure "at what time instance you want to initiate the action" if the percentage is set to 30% that means the action will execute when 30% of that section is visible on the screen.
#### Setting up a Tableau action
ScrollyTelling offers various configurable tableau actions to enhance your story. The following sections help you to get started with tableau actions. The guide might not go through all the actions as the configuration part is similar. In the following sections, you can find steps to configure the parameter actions and the filter animations.
---
# 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.infotopics.com/scrollytelling/features/tableau-actions.md?ask=&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.