> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/actions/playbooks/triggers.md).

# Playbook Triggers

Playbook Triggers start published Playbooks automatically. Use them when a Playbook should run on a schedule, respond to an HTTP request, monitor a condition, or react to an enabled AirOps signal.

## Overview

Triggers run a selected Playbook version and pass configured Input values into the run. Triggered runs appear in **Run History**. Runs that need Human Review also appear in the Inbox.

| Trigger         | How it works                                                                                                                 | Best for                                                              |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| **Schedule**    | Runs on a recurring cadence, such as every Monday at 9am.                                                                    | Weekly content audits, Brand Kit freshness checks, recurring reports. |
| **Webhook**     | Starts when an external system sends an HTTP request to the Playbook webhook URL.                                            | CMS publish events, form submissions, third-party integrations.       |
| **Monitor**     | Uses Parallel Web Systems to check a monitoring query every 12 hours and starts the Playbook when the condition is detected. | Competitive alerts, market monitoring, content health monitoring.     |
| **AEO Insight** | Starts when enabled AEO Insight thresholds are met, such as mention rate, share of voice, or citation rate changing.         | Programmatic refresh, competitive response, AEO coverage gaps.        |

{% hint style="info" %}
AEO Insight Triggers are available only when enabled for your workspace.
{% endhint %}

## How to Configure

Configure a Trigger after you publish the Playbook version you want downstream systems to run.

1. Open the published Playbook.
2. Click **Add Trigger**.
3. Select the Trigger type.
4. Choose **Default** or a pinned Playbook version.
5. Configure the Trigger settings.
6. Set any required Input values that should come from the Trigger.
7. Save the Trigger.
8. Review the first triggered Session in **Run History**.

For Webhook Triggers, copy the webhook URL after you save the Trigger. Send a `POST` request to that URL with the payload format below.

## Parameters

| Parameter           | Applies to   | Description                                                                                                                                                        |
| ------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Trigger type        | All Triggers | The condition that starts the Playbook, such as **Schedule**, **Webhook**, **Monitor**, or **AEO Insight**.                                                        |
| Version             | All Triggers | The Playbook version the Trigger runs. **Default** follows the current published version. A pinned version keeps running the selected version until you change it. |
| Input configuration | All Triggers | Values the Trigger passes into the Playbook run. Required Inputs need a value from the Trigger configuration or the webhook payload.                               |
| Webhook URL         | Webhook      | The URL external systems call to start the Playbook. Copy this URL from the Webhook Trigger configuration.                                                         |
| Request body        | Webhook      | JSON body containing an `inputs` object with Playbook Input variable names as keys.                                                                                |

{% hint style="warning" %}
If a new Playbook version changes Inputs, update any Grid column mappings and Trigger Input configuration before running at scale. New required Inputs without mapped or configured values can make runs fail validation or be skipped.
{% endhint %}

## Webhook Payload Format

The request body must include an `inputs` object. Each key inside `inputs` should match a Playbook Input variable name.

To find or edit an Input variable name, open the Input and click **Show Advanced Settings**.

```json
{
  "inputs": {
    "value": "overridden value input",
    "non_req": "optional override",
    "non_req_2": "another optional override"
  }
}
```

| Field                          | Required             | Description                                                                                                                                                                                                                                      |
| ------------------------------ | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `inputs`                       | Yes                  | Object containing the Playbook Input values for the run.                                                                                                                                                                                         |
| `inputs.<input_variable_name>` | Depends on the Input | Value for a Playbook Input. Use the Input variable name, not the display label. Required Inputs need a value from the Trigger configuration or the webhook payload. Optional Inputs can be omitted unless you want to override them for the run. |

## Examples

### Webhook request

Replace `WEBHOOK_TRIGGER_URL` with the URL AirOps gives you when you configure the Webhook Trigger.

```bash
curl --request POST \
  --url 'WEBHOOK_TRIGGER_URL' \
  --header 'content-type: application/json' \
  --data '{
    "inputs": {
      "value": "overridden value input",
      "non_req": "optional override",
      "non_req_2": "another optional override"
    }
  }'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.airops.com/actions/playbooks/triggers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.