# Adding a new event connector

## Introduction

When adding a new event connector, you step through a series of wizard-type pages to add general settings, authentication credentials, and required queues/topics.

## Need to know

* New event connectors are available for selection as **brokers** 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.

## The steps

**Step 1**\
Log into the Patchworks dashboard, then select **process flows** <mark style="color:red;">></mark> **event connectors** from the left-hand navigation menu.

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

<div align="left"><figure><img src="/files/BEHqddYaPjGzv9DYtrJe" alt=""><figcaption></figcaption></figure></div>

**Step 3**\
You're prompted to enter general settings for this connector:

<div align="left"><figure><img src="/files/k7pt2co0iFLahEZXWrxt" alt="" width="563"><figcaption></figcaption></figure></div>

Use the table below as a guide:

| Setting               | Summary                                                                                                                                                                                                                                                    |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name                  | Enter a name for the event connector, as it will identified throughout Patchworks.                                                                                                                                                                         |
| Description           | Enter a description for the event connector to provide a little more detail about its purpose.                                                                                                                                                             |
| Host                  | Enter the the address of the machine where your messaging broker (e.g. RabbitMQ) is running - typically this is an IP address or a domain name.                                                                                                            |
| Port                  | Enter the network port where RabbitMQ is listening for connections. RabbitMQ uses the AMQP (Advanced Message Queuing Protocol) for communication which, by default, listens on port `5672` for non-TLS connections and on port `5671` for TLS connections. |
| Protocol              | Select the appropriate protocol for your messaging broker.                                                                                                                                                                                                 |
| Authentication method | Currently, `basic auth` is supported.                                                                                                                                                                                                                      |

**Step 4**\
Click the **create** button.

**Step 5**\
Enter your authentication credentials for the message broker - in this case, username and password:

<div align="left"><figure><img src="/files/BphuHRlVVbbLNAAjOZ0e" alt="" width="563"><figcaption></figcaption></figure></div>

**Step 6**\
Click the **update** button.

**Step 7**\
Now you can select or add which message queue/topic to associate with this event connector:

<div align="left"><figure><img src="/files/BIcWov7vSYysRVVGdhqb" alt="" width="563"><figcaption></figcaption></figure></div>

Any existing queues are listed for selection, or you can add new queues/topics.&#x20;

{% hint style="info" %}
When you add a new queue/topic here, it is added to your message broker. You can add as many as you need - any queues/topics that you add will be available for selection when this event connector is selected as the **broker** in a process flow [trigger shape](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-event-listener.md).
{% endhint %}

**Step 8**\
Having added all required queues/topics, the event connector is ready to [use in process flows](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-event-listener.md).

## Related information

* [Trigger shape (event connector)](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-event-listener.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/connectors-and-instances/event-connectors-beta/adding-a-new-event-connector.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.