Sandbox Environments Are Not Available#
AutomateNexus CRM does not offer sandbox environments. There is no way to create an isolated copy of your organization, make changes in it, review a diff against production, or promote changes. Every change you save in AutomateNexus CRM applies to your live workspace immediately.
Agencies can copy a setup with snapshots under Administration → Plans → Agency: Take a snapshot copies an organization's setup, not its data, and Apply to a client gives a client organization the same starting point. A snapshot cannot be applied back to the organization it was taken from, so it is not a sandbox.
Testing Safely in the Live Workspace#
These features let you try things out before customers see them. Most send nothing and change no records; where one reaches a real person or service, it says so below.
- Workflow dry runs — In the workflow builder (Projects → Workflows), open a saved workflow and choose Test. In Test this workflow, pick a real record under Run against and choose Run test: every step runs against that record and shows what it would do. Nothing is sent, nothing is written, and waits are skipped. Unsaved changes on the canvas are included, so you can test an edit before you save it; a new workflow has to be created first. Run now, next to Test, is not a test: it runs the saved workflow for real, emails, texts and record changes included.
- AI agent dry runs — Open an agent under AI → AI Agents and, on its Overview tab, switch on Dry run before you give it an instruction. Reads are real; writes, proposals and delegation are simulated. A paused agent can still be tried with a dry run, unless it was paused because its monthly budget is used up: then nothing runs, dry runs included. Dry runs carry a Dry run badge on the agent's Overview and Runs tabs.
- Stripe test keys — Under Administration → Integrations → Payments, the Stripe card has optional Test mode keys: a Test publishable key (
pk_test_…) and a Test secret key (sk_test_…), kept beside your live keys. Checkouts use them for test purchases. If you enter test keys as your main keys instead, the card shows Test mode and only test payments work until you switch to live keys. - Checkout test purchases — In Commerce → Checkouts, open a checkout and choose Test purchase. The page opens in test mode with no real charges, paid with Stripe's test card 4242 4242 4242 4242. Test purchases are listed in the checkout's figures but never counted as sales.
- WhatsApp Twilio Sandbox — Under Administration → Integrations → Communications → WhatsApp, choose Twilio Sandbox under Sending from to try WhatsApp messaging today without a Twilio sender approval; each person first sends your sandbox join code to Twilio's sandbox number. These are real WhatsApp messages: to test, send a WhatsApp message to your sender from your phone, and it appears in Inbox → WhatsApp, where you can reply.
- Meta test events — With the Meta Conversions API set up, open Marketing → Meta Ads → Conversions → Test events. Send test event sends one event with the Test code from Events Manager, and Test mode for 30 minutes adds that code to real events so you can watch a whole flow arrive in Events Manager. Meta treats a test event like a real one, so send a few, not many.
- Test leads — Under Administration → Integrations → Automation → Lead forms, Send a test lead on one of a connected Page's forms creates a lead that arrives in People within a few seconds, with its answers.
- Test emails and webhooks — Send test on an email campaign in Marketing → Marketing Campaigns sends it to one address you choose, with "[Test]" before the subject. Test on a webhook under Administration → Integrations → Developer sends a test delivery to its address.
- Preview as Client — Administration → Preview as Client opens the client portal the way your clients see it, under an Admin preview bar with Back to admin, so you can check portal changes before inviting anyone.