Use Salesforce Sandbox instead of Salesforce when you want to test Salesforce-backed workflows against a sandbox org instead of production.
Prerequisites
Use a Salesforce Sandbox user with the object and field permissions required for your tests. Confirm that the sandbox contains the records, fields, validation rules, and connected app setup needed by the workflow.
Allowing Breakout to access Salesforce Sandbox
Click your name to navigate to Settings
Click Integrations and then toggle the switch on in the Salesforce Sandbox card
If you do not see the card, ask a workspace or platform administrator whether sandbox connections are enabled for your workspace.
Supported authentication methods
Salesforce Sandbox supports OAuth sign-in and consumer credentials. Use the method shown on the Salesforce Sandbox card in your workspace.
Connect with OAuth sign-in
Click your name to navigate to Settings
Click Integrations and then toggle the switch on in the Salesforce Sandbox card
Allow the Salesforce sign-in window to open.
Sign in to the correct Salesforce sandbox org.
Review and approve the requested permissions.
Permission | Salesforce label | Why Breakout needs it |
api | Manage user data via APIs | Read and write sandbox records through Salesforce APIs according to the connected user's permissions. |
refresh_token | Perform requests at any time | Maintain the sandbox connection without asking the user to sign in before every test workflow run. |
Return to Breakout and wait for the Salesforce Sandbox integration to show as Connected. It may take a few minutes for the status to update on the Integrations page.
If the Salesforce Sandbox approval window closes but the integration still doesn't show as connected, refresh the Integrations page.
If Salesforce Sandbox still appears as Disconnected, reconnect the integration and make sure you complete the Salesforce Sandbox approval process successfully.
Connect with client credentials
If the card shows a credentials form, enter the following details and click Continue.
Field | What to enter |
Consumer ID | Consumer key for the sandbox's connected app |
Consumer Secret | Consumer secret for the sandbox's connected app |
Token URL | My Domain token URL for the sandbox |
Note: Use an HTTPS Salesforce My Domain URL.
Return to Breakout and wait for the Salesforce Sandbox card to show as connected. It will take a couple of minutes to show Salesforce Sandbox as connected on the Integrations page in Breakout.
If the approval window closes but the Salesforce Sandbox card does not update, refresh the Integrations page
If Salesforce Sandbox still shows disconnected, repeat the connection and ensure that the Salesforce Sandbox approval was completed successfully
Creating a sandbox connected app for client credentials
A Salesforce Sandbox admin should follow the same connected-app process used for Salesforce production, but complete the steps inside the sandbox org and choose a sandbox execution user.
Ensure that the execution user has API access and the permissions required by the workflows you plan to test. The execution user's permissions determine what Breakout can read or write in the sandbox.
Verifying the connection
The Salesforce Sandbox card should show as connected. Test a workflow that reads a non-critical sandbox record.
If a test fails, compare the sandbox user's profile, permission sets, required fields, and validation rules with the expected workflow behavior.
Disconnecting or reconnecting Salesforce Sandbox
Disconnect Salesforce Sandbox in these cases:
Sandbox is refreshed
Credentials are rotated
Wrong sandbox was selected
Important: Disconnecting the Salesforce Sandbox does not disconnect the production Salesforce integration