Custom Actions configures tools and personalized links available from lead workflows. You need authority to change shared actions, and the destination must be appropriate for any lead information supplied to it.
What you’ll see
Review an existing action
- Open Settings → Integration → Custom Actions.
- Expand its summary and inspect Menu label and Action type.
- Check Where it appears: the Lead Action menu, Email composer Placeholders menu, or both.
- Review When clicked before using the action on a real lead.
Action types include Open a safe link, Get a link from a connected app, and Generate a registered document. A connected-app action requires the selected app and resource. A stored item no longer offered by the app may remain visible as a disabled saved selection.
Understand editing and execution
The editor uses a draft copy. Save Changes writes the configuration; Unsaved changes indicates the draft differs from the saved version. Adding or removing a row is not complete until the save succeeds.
Click behaviors include opening a new tab, opening a pop-up, generating a link in the background, and copying a personalized link. Placeholder values can contain lead information, so check the destination and sharing purpose before running an action or inserting its link into an email.
Registered-document actions can remain hidden until wording, branding, and runtime activation are approved. An activation-pending option is not a usable production workflow merely because it appears in the catalog.
Verify and recover
After an authorized save, reload and inspect the action's type, resource, surfaces, and behavior. Test execution separately with approved data; saving does not prove the destination works or that a document was generated.
If an app is disconnected, reconnect through Apps rather than embedding credentials in a URL. Resolve service errors before assuming menu changes persisted.
Related: Apps, Documents, Lead record.
Screenshots
The screenshot for this guide is shown above, under “What you’ll see”.