Featured on 
USE CASE 08 · SALESFORCE
Define the result. Approve the plan.
ABX executes the change in your Salesforce.
Most AI tools answer questions about your CRM. ABX for Salesforce writes — sandbox-first, OAuth-authenticated, with a full audit trail. Live in our own corporate Salesforce since April 2026.
THE LOOP
Four steps. One change.
Sandbox to Production with the human in control.
Every ABX execution follows the same loop. It's the same loop we use on our own corporate Salesforce instance — including the April 29 Pricebook write that's behind every demo we run.
01 / Define
Type what needs to change
Plain English. Field names, validation rules, Pricebook entries, list views — described the way Sales describes them in Slack.
Add product 'Partfox EU 60' to the Gieni Pricebook. Price 60 EUR, Stripe SKU sf_pf_eu_60.
02 / Plan
ABX maps it to your org
Pulls the schema through Pipedream MCP. Identifies the right objects, field mappings, validation rules, and order of operations. Shows you the plan before anything runs.
Product2 → PricebookEntry → Stripe SKU → validation rules → ready for sandbox dry-run.
03 / Approve
Sandbox dry-run, then your click
ABX runs the change in your sandbox first. You see the diff — every field, every rule. Production only happens after you approve.
DEVAIORG · diff reviewed · approval gate · OAuth-authenticated as you.
04 / Execute
Production write, fully documented
Same change, same diff — now in Production under your admin OAuth. Every step in a structured change log. Searchable. Exportable.
Production · audit log · timestamps · who · what · sandbox diff · Production diff.
See it in action
Watch the full execution
REAL EXECUTION · APRIL 29, 2026
The first Production write — adding a product to our own Gieni Pricebook.
Sales asked for a new product line in the Pricebook. With Stripe sync. With validation rules.
The kind of request that's normally a ticket, a sprint, a deploy. ABX did it in under an hour.
THE ASK, FROM SLACK
"Need a new product line in the Gieni Pricebook for Partfox. Price 60 EUR, quantity unit each, must sync with Stripe SKU. Standard validation rules apply."
— Sales team request, Salesforce support channel
WHAT ABX DID
- 01Connected to DEVAIORG sandbox via Pipedream MCP layer
- 02Created Product2 record with correct field mapping
- 03Created PricebookEntry on the Gieni Pricebook
- 04Mapped the Stripe SKU reference field
- 05Applied standard Pricebook validation rules
- 06Generated sandbox dry-run with reviewable diff
- 07On approval, executed in Production via admin OAuth
- 08Documented every step in the change log
TOTAL TIME
< 1 hour
WITHOUT ABX
1–2 weeks
SANDBOX-FIRST
always
PRODUCTION WRITES SINCE
growing
OAuth
on the user. Never a shared admin login. Audit trail intact.
Sandbox
first by default. Every Production write needs your explicit approval.
Pipedream
MCP layer. Production-grade integration. No new infrastructure to host.
Live
in our own Salesforce since April 2026. We use what we sell.
SCOPE
What it does today. What ships in 2026.
We're honest about what's built and what's coming. The wedge — read at scale, sandbox writes, Production writes via admin OAuth — is shipped. The enterprise layer is in build.
Today — already shipped
- Read any field, object, or report in your Salesforce
- Write Production changes under your admin OAuth
- Sandbox-first by default — reviewable dry-run on every write
- Audit trail on every execution — searchable, exportable
- Pipedream MCP layer — production-grade integration
- Multi-sandbox connection support at the connection layer
Read how the agentic enterprise vision maps to CRM operations →
See the loop run against your sandbox.
Twenty minutes with Thomas Bech, who leads ABX for Salesforce.
Live execution in DEVAIORG — your use case, real diff, no slides.