ONE WORKFLOW. EVERY CUSTOMER.
Select a customer’s opted-in services at site level, then let shared onboarding workflows read the configuration and carry out the relevant work.
Choose the services a fictional customer has opted into. The plan updates from the site settings.
- Read site service EDFs and customer parameters.
- Check for the selected security agent, install where required and validate.
- Detect and deploy the selected standard software packages.
- Apply the agreed workstation patching scope and schedule; verify results.
- Record outcomes and escalate failed checks with useful context.
Simplified demonstration of the configuration pattern. No client is onboarded, no EDF is changed and no software is installed.
THE PROBLEM.
Different customers needed different software, security agents and installation parameters. A separate script for every variation would make every future change harder to maintain.
MY ROLE.
I extended ConnectWise Automate onboarding workflows using client/site information and Extra Data Fields. Site-level service selections and customer-specific parameters supplied the settings for shared automation, rather than maintaining a separate script for every customer.
HOW IT WORKED.
Configure the customer’s services
Record the opted-in services and customer parameters in site-level EDFs. The configuration becomes the starting point for the onboarding workflow.
Read the settings and develop shared logic
Reusable scripts resolve client/site context, check existing installations and prerequisites, then choose the relevant security agent, software package or workstation configuration.
Deploy, validate and hand over
Run the selected silent installations, validate the result and record outcomes. Failed prerequisites or deployments return to a technician with context; unselected services stay outside the workflow.
MAKE IT TRUSTWORTHY.
Existing-install checks and follow-up validation formed part of the workflow. Before extending it to a new package, I would validate its parameters on a test endpoint, pilot at a selected site and keep the previous configuration available for rollback.
Controls that matter
- Existing-install detection
- Prerequisite checks
- Customer and site targeting
- Follow-up installation validation
- Technician handover on failure
WHY IT MATTERS.
A shared workflow keeps customer differences in configuration rather than duplicated script logic. Engineers have fewer versions to maintain and a clearer way to investigate onboarding failures.
MONITOR + REPORT.
Monitoring approach
Review script outcomes and post-install checks against the selected site services. Missing parameters, failed prerequisites and unvalidated installations need an engineer rather than a blanket success state.
Reporting approach
Report selected services, validated installations, outstanding devices and named exceptions by site. Keep the configuration and technician handover clear when a customer changes its contracted services.
STANDARDISE THE LOGIC. PERSONALISE THE CONFIGURATION.
Business Premium baselines
GOT SOMETHING
WORTH AUTOMATING?
Tell me where your RMM is creating work.
Let’s look at what could run better —
and how to get there.