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.
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.
Configuration
To add this interaction, go to the Properties Panel of any supported Avonni component, navigate to Interactions, and select Open Quick Action

Target Name
The specific element (e.g., a Header Action or Row Action) that triggers the interaction.
Source Entity
The API name of the object the Quick Action belongs to (e.g., Contact, Account, Custom_Object__c). When set, you can use just the Action API Name in the Quick Action API Name field without repeating the object prefix.
Quick Action API Name
The API name of the action to launch. Accepts either the short format (ActionAPIName, e.g., SendEmail) or the full format (ObjectAPIName.ActionAPIName, e.g., Contact.SendEmail) — both work. If you've already set a Source Entity, the short format is enough.
Record ID
(Optional) The ID of the record the action should be associated with.
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:
Field API Name: The technical name of the field (e.g.,
Subject,Status).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
Create Action: Add a Row Action to a Data Table titled "Send Email".
Target Name: Select
Send Emailfrom the dropdown.Source Entity: Enter
Contact.Quick Action API Name: Enter
Contact.SendEmail.Record ID: Enter
{!Datatable1.selectedRowsKeyValue}.
Troubleshooting
The Quick Action doesn't open
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.ActionAPINameformat (e.g.,Contact.SendEmail)Confirm the Source Entity field is filled in — this interaction requires an object-level action
Record ID not passing correctly
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 (
.selectedRowsKeyValuefor single selection)
Prefilled values don't appear
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
User sees an error when submitting the Quick Action
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
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.
Last updated
Was this helpful?
