New: Drizz now tests AI agents in simulated companies, with a graded report on every run. See how it works →

TwinsSalesforce

A Salesforce twin for testing AI agents.

Test agents that read and update the CRM. The same API and MCP calls, the same validation and permissions, and nothing changes in your real org.

twin / salesforceprivate · seeded · resets in one call
Salesforce twinAccounts, opportunities and validation.
  • Accounts and opportunities
  • Field validation
  • SOQL
  • Permissions and sharing
  • MCP and REST on the same data
  • One-call reset
Meet the twin

A stateful copy of Salesforce, built for testing agents.

It accepts the same API and MCP calls, checks sign-in and input, and follows the same rules, but runs on its own data, so nothing reaches your real account.

What your agent can do
  • Accounts, contacts, leads and opportunities
  • Field validation and required fields
  • Stages and workflow rules
  • SOQL queries
  • Permissions, sharing and API limits
Seeded state

Every run starts from a company that already has history. We seed:

  • Accounts with contacts and history
  • Open opportunities at every stage
  • Activities, notes and tasks
  • Users with profiles
In staging

Use Salesforce in staging, without using production.

1

Validate every action

The twin checks what the agent sends the way Salesforce would: required fields, permissions, rate limits, malformed input. Mistakes fail here, not in your account.

2

Start from a realistic state

Describe the company and the situation in plain English. Drizz seeds the twin to match, and resets it to that state before every run.

3

Replay tasks across tools

The Salesforce twin shares its people, customers and history with the other twins, so a task that touches three tools runs the way it would at work.

Point your agent at it

Swap the address. Your agent code stays the same.

Replace the live Salesforce endpoint with the twin’s. Everything your agent already does keeps working, on data that is yours to break.

  • Same API and MCP calls
  • Sign-in and its failures
  • Real errors
  • Rate limits
  • Permissions and rules
  • Connected data
  • Reset in one call
{
  "mcpServers": {
    "salesforce": {
      "type": "http",
      "url": "<twin MCP endpoint>",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

REST works on the same data. Both are reset with one call.

One company

Connected to the rest of the company.

A deal in Salesforce has the email threads, meetings, Slack channel and Gong calls behind it, so an agent that updates the stage can be checked against what actually happened.

17 of 20 runs passed. 3 broke a rule.

Run your agent on the Salesforce twin.