Salesforce Browser Automation Skill
This skill enables browser automation for Salesforce orgs authenticated via SF CLI.
Overview
Use the sf-browser-control MCP server tools to:
- Launch authenticated browser sessions for any SF CLI connected org
- Navigate Lightning pages, Setup, App Launcher, and object views
- Fill forms including text fields, picklists, lookups, checkboxes, and dates
- Create, edit, save, delete, and clone records
- Capture screenshots and extract page content
Prerequisites
Before using these tools, ensure:
- SF CLI is installed and authenticated with target orgs (
sf org login web -a alias)
- Playwright browsers are installed (
npx playwright install chromium)
Workflow Pattern
Starting a Session
- List available orgs: Use
sf_list_orgs to see authenticated orgs
- Start session: Use
sf_session_start with the desired orgAlias
- Verify: Use
sf_session_status to confirm connection
Navigation
- Home:
sf_navigate_home
- Setup:
sf_navigate_setup with optional section parameter
- Objects:
sf_navigate_object with objectApiName
- Records:
sf_navigate_record with recordId
- Apps:
sf_navigate_app with appName
Form Filling
Use these tools in sequence:
sf_record_new or sf_record_edit to open formsf_fill_field for text inputs (use fieldLabel)sf_select_picklist for dropdown fieldssf_select_lookup for relationship fields (searches and selects)sf_check_checkbox for boolean fieldssf_fill_date for date/datetime fieldssf_record_save to save
Verification
sf_get_toast_message - Check success/error messagessf_screenshot - Capture current statesf_get_field_value - Verify field valuessf_get_record_details - Get record information
Key Tools Reference
| Category |
Tools |
| Session |
sf_session_start, sf_session_status, sf_session_close, sf_list_orgs |
| Navigation |
sf_navigate_home, sf_navigate_setup, sf_navigate_object, sf_navigate_record |
| Forms |
sf_fill_field, sf_select_picklist, sf_select_lookup, sf_check_checkbox |
| Records |
sf_record_new, sf_record_edit, sf_record_save, sf_record_delete |
| Capture |
sf_screenshot, sf_get_page_text, sf_get_toast_message |
Tips
- Always wait for Lightning spinners with
sf_wait_for_spinner after navigation
- Use
sf_screenshot liberally to debug issues
- Field labels are case-sensitive - match exactly as shown in UI
- Lookups require a search term that matches records in the org
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: sf-browser-automation3description: Use this skill when automating Salesforce browser interactions, controlling browser sessions for SF orgs, navigating Lightning pages, filling forms, creating/editing records, or performing Setup configurations. Trigger keywords include Salesforce browser, Lightning UI, SF automation, record creation, Setup navigation, form filling.4---56# Salesforce Browser Automation Skill78This skill enables browser automation for Salesforce orgs authenticated via SF CLI.910## Overview1112Use the sf-browser-control MCP server tools to:13- Launch authenticated browser sessions for any SF CLI connected org14- Navigate Lightning pages, Setup, App Launcher, and object views15- Fill forms including text fields, picklists, lookups, checkboxes, and dates16- Create, edit, save, delete, and clone records17- Capture screenshots and extract page content1819## Prerequisites2021Before using these tools, ensure:221. SF CLI is installed and authenticated with target orgs (`sf org login web -a alias`)232. Playwright browsers are installed (`npx playwright install chromium`)2425## Workflow Pattern2627### Starting a Session28291. **List available orgs**: Use `sf_list_orgs` to see authenticated orgs302. **Start session**: Use `sf_session_start` with the desired `orgAlias`313. **Verify**: Use `sf_session_status` to confirm connection3233### Navigation3435- **Home**: `sf_navigate_home`36- **Setup**: `sf_navigate_setup` with optional `section` parameter37- **Objects**: `sf_navigate_object` with `objectApiName`38- **Records**: `sf_navigate_record` with `recordId`39- **Apps**: `sf_navigate_app` with `appName`4041### Form Filling4243Use these tools in sequence:441. `sf_record_new` or `sf_record_edit` to open form452. `sf_fill_field` for text inputs (use `fieldLabel`)463. `sf_select_picklist` for dropdown fields474. `sf_select_lookup` for relationship fields (searches and selects)485. `sf_check_checkbox` for boolean fields496. `sf_fill_date` for date/datetime fields507. `sf_record_save` to save5152### Verification5354- `sf_get_toast_message` - Check success/error messages55- `sf_screenshot` - Capture current state56- `sf_get_field_value` - Verify field values57- `sf_get_record_details` - Get record information5859## Key Tools Reference6061| Category | Tools |62|----------|-------|63| Session | `sf_session_start`, `sf_session_status`, `sf_session_close`, `sf_list_orgs` |64| Navigation | `sf_navigate_home`, `sf_navigate_setup`, `sf_navigate_object`, `sf_navigate_record` |65| Forms | `sf_fill_field`, `sf_select_picklist`, `sf_select_lookup`, `sf_check_checkbox` |66| Records | `sf_record_new`, `sf_record_edit`, `sf_record_save`, `sf_record_delete` |67| Capture | `sf_screenshot`, `sf_get_page_text`, `sf_get_toast_message` |6869## Tips7071- Always wait for Lightning spinners with `sf_wait_for_spinner` after navigation72- Use `sf_screenshot` liberally to debug issues73- Field labels are case-sensitive - match exactly as shown in UI74- Lookups require a search term that matches records in the org7576---77> Converted and distributed by [TomeVault](https://tomevault.io/claim/ehartye) — claim your Tome and manage your conversions.78<!-- tomevault:4.0:skill_md:2026-04-15 -->
tomevault-io