Salesforce Productivity: Workbench Tool

Salesforce Productivity: Workbench Tool

A Salesforce tool was recommended to me several years ago, and I have used that tool every week since in my Salesforce career. That tool is Workbench.

Workbench is absolutely free to use and is open source. Workbench uses the Salesforce API to allow a Workbench user access to individual (or multiple) records in a browser interface, amongst many other things. Users can then make updates to the record from the browser tool.

Workbench allows users to inspect and manipulate data and metadata without having to use the Salesforce front-end, Dataloader.iO or Data Loader. Workbench is an additional tool in your Salesforce data toolbelt.

Users login to Workbench using their Salesforce credentials.

Note: Workbench is not an official Salesforce tool and not tested by Salesforce. All questions about Workbench need to be directed to the Workbench team via Stackflow. Salesforce won’t support the use of Workbench. Full documentation is available from here on GitHub.

Workbench is a broswer-based set of tools designed for Salesforce admins and devs to interact with Salesforce orgs using the the Force.com APIs.

Workbench offers a wide range of functionality, including:

  • The ability to Insert, Update, Upsert, Delete, Undelete, and Perge one or multiple Salesforce records
  • The ability to manipulate data and metadata in bulk
  • An array of tools to test and troubleshoot the Force.com APIs
  • And all with a simple and intuitive user interface

I personally use Workbench regularly to investigate hidden fields on a page-layout that I may need to update. I also use Worbench to explore the REST APIs and for managing user passwords.

Workbench has been developed by the amazing Ryan Brainard. Huge thanks to Ryan for this amazing tool he has created to help us in our day-to-day Salesforce work.

Head over to Workbench now and see how it can help make your Salesforce day simpler.

Ian Jamieson avatar

Leave a Reply

Your email address will not be published. Required fields are marked *