We break down how to use custom fields in ConnectWise Automate to drive more dynamic and targeted scripts. These extra data fields let you customize behavior per device, client, or scenario. Unlocking smarter automation without reinventing your entire script library.
Step by Step:
- Open ConnectWise Automate and navigate to Extra Data Fields (EDFs).
- Review how EDFs can be used to support scripting and automation workflows.
- Identify the three primary ways EDFs can be used: passing information into scripts, storing information from scripts, and controlling where scripts run.
- Use a real-world example such as a SentinelOne agent install script to demonstrate passing data into a script.
- Store client-specific values, such as a SentinelOne site or organization token, in a client-level or location-level EDF.
- Retrieve the EDF value within the script based on where the script is executed.
- Save the retrieved EDF value as a script variable and pass it as an argument during the application install process.
- Avoid hardcoding client-specific values directly into scripts by using EDFs instead.
- Configure scripts to store output data back into EDFs when needed.
- Use the Extra Data Field Set Value function to write script results into an EDF.
- Select the appropriate EDF and map it to a variable generated by the script.
- Store audit-related results such as BitLocker status, installed software, or Windows 11 compatibility.
- Use computer-level EDFs so results are visible directly on individual agents.
- Open an agent and review populated EDFs to confirm the script ran and stored data correctly.
- Create EDFs to control whether scripts should or should not run in specific environments.
- Use true/false or yes/no EDFs at the client, location, or computer level to enable or disable script execution.
- Configure a software deployment script to reference these EDFs before running.
- Avoid inefficient scheduling by preventing scripts from running repeatedly once their task is complete.
- Open a client record and navigate to the Info tab to manage application deployment EDFs.
- Define which agent types within a client or location should receive a deployment.
- Store deployment keys or location-specific tokens in EDFs when required by the installer.
- Enable deployment at the client level while creating exclusions at the location or computer level.
- Create EDFs that explicitly exclude specific locations from application deployment.
- Pull exclusion EDF values into the script and exit the script if the exclusion condition is met.
- Apply the same EDF-based logic within internal monitors if scripts are triggered that way.
- Add additional queries to internal monitors to prevent scripts from running where exclusion EDFs are set.
- Use EDF-driven logic to ensure scripts run only where intended and remain efficient.