Identifies the configurations of a connected app and creates an identical external client app to replace it. After connected app migration, the connected app remains in the App Manager list but is read only.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Foundations, or Agentforce 1 or Einstein 1 Editions |
| User Permissions Needed | |
|---|---|
| See Common User Access for Standard Agent Actions. | |
Action Details
| API Name | MigrateConnectedApp |
| Reference Action Type | Standard Action |
| Reference Action | Migrate Connected App (migrateConnectedApp) |
| Does this action execute one or more prompt templates? | No |
Guidelines and Considerations
This agent action calls the Migrate Connected App standard invocable action, which disables the connected app and creates an external client app with identical settings and policies.
To provide a connected app summary, the agent might ask for the connected app's application ID. The application ID is found in the URL for the connected app settings page. It's an alphanumeric string that starts with 06P and appears in the URL after applicationId%3D.
Before migrating the connected app to an external client app, you must identify the connected app to migrate. Only local connected apps can be migrated to external client apps. Connected apps that use the OAuth 2.0 Username Password flow can’t be migrated to external client apps, because external client apps don’t support that flow.