---
title: Private Actions Overview
description: >-
  Allow workflows and apps to interact with private network services using
  private action runners with secure authentication.
breadcrumbs: Docs > Actions > Private Actions Overview
---

# Private Actions Overview

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site). ().
{% /alert %}

{% /callout %}

Private actions allow your Datadog workflows and apps to interact with services hosted on your private network without exposing them to the public internet. To use private actions, you must install a private action runner on a host in your network and pair the runner with a [connection](https://docs.datadoghq.com/service_management/workflows/connections/).

The recommended way to install a private action runner is through the [Datadog Agent](https://docs.datadoghq.com/agent/) (version `7.77.0` or later). This method supports Linux, Windows, and Kubernetes environments. Alternatively, you can install the runner as a standalone Docker container or [Kubernetes](https://github.com/DataDog/helm-charts/tree/main/charts/private-action-runner) deployment. See [Use Private Actions](https://docs.datadoghq.com/actions/private_actions/use_private_actions) for installation instructions.

{% alert level="danger" %}
To install a private action runner, your organization must have [Remote Configuration](https://docs.datadoghq.com/remote_configuration) enabled.
{% /alert %}

When you first start the runner, it generates a private key for authentication with Datadog's servers. This private key is never accessible by Datadog and ensures you exclusive access. Datadog uses a public key derived from the private key as the means to authenticate specific runners.

## How it works{% #how-it-works %}

The private action runner continuously polls for tasks from your Datadog account, executes them by interacting with your internal service, and reports the result back to Datadog.

{% image
   source="https://datadog-docs.imgix.net/images/service_management/private_action_runner_-_diagram_workflow.9034fc43fe904c71755911b987a8475e.png?auto=format"
   alt="Overview diagram illustrating how Private actions work" /%}

## Monitor your Private Action Runners with Datadog Metrics{% #monitor-your-private-action-runners-with-datadog-metrics %}

While setting up your Private Action Runners, you can enable observability metrics to monitor your runners' health and private action usage. These metrics can be used in Datadog products like Dashboards and Monitors. To get started quickly, you can use the provided [out-of-the-box Dashboard](https://app.datadoghq.com/dash/integration/private_actions_runner).

## Further reading{% #further-reading %}

- [App Builder Connections](https://docs.datadoghq.com/service_management/app_builder/connections)
- [Workflow Connections](https://docs.datadoghq.com/service_management/workflows/connections)
- [Use Private Actions](https://docs.datadoghq.com/actions/private_actions/use_private_actions)
- [Run a Script with the Private Action Runner](https://docs.datadoghq.com/actions/private_actions/run_script)
- [Handling Private Action Credentials](https://docs.datadoghq.com/actions/private_actions/private_action_credentials)
- [Remediate Kubernetes incidents faster using private actions in your apps and workflows](https://www.datadoghq.com/blog/private-actions/)
- [How we created a single app to automate repetitive tasks with Datadog Workflow Automation, Datastore, and App Builder](https://www.datadoghq.com/blog/pm-app-automation/)