---
schema_version: "1"
id: 69d2d188b60adb264621358faa6fded758fc6d2f47888bcaae958393ddf11a1e
title: Considerations for Mobile Builder for Agentforce (Beta)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/salesforce_app_agentforce_builder_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.salesforce_app_agentforce_builder_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 21b8b43c3043ad9cdb110d70b9eb9be58bbc6a7ea574074866fd914889ca9088
description: Keep these limitations and known issues in mind when using this feature.
products:
  - Mobile App Mobile App Mobile App
  - Cross Cloud Cross Cloud Cross Cloud
release: "264"
---
# Considerations for Mobile Builder for Agentforce (Beta)

Keep these limitations and known issues in mind when using this feature.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-salesforce_app-264-0-0-production-enus/cb8c7d7a-5f86-49c5-967c-c4d5cb2f80b6/images/icon_important.png)

Important Mobile Builder for Agentforce is a pilot or beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the Customer's sole discretion.

## Apex Action Requirements

  
| Limitation | Impact | Recommendation |
| --- | --- | --- |
| Nested or object-type output fields aren't supported. | The builder shows the field name as selectable, but mobile devices don't show anything for that field. | Use only simple field types in your Apex output (`String, Integer, Boolean, Decimal`). Keep the output flat, without any nested objects. |
| Only Apex invocable actions that return a list are supported. | Apex actions that return a single flat object (not wrapped in a list) can't be configured in the builder. | Structure all Apex actions to return a list, even when only one item is expected. |
| The **Show in Conversation** setting is ignored. | If you don't select **Show in Conversation** on the output variable, the action shows in the builder but can't be saved correctly. | Always select **Show in Conversation** on your Apex output variable. |

## Display

  
| Limitation | Impact | Workaround / Guidance |
| --- | --- | --- |
| A red error may appear when adding an external image asset. | If your org doesn't have a third-party digital asset manager configured, the image selector shows a misleading error even though the image was added successfully. | Disregard the error. The image is added to your customization successfully. |

## Other Considerations

- Deploying an Apex class with `@InvocableMethod` isn't sufficient on its own. After the Apex class is deployed, register it as an Agentforce Action of type Apex:
    
    1. From Setup, enter Agentforce Assets in the Quick Find box and select it.
    2. Click the Actions tab, then click New Agent Action.
    3. In the modal, set Reference Action Type to `Apex`.
    4. Set Reference Action Category to `Invocable Methods`.
    5. Set Reference Action to your Apex class.
    6. Click Next and complete the configuration.
    
    The Agentforce SDK responds with Agentforce Actions, which can be of different types (for example, Apex or Flow), so an unregistered Apex class won't be surfaced by the agent or appear as a selectable action in Mobile Builder for Agentforce.
- Image URLs using authentication don't display for guest users. Make sure image URLs are publicly accessible. Add CMS images in a public channel. For external image links, add the domain to Trusted URLs in Setup.
- Only one mobile customization is allowed per Agentforce action, and it is applied to all users accessing the Salesforce mobile app and external apps using the Agentforce Mobile SDK. To make changes, edit the existing customization.
- An in-builder preview isn't available in beta. Publish your customization and test on a mobile device to verify the layout.
- Only top-level fields from your Apex action's output appear as selectable fields in the builder. Keep the output flat.
- References to nested data fields aren't supported in beta.
- Mobile customizations apply to how Agentforce action responses are displayed only. User input isn't customizable.