Salesforce Inspector Advanced¶

Salesforce Inspector Advanced is a browser extension for Salesforce administrators, developers and integrators. It adds contextual tools for data, metadata, debugging, API exploration, access diagnostics and org navigation directly inside Salesforce. This is an independent project and is not affiliated with, endorsed by, or sponsored by Salesforce.

The extension runtime has completed its migration to the new stack: React 19, TypeScript, Vite, React Router 7, Tailwind CSS 4, Radix UI and local shadcn-style components. Active pages, popup, background service worker and Salesforce content runtime are built from src; addon remains the extension package shell for manifests, HTML bridge files, generated Vite assets and static browser-extension assets.

Documentation¶

What Is New In The Modern Runtime¶

A fully Vite-built extension runtime for Chrome, Edge and Firefox packaging.
Typed Salesforce REST, SOAP, Tooling, Streaming API, storage and extension messaging adapters.
Local design system primitives under src/components/ui, composed by reusable domain components under src/components/domain.
Command-focused navigation with Quick Find across extension tools and popup tabs.
New productivity surfaces: Access Doctor, Record Watch, Regex Catalog, GraphQL Explorer, OpenAPI Explorer, Flow Orchestrator, Apex Execute, Login Manager, API Statistics and a React-based Logs Viewer.
Expanded Agentforce entry points for SOQL generation, formula analysis, flow analysis and debug log analysis.
Event Monitor publishing support with generated payloads, publish history and saved event payloads.
Flow Scanner improvements for configurable rules, CSV export, old-version purge and Flow Compare access.
Login Manager encryption is enabled by default, with local groups, backups, import/export and tab/window/incognito launch modes.
More resilient contextual links from Salesforce record pages, list views, setup pages and Flow Builder.

Feature Overview¶

Popup: Objects, Users, Shortcuts and Org tabs with record-aware actions, setup links, user tools, org details and configurable defaults.
Quick Find: Keyboard-friendly command palette for extension pages and popup tabs, with contextual links from the current Salesforce page.
Inline Salesforce runtime: Inspector button, field API name display, contextual page detection, popup iframe handling and shortcut command handling.

Data And Querying¶

Data Export: SOQL, SOSL and GraphQL workspace with multiple tabs, saved queries, query templates, query plan, autocomplete, list-view context export, filtering, field grouping, Excel/CSV/JSON copy and CSV download.
Data Import: Create, update, upsert, delete and undelete records from pasted CSV, spreadsheet-style tables or JSON, including Enterprise and Tooling API modes.
Inspect: View and edit record fields, preserve selected fields, open related setup areas, analyze field usage and launch record-specific tools.
Record Watch: Track selected records or WHERE values over time, run manual or scheduled polling, inspect snapshots and compare changed values.
Regex Catalog: Store reusable regex rules, test them against pasted source text, extract tabular matches, copy results and export CSV.
Apex Execute: Save, import and export Apex scripts; resolve template variables; confirm execution; manage trace flag settings; inspect compile status, debug statements, result markers and raw logs.

Metadata And Setup¶

Access Doctor: Diagnose object permissions, record access and field-level security for a user and object or record, then jump to relevant Salesforce setup areas.
Field Creator: Create fields for standard objects, custom objects, platform events and custom metadata types, with CSV import and permission handling.
Download Metadata: Build package.xml, retrieve metadata, import package definitions and manage retrieve/deploy settings.
Dependencies Explorer: Explore metadata dependencies and discover references to selected metadata components.
Flow Scanner: Scan Flow metadata with @flow-scanner/lightning-flow-scanner-core, customize rules, export findings, purge old versions and open Salesforce Flow Compare.
Flow Orchestrator: Build reusable low-code flows with a visual canvas, saved flows, import/export, validation, runtime state, run logs and nodes for Salesforce queries, DML, Apex REST, Apex Execute, decisions, transforms, forms and fake data.

API, Events And Debugging¶

REST Explorer: Send Salesforce REST requests with saved requests, request history, custom headers, templates and formatted response metadata.
API Explorer: Browse Salesforce REST resources, grouped API URLs and formatted responses, with a console bridge for ad-hoc API calls.
GraphQL Explorer: Execute Salesforce GraphQL operations with variables, saved requests, history, schema introspection, templates, formatted responses and copyable response paths.
OpenAPI Explorer: Import Swagger/OpenAPI JSON or YAML from paste, file, URL or saved documents; browse operations and schemas; filter by method, tag or text; generate cURL commands and request/response samples.
Event Monitor: Subscribe to platform events, change events and custom channels; filter event streams; inspect platform event limits; generate, publish and reuse event payloads.
Logs Viewer: Browse, filter, preview, search, download, share and bulk-delete debug logs, with optional Agentforce analysis.
API Statistics: Track REST and SOAP calls, endpoint usage, errors and response times when API debug statistics mode is enabled.
Org Limits: Review Salesforce org limits with filtering, refresh support, visual usage indicators and copyable raw JSON.

Access And Identity¶

Login Manager: Store Salesforce login targets locally, organize them in groups, search and sort accesses, launch logins in a tab, popup window or incognito window, and maintain local backups.
Encrypted credential storage: Credential encryption is enabled by default with a user-provided passphrase, while export/import and backup workflows stay local to browser storage.

Configuration¶

Options: Configure API version, OAuth client settings, popup behavior, keyboard shortcuts, Data Export, Data Import, Field Creator, Metadata, Debug Logs, Flow Scanner, cache behavior, REST Explorer and Inspect settings.
OAuth / API Access Control: Use Salesforce Connected App or External Client App configuration with OAuth 2.0 and PKCE when org policy blocks direct API access.
Org customization: Configure favicon colors, sandbox and production banners, custom shortcut links, popup button visibility and cache behavior.
Agentforce controls: Enable or hide Agentforce buttons per feature and configure prompt template names for org-specific workflows.

Security And Privacy¶

Salesforce Inspector Advanced communicates directly between the browser and Salesforce. The extension does not send Salesforce data to an external backend.

The extension stores preferences, query history, saved queries, saved event payloads, generated access tokens when configured, Login Manager entries, and cache data in browser storage. Login Manager credential encryption is enabled by default and requires a user-provided passphrase before credentials are persisted. It uses the current browser Salesforce session or an OAuth-generated token when API Access Control is enabled. All Salesforce access remains limited by the permissions of the currently logged-in user.

See the full Privacy Policy and privacy documentation.

Use With API Access Control¶

If your Salesforce org has API Access Control enabled, configure Salesforce Inspector Advanced with an allowed Connected App or External Client App.

Follow the guide: Use Salesforce Inspector with a Connected App.

Installation¶

Local Chrome Or Edge Installation¶

Download or clone this repository.
Install dependencies and build the extension:

npm install
npm run build

Open chrome://extensions/ or edge://extensions/.
Enable Developer mode.
Click Load unpacked.
Select the addon directory.

Local Firefox Testing¶

Build the Firefox package:

npm run firefox-release-build

In Firefox, open about:debugging.
Select This Firefox.
Click Load Temporary Add-on....
Select target/firefox/dist/manifest.json.

Development¶

Requirements¶

Node.js 24, aligned with CI.
npm.
Playwright browsers for e2e testing.

Common Commands¶

npm install
npm run dev
npm run dev:html
npm run typecheck
npm run build
npm run eslint
npm run test:e2e:mock
npm run chrome-release-build
npm run firefox-release-build

Targeted e2e examples:

npx playwright test tests/e2e/popup.spec.js
npx playwright test tests/e2e/data-export.spec.js
npx playwright test tests/e2e/record-watch.spec.js

See tests/HOW_TO_RUN_TESTS.md for mocked and real Salesforce org test setup.

Architecture¶

The active extension runtime is organized around small, typed modules:

src/pages/<tool>/main.tsx: Vite entrypoint for each extension page.
src/background: Manifest V3 background service worker and extension command handling.
src/content-runtime: Salesforce page integration, inspector button, popup iframe, Quick Find overlay and inline helpers.
src/components/ui: Local shadcn/Radix-style UI primitives.
src/components/domain: Reusable business components that compose UI primitives.
src/lib/salesforce: Salesforce REST, SOAP, Streaming API, session and schema adapters.
src/lib/extension: Browser extension messaging, Salesforce page context and tool-link helpers.
src/lib: Shared parsing, storage, export, IndexedDB, clipboard, formatting and utility modules.
src/styles/globals.css: Tailwind CSS 4 setup, CSS variables and design tokens.
addon: Extension package shell with manifests, HTML bridge files, generated Vite assets and static assets.
docs: MkDocs documentation published to GitHub Pages.
tests/e2e: Playwright coverage for extension pages and workflows.

Development Rules¶

Add application code under src.
Keep components, hooks and classes small, modular and reusable.
Use src/components/ui primitives instead of raw form controls in migrated pages and domain components.
Put reusable business UI in src/components/domain.
Preserve public page URLs, query parameters, manifest command names, localStorage keys and Salesforce API contracts.
Treat remaining legacy files in addon/*.js as reference or cleanup candidates, not as the place for new fixes.

Validation¶

For normal code changes, run the relevant targeted checks plus the shared validation suite:

npm run typecheck
npm run build
npm run eslint
npm run test:e2e:mock

For browser packaging, also run:

npm run chrome-release-build
npm run firefox-release-build

When a change touches one extension page, run its specific e2e spec as well. If a failure belongs to a legacy area that is not part of the change, document it instead of fixing legacy code opportunistically.

Contributing¶

Contributions are welcome.

Before starting a larger change, open an issue or feature request that explains the goal, expected workflow and affected Salesforce surfaces.

For pull requests:

Create a branch from master.
Update CHANGES.md.
Update the relevant documentation under docs.
Run the relevant validation commands.
For browser packaging changes, run both release builds.

Troubleshooting¶

If the popup is blank or authentication fails, check Salesforce cookies, third-party cookie settings and generated token state. See Troubleshooting.
If your org moved domains or My Domain changed, clear the old Salesforce sid cookie or browser site data.
If new objects or fields do not appear immediately, clear the SObjects cache from the popup or Options page.
If API calls are blocked by org policy, configure the Connected App or External Client App flow.
If streaming events do not arrive, verify platform event allocation, channel name, replay settings and Salesforce Streaming API availability.

Design Principles¶

Stay inactive until the user explicitly interacts with the extension.
Prefer manual, ad-hoc administrator and developer workflows over background automation.
Keep advanced tools discoverable without slowing down common workflows.
Provide contextual Salesforce information when it helps the current task.
Keep the raw Salesforce API accessible and avoid breaking core workflows when enhanced parsing fails.
Support admins, developers and integrators across many Salesforce editions, org shapes and network conditions.
Be conservative with Salesforce API usage while preserving productivity.

About¶

Salesforce Inspector Advanced is maintained by Jean Paul Sanchez and is based on Salesforce Inspector Reloaded by Thomas Prouvot, which is forked from the original Salesforce Inspector by Soren Krabbe and Jesper Kristensen.

Current development and modernization work is supported by Codestorm Srl.

Third-Party Notices¶

This project uses CometD for Salesforce Streaming API support and @flow-scanner/lightning-flow-scanner-core for Flow Scanner analysis.

See THIRD_PARTY_NOTICES.md for license and source details.

License¶

MIT