For Salesforce consultancies
Flow failures, API limits, failed logins and job errors across every client org, in one place, inside your own Salesforce.
Client data never leaves Salesforce. See how we know
What it watches
Each client org is checked every 30 minutes through a read-only connection. Problems open incidents, and repeats add to the same one.
Failed Flow interviews from every client, with the Flow, the element that failed and the error. Route the client's Flow error emails to us as well, and a failure is an incident within seconds instead of at the next check.
By default, Salesforce sends Flow error emails to whoever last edited the Flow. That might be a developer who moved on months ago. Routing them to MultiOrgMonitor means they reach the team.
Every limit the org reports, with the one closest to its maximum first, so you see the 84% before the integration stops.
Failed attempts in the last 24 hours, by the reason Salesforce gives and by user, so a locked-out integration user stands out.
Batch, queueable, scheduled and future Apex that failed or reported errors in the last 7 days, and Bulk API jobs that failed. Never the records themselves.
The Health Check score and its high-risk settings, Setup changes in the last 7 days, scheduled jobs, licence use, and locked or inactive users.
How it works
A managed package in your consultancy's Salesforce org. Collection, incidents and alerts all run there, under your own security settings.
The client admin approves once with their own login, and the app does the setup after listing every change. Prefer not to? Use the script or a Setup checklist. Or skip the connection and just route Flow error emails.
Repeats group into one incident you can acknowledge and resolve. A single failed check doesn't alert anyone. Consultants see the clients assigned to them, and managers see every client.
Honest by design
"Collected 4 minutes ago" sits next to the data. When a check fails, you see that in amber, never old data dressed up as healthy.
What Salesforce reported is kept apart from what we infer. An email report stays labelled "Reported by email" until the API confirms it.
If a sandbox refresh changes a client's org ID, collection stops for that client until a manager accepts the new org. You never see another org's data by mistake.
Security
Monitoring runs in your org, so your clients' data goes from their Salesforce to yours and nowhere else. Not to us, and not to anyone we use.
Two ways to monitor a client
Two Setup changes in the client org, and nothing to install. Flow error emails become incidents in seconds, labelled as reported by email.
A read-only connection adds limits, logins, jobs, security and Setup checks every 30 minutes, and confirms each emailed failure through the API.
Each client environment uses one or the other, so a light-touch client and a fully connected one can sit side by side. Compare plans
More on the pricing page and in the docs.
For Flow errors only, no. The client admin makes two Setup changes so that Flow error emails come to you.
For full monitoring, the client org needs an integration user and a small connector app. The client admin can approve once with their own login, and the app sets everything up and lists each change first. A script and a Setup checklist do the same for admins who prefer them.
About 10 API requests per client environment every 30 minutes, which is under 500 a day. Flow errors only uses none.
Not yet. We're selling directly while we work with pilot consultancies. Salesforce shows a warning when you install a package that hasn't been through its review. The security overview explains what the package does and how to check it yourself.
It's in your Salesforce org, not ours, so it stays yours. Removing a client deletes its monitoring data straight away. Uninstalling the package removes the rest.
A 14-day trial covers full monitoring for up to 5 client environments, plus 10 on Flow errors only.