# Trigger shape (event listener)

## Introduction

[Event connectors](/product-documentation/connectors-and-instances/event-connectors-beta.md) can trigger process flows by listening for events that are published to message queues/topics by a message broker (e.g. [RabbitMQ](https://www.rabbitmq.com/)).

Once an event connector is [configured](/product-documentation/connectors-and-instances/event-connectors-beta/adding-a-new-event-connector.md), it becomes available for use as a process flow trigger. 

## Need to know

* New event connectors are available for selection in process flow [trigger shapes](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-event-listener.md) as soon as they are saved successfully.
* Event connector triggers only become active when the process flow is [deployed](/product-documentation/process-flows/building-process-flows/process-flow-versioning.md#deploying-a-draft-or-inactive-version) and [enabled](/product-documentation/process-flows/managing-process-flows/enabling-and-disabling-a-process-flow/enabling-and-disabling-a-process-flow-without-virtual-enviroments.md).
* ALL messages published to selected queues/topics are passed through to the process flow.

## Adding an event connector trigger

Follow the steps below to add an event connector as a process flow trigger.

**Step 1**\
Click the **settings** icon associated with the **trigger shape** in your process flow:

<div align="left"><figure><img src="/files/nZBlKZhdCnrQUTaU7XXm" alt="" width="289"><figcaption></figcaption></figure></div>

**Step 2**\
Click the **add new event listener** button:

<div align="left"><figure><img src="/files/rssCInZ7sXoYY1hBmt2o" alt="" width="357"><figcaption></figcaption></figure></div>

...event options are displayed:

<div align="left"><figure><img src="/files/yXii0CXTvfrG0swcuh3g" alt="" width="348"><figcaption></figcaption></figure></div>

**Step 3**\
Select a **broker** from the list (all configured [event connectors](/product-documentation/connectors-and-instances/event-connectors-beta.md) are available for selection):

<div align="left"><figure><img src="/files/Jer6dYUAtlQobuYrcwmz" alt="" width="351"><figcaption></figcaption></figure></div>

**Step 4**\
Select a **queue** from the list - all configured [message queues/topics](/product-documentation/connectors-and-instances/event-connectors-beta/message-queues-topics.md) for the selected **broker** (i.e. [event connector](/product-documentation/connectors-and-instances/event-connectors-beta.md))  are available for selection:

<div align="left"><figure><img src="/files/QRwmhxtGgxXp263obNbf" alt="" width="351"><figcaption></figcaption></figure></div>

**Step 5**\
Save the shape settings.

{% hint style="info" %}
Remember that event connector triggers only become active when the process flow is [deployed](/product-documentation/process-flows/building-process-flows/process-flow-versioning.md#deploying-a-draft-or-inactive-version) and [enabled](/product-documentation/process-flows/managing-process-flows/enabling-and-disabling-a-process-flow/enabling-and-disabling-a-process-flow-without-virtual-enviroments.md).
{% endhint %}

## Related information

* [Event connectors](/product-documentation/connectors-and-instances/event-connectors-beta.md)


---

# 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://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-event-listener.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.