> 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/campaigns/action.md).

# Action

Complete accepted Campaign work and keep it connected to Measurement.

Action is the Campaign workspace where accepted opportunities become rows of work. It operates like a [Grid](/actions/grids.md), so your team can add fields, run [Playbooks](/actions/playbooks.md) and [Workflows](/actions/workflow-concepts.md), review outputs, track publishing, and manage the work tied to the Campaign.

Use **Action** after your team accepts opportunities. The goal is to keep the work connected to the Campaign, instead of moving it into a separate process where impact is harder to measure.

## How Action works

1. Accept opportunities from **Opportunities**.
2. Open **Action** in the Campaign.
3. Open an Action cell to see the approved brief, target page, and included context.
4. Edit the brief in the Action cell if the instruction should change after acceptance.
5. Add the Playbooks or Workflows your team needs to create, refresh, review, or publish the work.
6. Add publishing, ownership, and handoff fields as needed.
7. Run the work from the accepted Action rows.

Each accepted opportunity creates one Action row. The row is the durable record of the approved action, not only a page or prompt cell.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-ee72211d0b2710c143a18257d83a51d96454d504%2Fcampaign-action-01-rows.png?alt=media" alt="Campaign Action tab with target pages in the Opportunity column, Content Refresh run statuses, Refreshed Article drafts, owners, and published URLs"><figcaption><p>Each accepted opportunity becomes an Action row you can run and track.</p></figcaption></figure>

## Reuse an Action setup

For page refresh and page creation Campaigns, use **Start with template** to apply the default Action Grid for the Campaign's action type. The Campaign must be active, you must have permission to update it, and a published default template must be available. Templates apply only when the Grid has no action columns; accepted opportunity rows do not prevent you from applying one.

You can also import an Action setup from another Campaign or a standalone Grid through **Configure actions**. The import carries over columns, inputs, and Playbook or Workflow references, without copying source rows.

If the destination already has action columns, review the replacement confirmation. Importing replaces those columns and their outputs. It preserves accepted-opportunity rows, the system Action Item column, and the existing Track Event column and Measurement history. Cancel to keep the current setup. If dependencies cannot be mapped safely, the import fails without changing the setup.

## What an Action row contains

| Part                  | Use it for                                                                                                                  |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Action cell**       | The approved brief, target page, and supporting context carried over from the opportunity.                                  |
| **Playbook columns**  | Repeatable content tasks, such as refresh briefs, content updates, or review steps. See [Playbooks](/actions/playbooks.md). |
| **Workflow columns**  | Lower-level workflow processes tied to the accepted action. See [Workflows](/actions/workflow-concepts.md).                 |
| **Publishing fields** | CMS details, URLs, and handoff notes. See [Publish to CMS from Grid](/actions/grids/publish-to-cms-from-grid.md).           |

## Map Action values to Inputs

When you select an Action column as a Playbook or Workflow Input, use the secondary selector to choose the value to pass:

* **Entire Action Item:** Pass the full object. The selector uses the Action column name for this option, which remains the default for existing mappings.
* **Target page → URL** or **Target page → ID:** Pass the page URL or ID. These resolve to `null` when the Action has no target page.
* **Rationale:** Pass the editable brief.
* **Contexts:** Pass the supporting pages or prompts.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-101fbef79b505c3c9eae9f6a9a056a100d07e75f%2Fcampaign-action-02-input-mapping.png?alt=media" alt="Configure Playbook panel with page_url mapped to the Opportunity column and its value list open: Opportunity, Target page URL and ID, Rationale, and Contexts"><figcaption><p>Choose which Opportunity value to pass to each Input.</p></figcaption></figure>

AirOps saves your selection with the column mapping.

## Action JSON shape

When you pass the entire Action Item, the object contains these fields:

| Field                   | Shape            | Purpose                                                                         |
| ----------------------- | ---------------- | ------------------------------------------------------------------------------- |
| `action_item_id`        | Integer          | The Action record's ID.                                                         |
| `source_opportunity_id` | Integer          | The Opportunity that created the Action.                                        |
| `rationale`             | String           | The editable brief for the work.                                                |
| `target_page`           | Object or `null` | The page to refresh. It is `null` for a page-creation Action.                   |
| `contexts`              | Array            | All supporting pages or prompts carried over when the opportunity was accepted. |

The `target_page` object includes `web_page_id`, `url`, and `brand_kit_id`.

Each item in `contexts` includes:

* `id`: The context ID.
* `rationale`: Why the context supports the Action.
* `position`: The context's order.
* `resource`: The supporting page or prompt.

A prompt resource includes its `type`, `id`, prompt text, topic, and tags. A page resource includes its `type`, `id`, page URL, folder, and topics.

The Campaign action type, such as `page_refresh` or `page_creation`, is configured on the Campaign. It is not included in the current Action execution payload.

## Track content updates

Use the **Track Content Update** step in the Playbook or Workflow that publishes or refreshes the page. Older workflows may refer to this step as **Track Event**.

The step records a content update in AirOps so Measurement can show when the work happened alongside page performance. It does not activate the Measurement tab. Measurement is available before Action rows or tracked events exist.

### Configure the step

1. Add **Track Content Update** after the step that publishes or refreshes the page.
2. Choose the event type:
   * **Page Published** for a new page.
   * **Page Refreshed** for an existing page.
3. Pass the final public URL of the page.
4. Use the URL from the Action row or the publishing result so the event matches the page that changed.
5. Run the step only after the content is live.

The URL must be the canonical page URL. Do not include a trailing slash or query parameters. AirOps uses the URL's domain to match the event to a Brand Kit.

### Make sure Measurement can use the event

* Use the live page URL, not a preview, staging, or CMS editor URL.
* Use **Page Refreshed** when updating an existing page and **Page Published** when creating a new page.
* Keep the tracked URL consistent with the page URL in the Action row.
* Confirm that the domain belongs to the Campaign's Brand Kit.
* Check the page's content changes in Measurement after the workflow runs.

Track Content Update events help you compare page performance before and after the work. They do not replace the Action row, page scope, or connected Google Search Console and Google Analytics data.

## Good Action setup

A good **Action** setup matches the Campaign objective. Add the columns your team needs to complete the work, but avoid turning **Action** into a general project tracker.

For a page refresh Campaign, **Action** might include a refresh Playbook, CMS fields, and publish details. For a page creation Campaign, **Action** might include a brief Playbook, supporting-source fields, and publishing notes.

Keep the Action brief specific enough that a Playbook or Workflow can use it. If the instruction is still too broad, edit it in the Action cell before you run the work.

## Examples

### Page refresh Campaign

Use **Action** to refresh accepted pages from the Campaign:

1. Open the Action cell and confirm the target page and brief.
2. Add the Playbook or Workflow that drafts refresh recommendations.
3. Add publishing fields for the CMS handoff or publish URL.
4. Add ownership fields for the teammate responsible for the work.
5. Track each page through review and publishing.

### Page creation Campaign

Use **Action** to create content that supports accepted prompts:

1. Open the Action cell and confirm the included prompts.
2. Add the Playbook or Workflow that turns the brief into a draft page.
3. Add fields for supporting sources and publishing notes.
4. Track whether each accepted action has shipped.

## Use a Markdown page link in a Track Event column

In an Action Grid's **Track Event** column configuration, **Page Column** can reference a Markdown column, including a Workflow output displayed as Markdown. The cell must contain one page URL or one Markdown link, such as `[Published page](https://example.com/article)`.

A cell containing article text or several links cannot identify a single page to track. AirOps reports **Markdown cell must contain a single page URL or link** so you can correct the source cell.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/campaigns/action.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
