# Customize PSA ticket triggers

## Introduction

In Rewst, setting specific trigger criteria for PSA Ticket triggers can be crucial to ensuring that workflows are initiated only under certain conditions. This page provides a step-by-step approach to customizing these triggers.

***

## Getting Started with Trigger Setup

### Create the workflow

In the Rewst platform:

1. Navigate to **Automations > Workflows > Create Workflow**.
2. Enter a workflow name, like `My First Webhook Trigger`.
3. Click **Submit** to proceed to a blank workflow creation screen.
4. Add a single [no-op](/documentation/automations/actions-in-rewst/core-actions.md#no-operation-noop) action to the canvas. Name it `BEGIN`. Click **Publish** to save your workflow. No other actions are needed, as you'll just be working with triggers.
5. Click **Add Trigger** at the top of your workflow builder.

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

### **Create the trigger**

1. Name your trigger.
2. Toggle **Enable** on.
3. Choose the trigger type relevant to your particular PSA ticket system:
   1. ConnectWise PSA: **Ticket Record Saved**.
   2. Datto PSA: **Ticket Webhook**
      1. Note: Ensure that webhooks are enabled as per [Rewst Documentation](https://docs.rewst.help/documentation/integrations/psa/autotask-datto-psa/webhook-configuration).
   3. Halo PS&#x41;**:** **New Ticket Record**.
4. Click on the graph button under the **Trigger Criteria** section.

<div align="left"><figure><img src="/files/duEHICSCKtwpmVtGAO8z" alt="" width="404"><figcaption></figcaption></figure></div>

The trigger is now active and will capture data when a new ticket is submitted. This screen is listening for your ticket records to be saved, and will show you live results as they come in.

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

***

## Testing the Trigger with a PSA Ticket

To see the trigger in action follow the below steps

### **Creating a Test Ticket**

* In your PSA system, create and classify a new ticket with desired criteria.
* Submit the ticket.
* You should see the ticket record appear in Rewst.

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

{% hint style="info" %}
Once the ticket is visible in Rewst, click the pause button to stop more tickets from coming in while you're building your trigger criteria.
{% endhint %}

### **Selecting Criteria**

Find and click the values in the ticket you want as trigger criteria. They will have their corresponding path entered into the Trigger Criteria on the right.

<figure><img src="/files/7ral5KK5rokN9H2Hm65b" alt=""><figcaption></figcaption></figure>

***

## Finalizing and Implementing Trigger Criteria

### **Saving Your Criteria**

* After selecting all desired criteria, click `Save` then `Close`.
* Your trigger criteria are now set and visible.

### **Applying Criteria to Workflows**

* Copy these criteria values.
* Paste them into other workflows you are configuring.

<figure><img src="/files/3A7yuXwVGMUSab7zJSj3" alt=""><figcaption></figcaption></figure>

***

## Conclusion

This process allows for precise control over when your workflows are triggered, enhancing the automation's effectiveness. Experiment with different criteria to tailor your workflows to specific needs.


---

# 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.rewst.help/documentation/automations/intro-to-triggers/use-cases-and-examples/customizing-psa-ticket-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.