> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/interactions.md).

# Interactions

- [Enabling auto-refresh for queries after the Flow Dialog ends](https://docs.avonnicomponents.com/flow/tutorials/interactions/enabling-auto-refresh-for-queries-after-the-flow-dialog-ends.md)
- [Add a New Opportunity button that opens a prefilled record form](https://docs.avonnicomponents.com/flow/tutorials/interactions/how-to-create-an-interaction-to-navigate-to-an-object.md): Add a New Opportunity button to a Data Table that opens the standard new record form with Stage and Type already filled in, so reps skip retyping defaults.
- [Send users to an external site or another Lightning page](https://docs.avonnicomponents.com/flow/tutorials/interactions/send-users-to-an-external-site-or-another-lightning-page.md): Link Data Table header buttons to a website, an app tab or the Home page, and choose where the External URL opens, a new tab or the current window.
- [Open records in Console tabs and subtabs](https://docs.avonnicomponents.com/flow/tutorials/interactions/open-records-in-console-tabs-and-subtabs.md): In a Lightning Console app, open the opportunity a rep clicks in a labeled subtab next to the flow, so the pipeline list stays one click away.
- [Open a record from a Data Table row](https://docs.avonnicomponents.com/flow/tutorials/interactions/how-to-create-an-interaction-to-a-record-page.md): Add View and Edit row actions to a Data Table of opportunities so a sales rep opens the record page or its edit form straight from the row they clicked.
- [How to create an interaction to open another flow](https://docs.avonnicomponents.com/flow/tutorials/interactions/how-to-create-an-interaction-to-open-another-flow.md)
- [How to pass an Input Variable from One Flow to Another](https://docs.avonnicomponents.com/flow/tutorials/interactions/how-to-pass-an-input-variable-from-one-flow-to-another.md): Pass an input variable from one screen flow to another with the Open Flow Dialog interaction, for example to show an Account's Contacts from a table row.
- [Expression Syntax in Interactions](https://docs.avonnicomponents.com/flow/tutorials/interactions/expression-syntax-in-interactions.md)
- [How to setup an Open Flow Panel interaction](https://docs.avonnicomponents.com/flow/tutorials/interactions/how-to-setup-an-open-flow-panel-interaction.md)


---

# 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.avonnicomponents.com/flow/tutorials/interactions.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.
