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

# Stage Actions

Automate workflows in Pipelines and Lists by triggering actions when resources change stages or when scheduled dates are reached.

Stage Actions allow you to connect changes in your workspace to automated operations. Instead of manually sending notifications, initiating research, or updating records, you can configure actions that execute when defined conditions are met.

Stage Actions are available in **Pipelines** and **Lists**, with different trigger mechanisms depending on the resource.

### Stage Actions in Pipelines

Pipeline Stage Actions execute when cards enter, exit, or are added to a particular stage. They are useful for automating investment workflows, due diligence, approval processes, and other structured activities.

#### Creating a Pipeline Stage Action

1. Open a **Pipeline** from your workspace.
2. Select the **Properties** tab in the right sidebar.
3. Locate **Stage Actions** and click **New Stage Action**.
4. Select the **Stage** where the action should apply.
5. Enter a descriptive **Name** for the action.
6. Choose an **Action** and configure its required settings.
7. Select a **Trigger** to determine when the action executes.
8. Save the Stage Action and enable its toggle.

You can configure multiple Stage Actions within the same Pipeline, including different actions associated with the same stage.

#### Pipeline Triggers

Pipeline Stage Actions support three trigger types:

| Trigger        | Behavior                                                                                |
| -------------- | --------------------------------------------------------------------------------------- |
| On Stage Entry | Executes when a card is added or moved into the selected stage.                         |
| On Stage Exit  | Executes when a card moves out of the selected stage or is removed from the Pipeline.   |
| On Card Added  | Executes when a card without an existing stage is added directly to the selected stage. |

For example, a due diligence Pipeline could notify an analyst when an investment enters **In Review**, initiate additional research when it enters **Follow-up Required**, or start an approval workflow when it reaches **Approved**.

### Available Actions

Stage Actions support several automated operations across workspace resources and connected services.

| Action                        | Description                                                                    |
| ----------------------------- | ------------------------------------------------------------------------------ |
| **Send Webhook**              | Send the stage event to a configured workspace webhook.                        |
| **Send Alert**                | Notify selected workspace members through their enabled notification channels. |
| **Start Orchestration**       | Initiate an Orchestration run using the stage event as input.                  |
| **Start Agents Task**         | Start an Agents task using configured instructions.                            |
| **Write List Record**         | Create or update a native List record using explicit column mappings.          |
| **Move Resource to Pipeline** | Move a selected resource into a specified Pipeline stage.                      |

The configuration fields depend on the selected action. For example, **Send Alert** requires recipients and a message, while **Start Agents Task** uses instructions defining the work to perform.

#### Configuring Alerts

To send notifications automatically:

1. Select **Send Alert** from the Action dropdown.
2. Choose the Pipeline stage and trigger.
3. Select one or more workspace members under **Recipients**.
4. Enter the notification **Message**.
5. Save and enable the action.

Notifications are delivered through the recipients' enabled notification channels.

### Stage Actions in Lists

Lists support date-based Stage Actions that execute when a record reaches a date specified in a List column.

Unlike Pipeline Stage Actions, which respond to card movement, List Stage Actions are driven by date values.

#### Creating a List Stage Action

1. Open a **List** and navigate to **Properties**.
2. Add a date column to the List if one does not already exist.
3. Expand **Stage Actions**.
4. Select the date column that should trigger the action.
5. Configure the **Date-only Time** and **Timezone**.
6. Add a Stage Action and provide its name.
7. Choose the action and select **On Date Reached** as the trigger.
8. Complete the action-specific configuration.
9. Enable the action and click **Save Stage Actions**.

#### Date-Based Execution

The **On Date Reached** trigger executes once per date value using the configured time and timezone for date-only values.

For example, a List tracking investor relationships could include a **Next Email Interaction** column. When a record reaches its scheduled date, a Stage Action could send a reminder to the responsible workspace member at 9:00 AM in the selected timezone.

Date-based actions operate across the underlying List and are **not restricted by the filters applied to the current List view**.

A connected Data Source is optional for configuring these actions.

### Managing Stage Actions

{% hint style="info" %}
**Stage Action Limits**

Limits apply to the entire Pipeline or List. Plus includes one Stage Action per resource, Pro includes five, and Premium includes ten. Enterprise has no per-resource limit. List limits are shared across columns and views.
{% endhint %}

Existing Stage Actions can be managed from the resource's **Properties** panel.

You can expand an action to review its configuration, modify its settings, use its toggle to enable or disable execution, or delete it when it is no longer needed.

For Lists, use **Save Stage Actions** to persist changes to the configuration.

### Run Status & Troubleshooting

Open **Properties › Inspect Runs** to review recent Stage Action activity. In a Pipeline, you can also open the status indicator on the relevant stage or in the toolbar when it is shown. In a List, look for the indicator on the Date column that owns the action. Show the column if it is hidden in the current view.

Select a delivery to read its outcome and, where available, follow the linked Agents task or orchestration run. For an orchestration, inspect its execution steps, outputs, and any review it is waiting on. The inspector distinguishes **Event Received**, **Action Delivery**, and the linked **Orchestration Run** or **Agents Task** when one is available. The steps and linked work you can see depend on your access.

{% hint style="info" %}
**Delivery and Run Status Are Separate**

A successful delivery means the Stage Action handed off the work. The resulting Agents task or orchestration may still be running, paused, waiting for review, or finished with unsuccessful steps. Open the linked execution to see what happened.
{% endhint %}

| What You See                 | What to Check                                                                                                                                                                                                                                                                       |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No delivery                  | Check that the action is saved and enabled. For a Pipeline, confirm the card transition matches the selected trigger. For a List, confirm the Date column has a value and check the configured time and time zone. The current view's record filters do not scope the date trigger. |
| Queued or running            | Open the available delivery or linked execution and check its latest recorded step.                                                                                                                                                                                                 |
| Waiting for review or paused | Open the linked work if you have access. Check the review request or pause reason and follow the available controls in that workflow.                                                                                                                                               |
| Failed or skipped            | Check the recorded reason, then verify the action's inputs, destination, connected account, and current permissions. For Agent work, also check relevant model, credit, or workspace approval requirements.                                                                         |

{% hint style="warning" %}
**Check the Destination Before Repeating an Event**

Inspecting a delivery leaves the original execution as it was. Before moving a card again or changing a date to trigger another delivery, check whether the earlier action already updated a record or sent a notification.
{% endhint %}

### Best Practices

* **Use descriptive names.** Identify the event and intended outcome, such as "Notify Analyst on Review Entry."
* **Select precise triggers.** Distinguish between entering a stage, leaving a stage, and adding a new card.
* **Configure recipients carefully.** Ensure notifications reach the workspace members responsible for the next action.
* **Use consistent date columns.** For List automations, maintain accurate dates and select the appropriate timezone.
* **Review automated activity.** Use Inspect Runs to monitor executions and investigate unexpected behavior.

Stage Actions help turn Pipelines and Lists into operational workflows, connecting resource activity with notifications, agent execution, orchestration, and structured data updates.

#### Related Pages

{% content-ref url="/pages/7BJEpRZdcT1TI0sS9VoP" %}
[Pipelines](https://docs.countercyclical.io/workspaces/pipelines.md)
{% endcontent-ref %}

{% content-ref url="/pages/OKDqbPxLj9iLJJNg9nuF" %}
[Custom Alerts](https://docs.countercyclical.io/notifications/custom-alerts.md)
{% endcontent-ref %}

{% content-ref url="/pages/x5NcwZqAn0tjF3KR1AXS" %}
[Inspection](https://docs.countercyclical.io/agents/orchestrations/inspection.md)
{% endcontent-ref %}

{% content-ref url="/pages/NBKiHW45t5XOh9G14D5a" %}
[Research Monitors](https://docs.countercyclical.io/agents/research-monitors.md)
{% endcontent-ref %}
