A centralized UI for managing and visualizing Salesforce trigger actions — built on the Trigger Actions Framework. The Admin Panel gives administrators and developers a single pane of glass to visualize, organize, and configure automation logic directly in Salesforce, automating the underlying Custom Metadata deployments.
Important
Prerequisite: You must have the core Trigger Actions Framework installed in your org first.
-
Assign the Trigger Actions Framework Admin permission set:
- Go to Setup → Users → Permission Sets.
- Select Trigger Actions Framework Admin.
- Click Manage Assignments and assign to your user(s).
-
Add the Trigger Actions tab to any Lightning app of your choice:
- Go to Setup → App Manager.
- Edit your preferred app → Navigation Items → add Trigger Actions.
Your strategic entry point for automation governance. Get a centralized overview of framework adoption across every SObject, launch discovery scans, and initialize new SObject configurations — all from a single dashboard.
Quickly filter and select SObjects from the sidebar, where badge counts summarize adoption at a glance:
- TAF Actions Count: Displays the number of framework actions configured on the object.
- Native Automations Count: Displays the number of active, non-framework triggers and record-triggered flows on the object.
- Add SObject: Register a custom or standard SObject under the framework with a single click.
Uncover hidden automation debt in seconds. The Discovery engine scans your entire org for unmanaged Apex Triggers and Record-Triggered Flows, identifying exactly where native logic exists and providing a streamlined path to bring it under the framework's control.
Full visibility into every automation on an object. Actions are grouped by execution context — Before Insert, After Update, etc. — and displayed in their precise execution order.
- Interactive Reordering: Reorder execution sequences on-the-fly using precise, accessible up/down controls, with a draft banner to save or reset. Saving triggers an automated Custom Metadata deployment in the background.
- Unified Visibility: Native triggers and Record-Triggered Flows are tracked alongside framework actions, with direct access to View Source and Flow Visualizer from each item.
Visualize Record-Triggered Flows as interactive flowcharts directly in the Admin Panel.
- Multi-Level Drill-Down: Click on any Subflow node to fetch its metadata and render its nested flowchart, or click on an Apex Action to trace into its logic diagram and code.
- Side-by-Side Comparison: Compare subflows or Apex logic side-by-side with the parent Flow, or expand to a full focused view with breadcrumbs.
- Rich Diagrams & Exports: Use the built-in Legend to decode execution nodes, view input/output parameter maps directly inside nodes, and export high-definition PNGs of your flowcharts for offline documentation.
Inspect implementation logic without leaving the UI.
- Apex Logic Flowcharts: Automatically parse Apex source code and generate flowchart diagrams for classes and methods (including auto-detection of
@InvocableMethodentry points). - Direct Source Inspection: View full Apex class bodies side-by-side with logic diagrams for rapid validation.
Browse only the Apex classes that implement Trigger Action interfaces. On selection, the tool auto-detects and maps supported trigger interfaces directly to your configuration — no guesswork required.
Instantly toggle bypasses for data loads or maintenance windows with immediate visual feedback. The active/disabled state of each action is visible at a glance, enabling real-time control over org-wide automations.
For detailed documentation on the Trigger Actions Framework — writing Action classes, bypass logic, advanced patterns — visit the official documentation site or the GitHub repository.
- Metadata Deployments: Saving changes triggers a background metadata deployment. Changes typically take 5-10 seconds to reflect in the UI.
- Deletion: For security and stability, the Trigger Actions Admin Panel does not support deleting records. Use Salesforce Setup (Custom Metadata Types) or VS Code to remove configuration records.
The Flow Visualizer and Apex Code Visualizer read live metadata (Flow definitions, sObject describes, Apex bodies) from the Salesforce Tooling / REST API. To keep this responsive and avoid Apex callout governor limits, these calls are made directly from the browser, authenticated with the current user's session ID.
How the session token is handled
- The session ID is obtained from the
SessionIdPageVisualforce page ($Api.Session_ID) viaOrgSessionController.getSessionId()and sent as aBearertoken on the client-side API calls. - It is the logged-in user's own session, so every call runs as that user and honors their object/field permissions. Server-side Apex queries additionally run
WITH USER_MODE/with sharing. - The token is not cached or persisted —
getSessionIdiscacheable=false, and the value lives only in page memory for the duration of the session.
What this means for you
- The session token is present in the browser while the page is open. As with any tool that surfaces a session, restrict access to trusted administrators — the Admin Panel is gated behind the Trigger Actions Framework Admin permission set, and you should not broaden that assignment.
- Standard org hardening still applies and is recommended: login IP ranges, session timeout, and "Lock sessions to the IP address from which they originated."
- Diagram text (flow/apex labels) is rendered with HTML labels disabled and Mermaid's
strictsanitization, so metadata text cannot be interpreted as markup.
If your security posture does not permit a session token in the browser, the visualizer callouts would need to be re-routed through server-side Apex (e.g., a Named Credential). The rest of the Admin Panel does not depend on this pattern.
Because the visualizer calls the API from the browser, your org must allow the Lightning domain as a CORS origin:
- Go to Setup → Security → CORS.
- Under Allowed Origins List, add your Lightning domain (e.g.,
https://<your-domain>.lightning.force.com).
If diagrams fail to load with a CORS / callout error, this step is usually the cause.
- Renamed the project back from "Automation Command Center" to Trigger Actions Admin Panel (with the tab renamed to Trigger Actions)
- Overhauled empty-state dashboard layout under three visual pillars (Discover, Understand, Govern) using high-fidelity inline SVG illustrations and updated copy descriptions
- Removed interactive card triggers/buttons from the dashboard cards, standardizing them as informational layouts with a primary "Run Discovery" action in the footer
- Refactored stylesheet to implement SLDS design tokens, enabling native dark mode support in the dashboard layout
- Cleaned up obsolete and orphaned CSS styling classes from deleted global stats and welcome panels
- Updated README documentation to feature the new dashboard and SObjects navigation sidebar annotations
- Added Flow Details panel — version, status, API version, trigger order, run mode, and description, sourced from the flow's own metadata
- Added a diagram Legend, full-diagram PNG export, and an "unsupported element" placeholder so diagrams never silently drop nodes
- Improved drill-down — opens in a focused full view by default with a "Compare with parent flow" toggle, and a clean aligned side-by-side compare view
- Fixed edge-label rendering (labels are now centered on their connector) and special-character handling in flow labels
- Replaced drag-and-drop action reordering with precise, accessible up/down move buttons
- Fixed the Native Automations panel briefly showing the previous object's results while switching objects
- Widened the visualizer modals to use more of the viewport
- Hardened security — the session token is no longer cached, Mermaid runs in strict mode, and the browser session-token model + CORS requirement are documented
- Added continuous integration (ESLint + Jest) and expanded unit-test coverage
- Renamed from "Trigger Actions Admin Panel" to Automation Command Center
- Removed the dedicated Lightning app — the Command Center is now a standalone tab that can be added to any app
- Added Flow Visualizer — interactive flowchart rendering of Record-Triggered Flows
- Added Apex Visualizer — AST-powered source code visualization for Apex classes
- Updated framework documentation links to the official doc site
- Introduced the Command Center dashboard with org-wide automation overview
- Added Discovery engine for scanning unmanaged triggers and flows
- Added native trigger and Record-Triggered Flow tracking alongside framework actions
- Added one-click SObject initialization
- Initial release with hierarchy view, action creation, bypass toggles, and source view
If this project helps you, please consider supporting its development:
Contributions are welcome! Please feel free to open issues or submit pull requests.