Loading

Account Engagement Engagement Studio External Actions Best Practices

Publiseringsdato: Sep 30, 2025
Beskrivelse
With the Winter '23, you can use External Actions to seamlessly integrate any third-party app with Engagement Studio. Automatically register prospects for webinars, send SMS texts, and more.

This article outlines some best practices and considerations for working with External Actions. 
Løsning
External Actions
  • Although API names must be unique, you can have multiple actions with the same record name. To avoid confusion in Engagement Studio, use clear naming conventions. 
  • Deleting External Actions is permanent. Actions aren't sent to the Salesforce recycle bin and can't be recovered.
  • Deleting an action can affect Engagement Studio programs where it's being used.
  • Disabling ‘Active in Automations’ on the Marketing App Extension or the External Action results in the step being marked as ‘Inactive’ in an Engagement Studio program. 
  • Do not remove the properties, view, or required sections from the schema. The Properties and View sections can be empty or have empty components, but removing the sections completely can break your action in Engagement Studio.
  • Do not remove any fields from the Required section. You can add fields to the section, but removing fields can break the action.
  • Do not edit the Parameters field. Editing this field can break your action. 

Invocable Actions
  • To configure an action that creates a new contact in Salesforce with an associated account, use the NewContact invocable action and supply a context ID like an account ID.  When the action executes, it creates a new contact with the associated account. 
  • To ensure the best performance, include retry conditions in your invocable actions. Including retry logic provides protection when actions fail or time out for temporary reasons like too many concurrent requests to the third-party.
  • For proper execution, the B2BMA User must have access to the flow and/or APEX classes that define your invocable action.

Packaging
  • If you're creating a managed package, don't mark the marketing app extension or action type as 'Active in Automations'. Instead, let the installer activate the component as needed for their business use case. 
  • Extensions you install from a managed package can’t be edited. We also recommend you don’t add external actions or activities to extensions installed from a managed package.
  • You can add activities to extensions that you own via Tooling API.
Knowledge-artikkelnummer

000393471

 
Laster
Salesforce Help | Article