# Actions

After a trigger activates, actions execute predefined tasks that automate responses, such as notifying stakeholders, creating issue tickets, or managing processes.

### Core Actions

Core actions are designed to help you control how workflows progress, introducing delays or conditions that guide the next steps in the process.

<figure><img src="/files/SAOJxc8YZKmYh4o4G9QG" alt="" width="563"><figcaption></figcaption></figure>

#### **Delay**

The Delay action allows you to introduce a waiting period before executing the next step in a workflow. You can set the delay period based on:

* Hours, Days, Weeks, Months, Years

#### **Conditional**

With the **Conditional** action, you can set logic-based conditions that determine how a workflow progresses. Based on predefined parameters, workflows can take different paths, enabling flexible automation.

You can configure conditions based on the following attributes:

* **Ticket Attributes** – Status, Category
* **Recommendation Details** – Potential Savings, Effort Required
* **Resource Information** – Name, Account, Region, Service, Tags
* **Cost Center Details** – Cost Center, Category
* **Policy Information** – Name, Category

By setting these conditions, you control when a workflow moves forward.

### Ticketing Actions

Issue actions allow you to automate ticket creation and integration with external issue management systems like Jira.

#### **Jira**

The **Jira** action enables you to automatically create an issue in Jira when a workflow is triggered. To set it up, you'll need to provide the following information:

* **Connection Type** – Choose the Jira connection that OneLens will use.
* **Project** – Select the Jira project where the issue should be created.
* **Epic** – Choose the Jira epic under which the issue should be categorized.
* **Assignee Name** – Assign the issue to a specific user in Jira.

{% hint style="success" %}
**Prerequisite**: To use this action, Jira must be integrated with OneLens. If it's not yet integrated, refer to the \[Jira Integration] for setup instructions.
{% endhint %}

### Alert Actions

Messaging actions let you automate notifications, ensuring that your team or stakeholders are informed of relevant events or updates. You can use different channels, such as Slack or email, to communicate efficiently.

#### **Slack**

The **Slack** action sends notifications to either a **user** or a **channel**.

{% hint style="success" %}

## Note

You can connect your private slack channels too for the alerts.
{% endhint %}

**User Notifications:**

1. Select the **Slack connection**.
2. Choose the **user** who will receive the notification.
3. Optionally, add a **message** to provide additional context.

**Channel Notifications:**

1. Select the **Slack connection**.
2. Choose the **channel** where the alert will be posted.
3. Optionally, include a **message** with relevant details.

{% hint style="warning" %}

## **Prerequisite**&#x20;

Slack must be integrated with OneLens to use this action. If not already set up, follow the [Integration Documentation](/integrations/third-party-integrations/slack.md) for guidance.
{% endhint %}

#### **Email**

The **Email** action sends an automated email to selected recipients. When setting up the email action, you will:

1. Choose the **recipients** who will receive the email.
2. Optionally, add additional recipients in **CC** or **BCC**.
3. Define the **subject** of the email.
4. Optionally, include a **message** to provide further context.

{% hint style="warning" %}

## **Note**&#x20;

Email notifications can only be sent to users who have OneLens access.
{% endhint %}

You can combine multiple actions within a workflow, and depending on your needs, they can be executed in series, parallel, or hybrid execution types, offering flexibility to handle even complex automation scenarios.


---

# Agent Instructions: 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.onelens.cloud/automate/workflows-and-automation/actions.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.