Skip to content

Configure AddressTools Premium with an LLM Copilot

With an LLM copilot (GitHub Copilot, Agentforce Vibes, Cursor, Windsurf, or similar), AddressTools Premium can be installed and configured, including creating address blocks, assigning permissions, tuning settings, and managing reference data, by describing the requirement in plain English rather than working through Setup menus.

Note: This capability is under active development. It covers a focused set of configuration tasks and has been tested with a limited pool of models, so results may vary. Report any gaps to ProvenWorks support.

Documentation Map

Page Audience Covers
This page You How this works, prerequisites, tips and FAQ
Install AddressTools Premium You Getting the package installed via the copilot
Example Prompts You Copy-paste prompts organised by task
Headless Setup Guide The copilot Technical reference; paste this link into the copilot's chat

Prerequisites

  • VS Code (or another editor) with an LLM copilot installed
  • Salesforce CLI (sf) authenticated against the target org
  • System Administrator access on the target org

How It Works

  1. Open the copilot's chat.

  2. Paste the headless setup guide link so the copilot has the technical context it needs:

    https://provenworks.com/addresstools-premium-headless-setup-guide-for-llm-copilots/

  3. Describe the requirement in plain English, for example:

    "Use this guide – https://provenworks.com/addresstools-premium-headless-setup-guide-for-llm-copilots/ – I want to create a new address block on Contact for a Seasonal address with verification."

  4. Review and approve the terminal commands the copilot proposes.

  5. Done: no Setup menus, no manual metadata wrangling.

See Example Prompts for ready-to-use prompts by task category.

Tips for Better Results

  1. Be specific about the org. Include the org alias in the prompt if multiple orgs are authenticated: "On production-org, disable the Account trigger for the Data Migration profile."
  2. State the capabilities required. When creating an address block, say whether verification, lookup population and/or geocoding are needed. If unspecified, the copilot will ask.
  3. Name the object and address type. For standard objects, mention Mailing, Billing, Shipping, or Other. For custom objects, mention the API name, for example Property__c.
  4. Reference the guide URL. Paste the guide link in the first message so the copilot has the full context.
  5. Let the copilot run commands. It uses sf CLI commands and anonymous Apex; approve the terminal commands when prompted. No manual Setup clicks are required.

Frequently Asked Questions

Do I need to know Apex or the Salesforce CLI? Not strictly; the copilot writes and runs the commands. A basic familiarity with the Salesforce CLI and Apex helps follow along with the changes being made and catch anything that doesn't look right.

Will this work with any LLM, or just GitHub Copilot? The headless setup guide is designed for any LLM copilot that can execute CLI commands, including GitHub Copilot, Cursor, Windsurf, and Salesforce's own Agentforce Vibes (in Act mode). If the tool can run terminal commands and read web content, it should work.

Is this safe for production? The guide enforces safe practices: it checks before creating, uses anonymous Apex (which leaves no code behind), and creates dedicated Permission Sets rather than modifying managed-package metadata. Run these tasks in a sandbox first, verify the results, then promote the metadata to production through the normal deployment process. Always review the commands proposed before approving them.

Can I undo what the copilot creates? Yes. Custom fields, Permission Sets and address block records are standard Salesforce metadata and data, so they can be deleted or modified through Setup or the CLI at any time.

Does the package require a license for production? Production orgs start a 14-day free trial. Contact sales@provenworks.com for licensing after the trial.

Where do I get help?

Glossary

Term Meaning
Address block A record that tells AddressTools which fields on which object to validate, standardise and geocode
Anonymous Apex Apex code executed on the fly via the CLI; it runs and disappears, leaving no code in the org
FLS Field-Level Security; controls which users can read or write specific fields
Geocoding Converting an address into latitude/longitude coordinates
Hierarchy custom setting A Salesforce setting with org-wide, profile, and user-level overrides
Namespace (pw_ccpro) The managed package prefix; all AddressTools objects and fields start with this
Permission Set A Salesforce construct that grants users access to specific fields and features
PLAV Premise-Level Address Verification; validates addresses down to the building number
sf CLI The Salesforce CLI, the command-line tool for interacting with Salesforce orgs