> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Email: New Email Matching Criteria

Triggers when a new email matches your filter — by sender address or subject line. Useful for routing specific notifications or emails from certain senders.

Trigger Communications

Triggers when a new email matches your filter — by sender address or subject line. Useful for routing specific notifications or emails from certain senders.

## At a Glance

| Field | Value |
| --- | --- |
| Trigger ID | `email-new-email-matching-criteria` |
| Category | Communications |
| Tags | `email`, `communication`, `notification`, `filter`, `search` |

## Trigger Configuration

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `fromFilter` | `string` | No | Filter emails by sender address \(exact match or contains\) |
| `subjectFilter` | `string` | No | Filter emails by subject line \(contains match\) |

## Trigger Result

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `triggeredAt` | `string` | Yes | Timestamp when the event was received \(UTC, RFC3339 format\) |
| `from` | `string` | No | Sender email address |
| `to` | `array` | No | Recipient email addresses |
| `subject` | `string` | No | Email subject line |
| `text` | `string` | No | Plain text body of the email |
| `html` | `string` | No | HTML body of the email |
| `headers` | `object` | No | Email headers |

## Workflow Root Example

```json
{
  "nodes": {
    "root": {
      "type": "email-new-email-matching-criteria",
      "payload": {
        "fromFilter": "example-fromFilter",
        "subjectFilter": "example-subjectFilter"
      },
      "children": [
        "log_event"
      ]
    },
    "log_event": {
      "type": "log",
      "payload": {
        "message": "Triggered at {{$trigger.triggeredAt}}"
      },
      "children": []
    }
  }
}
```

**Reference trigger output**

Downstream nodes can use `{{$trigger.triggeredAt}}` and any result fields listed above. Event triggers usually expose the raw source payload under a field such as `event`, `body`, `trade`, or `raw`.