> For the complete documentation index, see [llms.txt](https://docs.onelens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onelens.cloud/automate/workflows-and-automation/triggers.md).

# Triggers

By leveraging triggers, you can automate responses to cost anomalies, ticket updates, and scheduled reports, ensuring timely and effective decision-making.

## **Core Triggers**

Core triggers detect critical events within OneLens, allowing you to automate workflows based on fundamental cost monitoring and anomaly detection mechanisms.

### **Anomaly Detection**

#### **1. Anomaly is Detected**

Activate workflows when an anomaly is identified. You can refine the trigger with conditions such as:

* **Anomaly Impact**: Cost Impact ($), Cost Impact (%)
* **Resource**: Account, Region, Service
* **Cost Center**: Cost Center, Category

  <figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2F6NyPkPtvzF112Q5lcqAm%2FScreenshot%202025-08-04%20at%2012.49.36.png?alt=media&amp;token=9e786c3f-4870-41fd-9f02-fa6329897168" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="success" %}

## **Example**

Automatically notify FinOps teams when unexpected cloud cost spikes are detected for critical services.
{% endhint %}

### **Tickets**

#### **1. Tickets**

* **Ticket is Created/Updated**

  These allow you to trigger workflows when tickets are generated or modified. Conditions can be based on:

  * **Ticket**: Status, Category
    * **Recommendation**: Potential Savings, Effort Required
    * **Resource**: Name, Account, Region, Service, Tags
    * **Cost Center**: Cost Center, Category
    * **Policy**: Name, Category

#### **2. New Ticket Digest**

* **Daily**, **Weekly**, or **Monthly**\
  Use this to receive a digest report of all newly created tickets that meet your specified conditions.

#### **3. All Tickets Digest**

* **Daily**, **Weekly**, or **Monthly**\
  Generate a periodic report for all tickets — not just the new ones — filtered by your chosen parameters.

  <figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FhscYE84QTCJkxPVART6L%2FScreenshot%202025-08-04%20at%2012.49.44.png?alt=media&amp;token=3ba7a6db-94b7-4ac8-91db-50a8d8ac8409" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="success" %}

## **Example**

* Trigger Slack alerts to engineering managers when high-effort, high-savings tickets are generated for their services.
* Auto-update Jira issues when the status of cost optimization tickets changes in OneLens.
* Send summarized reports of newly raised cost-saving opportunities to finance leads on a weekly basis.
* Share a complete digest of all ongoing optimization tickets with cross-functional teams for better visibility.
  {% endhint %}

### **Cost Alerts**

Automatically trigger workflows when account-level, service-level, or cost center-level cost reports are generated. These are not real-time alerts but scheduled **Cost Reports** that summarize key changes.

* **Account Wise**
  * Daily, Weekly, Monthly
* **Service Wise**
  * Daily, Weekly, Monthly
* **Cost Centre Wise**

  * Daily, Weekly, Monthly

  <figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FAJJM402I1qUBjv9fUALp%2FScreenshot%202025-08-04%20at%2012.49.50.png?alt=media&amp;token=7a28b773-dbd9-4aee-957f-28cf96e14ea1" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="success" %}

## **Example**

Route cost center-level reports to business unit heads for performance and variance analysis.
{% endhint %}

### **Resource**

**New Resource Digest**

* **Daily**, **Weekly**, or **Monthly**\
  Start workflows based on discovery of newly created resources. Ideal for governance or security-related automation.

  <figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FhpNviW4nUUjfrM2cviHz%2FScreenshot%202025-08-04%20at%2012.49.58.png?alt=media&amp;token=5ba2e123-3254-422b-9142-b43792abdc78" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="success" %}

## **Example**

Inform platform teams about newly launched resources to ensure tagging compliance and governance.
{% endhint %}


---

# 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.onelens.cloud/automate/workflows-and-automation/triggers.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.
