# Triggers

## Setup

Go to the Triggers page under Settings to start creating triggers. Triggers will always be organized into a folder to help your team stay organized. Once you hit "create trigger" you'll have the option to select from various premade templates or start from scratch.

### [​](https://docs.usepylon.com/platform/triggers#kickoffs)Kickoffs <a href="#kickoffs" id="kickoffs"></a>

Every trigger is activated by change(s) in state for an Issue, Account, or Contact. View our full list of trigger conditions, [here](https://app.usepylon.com/settings/triggers/create).&#x20;

<figure><img src="/files/RJBhwIrKj7EPm3jKrzMb" alt="" width="316"><figcaption></figcaption></figure>

### [​](https://docs.usepylon.com/platform/triggers#conditions)Conditions <a href="#conditions" id="conditions"></a>

#### Filters <a href="#conditions" id="conditions"></a>

Narrow down the specific conditions of when this trigger should be executed by applying filters. Select from many default and custom attributes on issues, accounts, and contacts. The default logic is an "AND" operator meaning all criteria must be met, but you can also create more complex combinations of "AND" + "OR" by selecting "Create Filter Group" from the dropdown.

<figure><img src="/files/ROnZUMe609xpIM628uk4" alt="" width="375"><figcaption><p>Condition for support issues from customers with spend below 5k</p></figcaption></figure>

#### Time Delay <a href="#actions" id="actions"></a>

Time delay conditions allow you to delay the action taken based on either wall clock time or your defined support hours (i.e. setting SLA breaches to only count time passed during support hours).

<figure><img src="/files/sgOymiKhfkG9qBMRskmw" alt=""><figcaption><p>A trigger to autoclose issues after 3 days of customer inactivity</p></figcaption></figure>

#### AI <a href="#actions" id="actions"></a>

Use AI filters to intelligently route issues between teams or provide specific responses in specific situations.

<figure><img src="/files/5MojqZJSwuIRMgHl44U2" alt=""><figcaption></figcaption></figure>

### [​](https://docs.usepylon.com/platform/triggers#actions)Actions <a href="#actions" id="actions"></a>

Pick from a set of actions to take when the conditions of the trigger are met. Chain many distinct actions together. Actions include sending notifications, auto-replying to issues, setting field values in Pylon, custom actions in external systems, and many more.

<figure><img src="/files/GFNOuwQ8yEvU3pPss9Ey" alt=""><figcaption><p>An action sequence of assigning an issue to the support team and DMing the assignee a message.</p></figcaption></figure>

***

### Organization

Triggers are executed in order from top to bottom for a given kickoff event. You can separate triggers into groups for easier management.

<figure><img src="/files/oBe0TeRQhB3iV0W2L1Rp" alt=""><figcaption></figcaption></figure>

### Recipes

Select from many pre-built templates of common automations.

<figure><img src="/files/WHoNC3fH6XBZ13AaEDRP" alt=""><figcaption></figcaption></figure>


---

# 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.usepylon.com/pylon-docs/platform/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.