---
schema_version: "1"
id: 761a87195824c0b7486c2b081d7f3f9252ccd46d656682249ea49bd430bf5869
title: Quick Action API Considerations
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/case_feed_dev_guide/guides/quickactions/quickaction-api-considerations.md
canonical_url: https://developer.salesforce.com/docs/platform/case-feed-dev-guide/guide/quickaction-api-considerations.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 1a94dd274e92fa0287819b959e075476e5cb9c4e0f57edadc0aded2f5d55b905
products:
  - Publisher and Quick Action Developer Guide
  - Platform Developer Content
---

# Quick Action API Considerations

Before working with the Lightning Quick Action JavaScript API methods, review some considerations that might impact your implementation.

**tip:** The Lightning Quick Action JavaScript APIs can only interact with quick actions that are targetable on the page. Review the following support.

-   Targetable: An action that displays in the highlights panel, including the dropdown action overflow
-   Targetable: An action that displays in the publisher, including the More overflow
-   Targetable: An action that’s nested in an accordion component section or tab that’s expanded by default
-   Not targetable: An action that’s nested in an accordion component section or tab that’s not expanded by default*

    *The action becomes targetable after a user opens the accordion section or tab containing the action.


If you use the Lightning Quick Action JavaScript APIs in custom code in a Lightning app, the targeted quick actions must be visible on the page. If you target an action that isn’t visible on the page, it fails.

The Quick Action APIs work with most action types.

|Action Type|Supported?|Notes|
|-----------|:--------:|-----|
|Create a Record|Yes|Supported in all Lightning apps, on any object.|
|Custom Visualforce|Yes|Supported in all Lightning apps, on any object. To work with these action types, use the `getCustomAction` method. Other methods aren’t supported for this action type.|
|Flow|No|Results in error.|
|Log a Call|Yes|Supported in all Lightning apps, on any object.|
|Aura Component|Yes|Supported in all Lightning apps, on any object. To work with these action types, use the `getCustomAction` method. Other methods aren’t supported for this action type.|
|Send Email|Yes|Supported in all Lightning apps, on any object.|
|Update a Record|Yes|Supported in all Lightning apps, on any object.|

The `lightning:quickActionAPI` component supports utility popout. However, the `getCustomAction` method doesn’t work with utility popout yet. The Salesforce Classic Publisher APIs also support utility popout if you place them in a Visualforce page that’s used in the utility bar. The `customActionMessage` doesn’t support utility popout either.

The Quick Action APIs don’t support the following items.

-   Opportunity products
-   Knowledge articles
-   Crew Size field on the Service Crew object
-   Social quick action in the case feed publisher provided with Social Customer Service
-   Experience Cloud sites—the `lightning:quickActionAPI` component doesn’t work in Experience Cloud sites

