# Open Quick Action

## Overview

The "**Open Quick Action**" interaction lets you launch object-specific Salesforce Quick Actions directly from within a Dynamic Component. Instead of navigating to a record detail page, users can trigger Quick Actions contextually — enabling faster data entry and more streamlined workflows.

{% hint style="warning" %}

#### Important

This interaction **only supports Quick Actions created at the object level** (e.g., a custom action on Contact or Account). Global Actions are not supported, as Salesforce does not expose them through the APIs Avonni relies on.
{% endhint %}

***

## Configuration

To add this interaction, go to the **Properties Panel** of any supported Avonni component, navigate to **Interactions**, and select **Open Quick Action**

<figure><img src="/files/ZbycMFMmLnJAUkHdoqa4" alt="" width="317"><figcaption></figcaption></figure>

<table><thead><tr><th width="181.294921875">Property</th><th>Description</th></tr></thead><tbody><tr><td><strong>Target Name</strong></td><td>The specific element (e.g., a Header Action or Row Action) that triggers the interaction.</td></tr><tr><td><strong>Source Entity</strong></td><td>The API name of the object the Quick Action belongs to (e.g., <code>Contact</code>, <code>Account</code>, <code>Custom_Object__c</code>). When set, you can use just the Action API Name in the Quick Action API Name field without repeating the object prefix.</td></tr><tr><td><strong>Quick Action API Name</strong></td><td>The API name of the action to launch. Accepts either the short format (<code>ActionAPIName</code>, e.g., <code>SendEmail</code>) or the full format (<code>ObjectAPIName.ActionAPIName</code>, e.g., <code>Contact.SendEmail</code>) — both work. If you've already set a Source Entity, the short format is enough.</td></tr><tr><td><strong>Record ID</strong></td><td><em>(Optional)</em> The ID of the record the action should be associated with.</td></tr></tbody></table>

> **Where to find Quick Action API names:** Setup → Object Manager → \[Object] → Buttons, Links, and Actions

### Record ID (Optional)

Providing a Record ID gives the Quick Action the context it needs to operate correctly. This is required for actions like "Send Email" or "Log a Call."

**Common References**:

* `record:Id`: Uses the ID of the current page.
* `{!Datatable1.selectedRowsKeyValue}`: Uses the selected row from a table.
* `{!variableName}`: Uses a custom variable

### Prefilled Values (Optional)

Automatically populate fields in the Quick Action modal to save user time and ensure data consistency.

**Each prefilled value requires:**

1. **Field API Name**: The technical name of the field (e.g., `Subject`, `Status`).
2. **Value**: Can be a **Static string** ("Urgent"), a **Dynamic component value** (`{!accountName.value}`), or a **Resource variable**.

**Example Use Cases**:

* Set a Task **Subject** to "Follow-up: " + Account Name.
* Default a Case **Status** to "New."
* Auto-populate the **Related To** field with a specific Record ID.

***

## Quick Start Example: "Send Email" Button

1. **Create Action**: Add a Row Action to a Data Table titled "Send Email".
2. **Target Name**: Select `Send Email` from the dropdown.
3. **Source** Entity: Enter `Contact`.
4. **Quick Action API Name**: Enter `Contact.SendEmail`.
5. **Record ID**: Enter `{!Datatable1.selectedRowsKeyValue}`.

***

## Troubleshooting

<details>

<summary>The Quick Action doesn't open</summary>

* Verify the Quick Action API Name is correct — it is case-sensitive
* Confirm the Quick Action exists, is active in your org, and that the user has permission to access it
* Make sure you're using the `ObjectAPIName.ActionAPIName` format (e.g., `Contact.SendEmail`)
* Confirm the Source Entity field is filled in — this interaction requires an object-level action

</details>

<details>

<summary>Record ID not passing correctly</summary>

* Verify your data table's API Name matches what you used in the formula
* Check that a row is actually selected in the table
* Use the correct attribute (`.selectedRowsKeyValue` for single selection)

</details>

<details>

<summary>Prefilled values don't appear</summary>

* Verify that the field API names exactly match the Quick Action's field names
* Check that the fields are actually included in the Quick Action layout
* Ensure your value expressions are valid and return the correct data type

</details>

<details>

<summary>User sees an error when submitting the Quick Action</summary>

* This is typically a Salesforce validation error, not a configuration issue
* Check Salesforce validation rules and required fields
* Ensure pre-filled values meet field requirements

</details>

***

## Need More Help?

If you have questions about implementing Quick Action interactions for your specific use case, or if you encounter issues with Quick Action configuration, [don't hesitate to reach out](/dynamic-components/resources/contact-support.md).


---

# Agent Instructions: 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:

```
GET https://docs.avonnicomponents.com/dynamic-components/component-builder/interactions/other/open-quick-action.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.