> For the complete documentation index, see [llms.txt](https://docs.onum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onum.com/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/extraction/extract-email-addresses.md).

# Extract Email Addresses

## Description

This operation extracts email addresses from an input text using comprehensive RegEx patterns.

***

## Data types

These are the input/output expected data types for this operation:

### Input data

<img src="/files/5znsr6RzLbBq94l3YqFM" alt="" data-size="line"> - Input events to extract email addresses from.

### Output data

<img src="/files/qew1VJKqeIQckZYtmzag" alt="" data-size="line"> - List of comma-separated extracted email addresses.

***

## Parameters

These are the parameters you need to configure to use this operation (mandatory parameters are marked with a <mark style="color:red;">**\***</mark>):

<details>

<summary>Sort Results</summary>

Set this parameter to **true** if you want to sort the extracted email adresses alphabetically, or **false** if you want to display them as they appear in the original input data. The default value is **false**.

</details>

<details>

<summary>Unique Only</summary>

Set this parameter to **true** (default value) if you want to include only unique email addresses in your results.&#x20;

</details>

***

## Example

Suppose you want to **extract** all the **email addresses** from a given series of events. To do it:

1. In your Pipeline, open the required [Action](/the-workspace/pipelines/actions.md) configuration and select the input **Field**.
2. In the **Operation** field, choose **Extract Email Addresses**.
3. Set **Sort Results** to **false**.
4. Set **Unique Only** to **true**.
5. Give your **Output field** a name and click **Save**.

For example, given this input text:

```
The quarterly department meeting has been rescheduled to next Thursday. Please contact Sarah Johnson (
sjohnson384@example.net) with any conflicts. The marketing team's proposal, submitted by Michael Chen (
mchen2023@samplemail.org), received positive feedback from the board.
```

You'll get the following:

```
sjohnson384@example.net,mchen2023@samplemail.org
```

{% hint style="info" %}
You can try out operations with specific values using the **Input** field above the operation. You can enter the value in the example above and check the result in the **Output** field.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.onum.com/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/extraction/extract-email-addresses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
