> 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/how-to-create-an-interaction-to-a-record-page.md).

# How to create an interaction to a record page

## Overview

This guide shows you how to easily add "clone," "edit," and "view" buttons to your Salesforce records using Avonni components. You'll learn how to make these buttons work in different ways, like:

* **Direct Buttons:** Add them right on the record page for quick access. For example, a salesperson could edit or view an opportunity with one click.
* **List Actions:** Place the buttons next to items in a list. This makes it easy to duplicate contacts quickly, for instance.
* **Table Actions:** Embed the buttons in rows of data tables. This is perfect for project management, letting users edit project details directly.

## **How to Link to Records**

In this example, we set up an interaction that takes you directly to a specific account's page.

1. **Create the button:** First, make the button you want to use for the link (e.g., a "Edit" button in your data table).
2. **Go to Interactions:** Click on the "Interactions" tab.
3. **Set up the Interaction:**
   * **Target Name:** Choose the name of the button you just created.
   * **Type:** Select "Navigate."
   * **Page Reference Type:** Choose "Record Page."
   * **Object API Name:** Select the type of record you want to link to (e.g., "Contact," "Account").
   * **Record ID:** Choose the field that holds the unique ID of the record.
   * **Action Name:** Pick the action you want the button to trigger ("clone," "edit," or "view").

<figure><img src="/files/YqQZkwSvJ8ujumztlnzt" alt=""><figcaption></figcaption></figure>

When you click the button, it will take you directly to the correct record page in Salesforce.


---

# 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://docs.avonnicomponents.com/flow/tutorials/interactions/how-to-create-an-interaction-to-a-record-page.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.