Action Link Templates live in Setup, but most of the value shows up only after integration code references them. Design the call site before configuring the template, not after.
- Open Action Link Templates in Setup
Setup, then search for Action Link Templates. The list view shows existing templates with their status (Draft, Published, Archived).
- Create a new template
Click New. Provide a Label, Action URL, HTTP Method, and Action Type (Api, ApiAsync, Download, Ui). Save the template as Draft until the configuration is fully tested.
- Configure bindings
Use {!Bindings.RecordId} or similar placeholders inside the URL, body, or headers. Document the binding names for the team that writes the code that will create feed items, since typos surface as broken buttons with no error.
- Set User Visibility and Requires Confirmation
Choose who should see the link. For destructive actions, check Requires Confirmation so users see a dialog before the action fires.
- Publish the template
Change status to Published. Once any feed item references it, the template becomes immutable. Edit only by creating a new version.
Api, ApiAsync, Download, or Ui.
The HTTP endpoint, file URL, or destination URL. Supports binding placeholders.
GET, POST, PUT, DELETE, PATCH, or HEAD. Only relevant for Api and ApiAsync.
Reference to a system-defined enum that controls button text in each state (New, Pending, Successful, Failed).
Who can see and click the link at runtime.
Boolean. True shows a confirm dialog before the action fires.
Optional. Auth profile used when the action calls an external API.
Optional. Header pairs and a body template for POST, PUT, and PATCH actions.
- Once a template is Published and referenced by a live feed item, key fields like URL and Method become locked. Plan to version the template instead of editing in place.
- Binding names are case-sensitive and must match the keys passed at runtime exactly. Typos render the button broken with no obvious error message.
- User Visibility Only Custom User must be set per feed item at creation time. Forgetting it means every user in the feed sees the approval buttons, not only the approver.
- Action Links render in a different surface in Lightning Experience than they did in Chatter Classic. Verify rendering in Lightning before assuming the template still works as designed.