diff --git a/articles/policy-automation-run-script.md b/articles/policy-automation-run-script.md
new file mode 100644
index 000000000000..da97654411d4
--- /dev/null
+++ b/articles/policy-automation-run-script.md
@@ -0,0 +1,53 @@
+# Automatic policy-based execution of scripts on hosts
+
+
+
+Fleet [v4.58.0](https://github.com/fleetdm/fleet/releases/tag/fleet-v4.58.0) introduces the ability to execute scripts on hosts automatically based on predefined policy failures. This guide will walk you through configuring Fleet to automatically execute scripts on hosts using uploaded scripts based on programmed policies. You'll learn how to configure and use this feature and understand how the underlying mechanism works.
+
+Fleet allows users to upload scripts executed on macOS, Windows, and Linux hosts to remediate issues with those hosts. These scripts can now be automated to run when a policy fails. See [the scripts guide](https://fleetdm.com/guides/scripts) for more information.
+
+## Prerequisites
+
+* Fleet Premium with admin permissions
+* Fleet [v4.58.0](https://github.com/fleetdm/fleet/releases/tag/fleet-v4.58.0) or greater
+* [Scripts enabled](https://fleetdm.com/guides/scripts#enable-scripts) on all target hosts
+
+## Step-by-step instructions
+
+1. **Add a script**: Navigate to **Controls** > **Scripts**, select the team on which you want the script and policy to run, and upload the script you want to run.
+2. **Add a policy**: Navigate to **Policies**, select the team you want the policy to run on, and click **Add policy**. Follow the instructions to set up a custom policy or use one baked into Fleet. You can also add a script automation to an existing policy.
+3. **Set the automation**: In the previous step's **Policies** list view you navigated to, click **Manage automations**, then click **Run script**. Check the box beside the policy (or policies) for which you want to run scripts, then select a script in the drop-down that appears next to the policy name. When you're done associating policies to scripts, click **Save**.
+
+The next time a fleetd host fails the policy you added automation for, Fleet will queue up the script you selected and run it on the host as if you had requested a script run manually.
+
+## How does it work?
+
+* Online hosts report policy status when on a configurable cadence, with hourly default.
+* Fleet will send scripts to the hosts on the first policy failure (first "No" result for the host) or if a policy goes from "Yes" to "No". Policies that stay failed ("No") for a host in consecutive reports will not be resent the script.
+
+> When script automation on a policy is added or switched to a different script, the policy's status will reset for associated hosts. This allows the newly attached script to run on hosts that had previously failed the policy.
+
+* Scripts are run once regardless of exit code.
+* When used in policy automation, Fleet does not run shell scripts on Windows hosts or PowerShell scripts on non-Windows hosts.
+
+## Via the API
+
+Script policy automation can be managed by setting the `script_id` field on the Fleet REST API's [Add team policy](https://fleetdm.com/docs/rest-api/rest-api#add-team-policy) or [Edit team policy](https://fleetdm.com/docs/rest-api/rest-api#edit-team-policy) endpoints.
+
+## Via GitOps
+
+To configure script policy automation via GitOps, nest a `run_script` entry under the `policy` you want to automate, then make sure you have the same `path` field both there and in the same team's `controls > scripts` section. See the [GitOps reference documentation](https://fleetdm.com/docs/configuration/yaml-files#policies) for an example.
+
+## Conclusion
+
+Fleet now supports running scripts on hosts that fail a policy check. We showed how to set up these automations via the Fleet admin UI, our REST API, and GitOps.
+
+Host condition-related issues can be resolved by running a script on those hosts. You can now automate those resolutions inside Fleet, allowing zero-touch remediation of policy failures on hosts running fleetd.
+
+
+
+
+
+
+
+
diff --git a/articles/scripts.md b/articles/scripts.md
index 754fdf4da9d7..2fa1bf3fd946 100644
--- a/articles/scripts.md
+++ b/articles/scripts.md
@@ -37,7 +37,7 @@ Fleet UI:
Scripts run from the Fleet UI will run the next time your host checks in with Fleet. You can view the status of the script execution as well as the output in the target host's activity feed.
-Fleet API: API documentation is [here](https://fleetdm.com/docs/rest-api/rest-api#run-script)
+Fleet API: See our [REST API documentation](https://fleetdm.com/docs/rest-api/rest-api#run-script)
fleetctl CLI:
@@ -45,9 +45,13 @@ fleetctl CLI:
fleetctl run-script --script-path=/path/to/script --host=hostname
```
+## Automate a script
+
+You can tell Fleet to run a script on a host when that host fails a policy. Learn more in our [script policy automations guide](https://fleetdm.com/guides/policy-automation-run-script).
+
-
+
diff --git a/website/config/routes.js b/website/config/routes.js
index 92618498739c..50ca4d28b911 100644
--- a/website/config/routes.js
+++ b/website/config/routes.js
@@ -578,6 +578,7 @@ module.exports.routes = {
'GET /learn-more-about/uninstall-scripts': '/guides/deploy-software-packages#uninstall-script',
'GET /learn-more-about/read-package-version': '/guides/deploy-software-packages#add-a-software-package-to-a-team',
'GET /learn-more-about/fleetctl': '/guides/fleetctl',
+ 'GET /learn-more-about/policy-automation-run-script': '/guides/policy-automation-run-script',
// Sitemap