SFDC Zeta

Query, load, and explore Salesforce data with SOQL, bulk DML, mapping, transforms, and pre-load validation.

SFDC Zeta is a Salesforce workbench that runs in Chrome beside Lightning or Setup. Query data, load files, run Apex, call APIs, watch events, inspect logs, retrieve metadata, and map the schema against the org you connect, without leaving the browser. Connect from the Salesforce tab you are already signed into, or with OAuth (PKCE). Production orgs show a red bar, sandboxes show green. Open the workbench in the side panel, a new tab, or an overlay. On Lightning pages, a slim launcher on the right edge opens objects, users, shortcuts, and org details. QUERY Run SOQL, SOSL, or GraphQL. Results open in a grid. Edit rows, update or delete from the toolbar, and export CSV or Excel. Autocomplete follows Salesforce SELECT functions, date literals, and field names. Ctrl+Enter (Cmd+Enter on Mac) runs; Stop cancels an in-flight query. DATA LOAD Insert, update, upsert, delete, or undelete from CSV or Excel. Map columns to Field API Names, apply named transforms (trim, case, dates, value maps, concat — no eval), and validate every row before anything hits the org. Small loads use Composite REST; large files use Bulk API 2.0. Custom metadata types deploy through the Metadata API. Multi-object workbooks can load related sheets (for example Account then Contact) in order. Copy Between Orgs On Load, pick a source org and a different destination org you already connected. Preview records from source, then Insert or Upsert into destination. Related lookup parents (for example Account and Campaign on Opportunity) copy with the rows. Source Salesforce Ids are never used as destination Ids. Upsert matches External ID or DeveloperName only. Existing destination records are not deleted. Person Contacts on Person Accounts are not copied as Contact rows. Files and attachment bodies are not copied. If a sheet fails, inserts from that run can be rolled back External Import On Load, use External Import to fetch JSON from an outside API, then map and load it the same way as Data Migration (field mapping, named transforms, Validate, Run, Retry failed). Two routes (configure under Settings → External): Salesforce — callouts go through a Named Credential in the org plus the deployable ZetaExternalFetch Apex REST class. No API secrets are stored in the extension. Extension — HTTPS fetch from the browser after you grant host access. Use a session-only bearer if needed; secrets are not saved on disk. Download the mapping template (How to use, Mapping, Transformations). Source column names must match JSON fields from the fetch. After Fetch, upload the mapping sheet, pick the target object if needed, then Validate / Run. APEX System Administrators can run anonymous Apex with System.debug output, compile errors, the full debug log, and governor limits without Developer Console. Production DML asks before it runs. API sends REST or SOAP against the connected org. View the full response as formatted JSON/XML, a tree, or a table. Saved calls stay on this computer. EVENTS, LOGS, AND LIMITS Subscribe to platform events or Change Data Capture. Browse Apex debug logs by user and time, search Debug / SOQL / DML / callouts, and download the log. Check Daily API Request and other org limits before a large job. Apex logs (Debug) Browse ApexLog records from the Tooling API by user and time. Start trace turns on USER_DEBUG (Debug Level + duration); Stop ends it early. Open a log for Overview, Timeline, SOQL/DML/callouts, limits, and exceptions. Search list or In Logs, compare two logs, download .log, or delete selected. Bulk delete is on the launcher Org tab. PERFORMANCE Use Perf when a Salesforce click or navigation feels slow and you need a downloadable triage report. Pick the Salesforce browser tab for the connected org, click Analyze performance, reproduce the slow action in that tab, then Stop & generate report. Clicking Cancel on Chrome’s debugging banner does the same: capture stops and Zeta builds the report. METADATA AND SCHEMA Retrieve or deploy a metadata zip from a package.xml. The Metadata types list comes from the connected org (Apex, custom objects, record types, validation rules, and the rest). Draw an ER diagram from sObject describe and export SVG, Mermaid, DBML, SQL, CSV, or draw.io. Org compare — pick a metadata type (objects, Apex classes, permission sets, and the rest of the Meta catalog). Compare names to see which members exist only here, only in the other org, or in both. Pick one component and Compare this to retrieve that member from both orgs and diff what is inside it (fields, validation rules, FLS, Apex source). Filter Only left, Only right, Different, or Same. Same is off by default. User access — Access snapshot loads a user: profile, role, license, effective permissions, assigned permission sets and groups, queues, public groups, and login history. Why can’t they see this? is the Setup time-sink: pick the user plus a record Id or field. The report is profile, permission sets, object CRUD, FLS for that field, sharing, and restriction rules. RUN AS A System Administrator can run SFDC Zeta as another user. Salesforce in the browser stays signed in as you; only the extension’s API calls use the other session. Stop Run as does not log you out of Salesforce. PRIVACY SFDC Zeta does not operate its own server. Session tokens stay in this browser and are sent only to that org’s Salesforce instance over HTTPS. Host access is limited to Salesforce domains. Your Salesforce data is not sold, not used outside this workbench, and not used for creditworthiness or lending. Bugs, suggestions, and feedback Help (?) → Website explains the extension and how to use it. Help → Feedback opens a form: pick Bug, Suggestion, or Feedback, fill the details, and click Submit. That opens a GitHub issue on the public SFDC Zeta tracker. Sign in to GitHub if asked, then click Submit new issue. Do not include session ids, passwords, or production record dumps. GitHub issues are public. Keyboard shortcut: Alt+Shift+D.