# Trigger shape

## Introduction

All process flows are created with a `trigger` shape already in place, so you can define when and how frequently the process flow will run via trigger settings:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FYMGq0sDuyj5qinlCJYEj%2Ftrigger%20-%20select%20settings.png?alt=media&#x26;token=e3086828-e662-4051-a114-f78372a4d9d2" alt="" width="308"><figcaption></figcaption></figure></div>

The `trigger` shape settings panel is split into two sections, with general trigger settings in the top pane (see 1 below) followed by available trigger types (see 2 below):&#x20;

![](https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FK08haMSmAqeKBdFFJidr%2Ftrigger%20settings%201.png?alt=media\&token=0b5dcf3c-2a71-466a-a6e4-904ee8a7b15e)

## General trigger settings

In the general `trigger settings` section, the `customise URLs for virtual environment` option can be used if you're creating [webhook](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-webhook) or [callback](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-callback) URLs for use with process flows that run in a [virtual environment](https://doc.wearepatchworks.com/product-documentation/virtual-environments).&#x20;

{% hint style="info" %}
If you don't use [virtual environments](https://doc.wearepatchworks.com/product-documentation/virtual-environments/about-virtual-environments), you can ignore this option.
{% endhint %}

## Trigger types

The following trigger types are available:&#x20;

* [Schedule](#adding-a-trigger-schedule)
* [Webhook](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-webhook)
* [Event listener](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-event-listener)&#x20;
* [Callback](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/callback-shape)

## Do I have to use a trigger shape?

When a new process flow is created, a `trigger` shape is added - by default, it's configured with an hourly `schedule`.&#x20;

Trigger shapes can't be moved or deleted, but you can change/remove the default settings as needed. If it's not appropriate to initialise a flow from the trigger shape - for example, if you're receiving data via a [Patchworks API request](https://doc.wearepatchworks.com/product-documentation/developer-hub/patchworks-core-api) - you can remove the default schedule, so no triggers are defined.