← All topics

Getting started with OrgBolt

Your first task, from a one-line description to a deployed Salesforce change, in about five minutes.

What OrgBolt does

OrgBolt is a chat-first change manager for Salesforce. You describe a change in plain English. OrgBolt's AI walks a two-phase pipeline — Work, Deploy — and pushes the metadata into your org through the Salesforce REST Metadata API. You watch each step, approve each step, and every deploy is a real deploy against a real org.

You never leave the browser. No SFDX CLI. No packaging. No manual XML. The AI generates the metadata, validates it with checkOnly, and then deploys it only when you click Deploy.

Your first task

On the dashboard, pick a demo task or type your own. A safe first task: "Add a Priority picklist field to Account with values High, Medium, Low." OrgBolt creates the task and opens a chat panel.

  1. Work phase (blue tag): the AI asks any clarifying questions it needs — target object, environment, naming — proposes the simplest solution that fits, and generates the Salesforce metadata XML. Work is read-only against your org, so nothing has touched Salesforce yet. You can read the metadata, ask Work to change it, or accept it.
  2. Deploy phase (green tag): if you have a connected org, OrgBolt validates the metadata with a checkOnly deploy, then pushes it for real. You see a success or failure message in chat, with the Salesforce deploy ID if you want to inspect it in Setup.

Connecting a Salesforce org

You do not need a connected org to try OrgBolt. Work runs without one — you'll see the AI's proposal and generated metadata, and you can review them end to end. Deploy is where an org matters. Click Connect on the dashboard or in Settings, pick production or sandbox, and OAuth takes about 30 seconds.

Start with a sandbox. OrgBolt is non-destructive by default — Work is read-only and Deploy offers Validate-first for production — but the fastest way to build trust in any new tool is to watch it work in a sandbox first.
If login fails immediately with "An unexpected error has occurred during authentication" and no consent screen — Salesforce's error code for this is OAUTH_APPROVAL_ERROR_GENERIC — your Salesforce user is missing the "Approve Uninstalled Connected Apps" permission — Salesforce has required it since September 2025 for any connected app not yet installed in the org. Ask an admin to grant that permission, or install OrgBolt first via Setup → Connected Apps OAuth Usage → Install (retry after the first failed attempt), then reconnect. In a sandbox where the permission doesn't appear in the profile/permission-set editor at all, run Setup → Company Information → Match Production Licenses first.

Where to go next

  • Read /help/work to see what Work asks for, the five read-only tools it calls against your org, and why generation never touches Salesforce
  • Read /help/deploy to understand checkOnly validation and the 5-phase deploy ordering
  • Read /help/safety to see every non-destructive guarantee OrgBolt makes