> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape.md).

# 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="/files/zNJbS3YUDDPE0lY7aWT4" 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;

![](/files/tw3XLCv66AzBefeQf6tt)

## General trigger settings

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

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

## Trigger types

The following trigger types are available:&#x20;

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

## 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](/product-documentation/developer-hub/patchworks-core-api.md) - you can remove the default schedule, so no triggers are defined.