# New Email Matching Criteria — Mailosaur

> Emit new event when a message matching specific criteria is received. See the documentation

- Key: `mailosaur-new-email-matching-criteria`
- Type: Trigger (Polling)
- Version: 0.0.1
- App: Mailosaur (`mailosaur`) — https://pipedream.com/apps/mailosaur.md
- This page (HTML): https://pipedream.com/apps/mailosaur/triggers/new-email-matching-criteria
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/mailosaur/sources/new-email-matching-criteria/new-email-matching-criteria.mjs

## Description

Emit new event when a message matching specific criteria is received. [See the documentation](https://mailosaur.com/docs/api#search-for-messages)

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `timer` | `$.interface.timer` | Yes | Timer |
| `serverId` | `string` | Yes | The identifier of the server from which the email should be sent. Options are loaded from the connected account. |
| `sentFrom` | `string` | No | The full email address or phone number from which the target message was sent. |
| `sentTo` | `string` | No | The full email address or phone number to which the target message was sent. |
| `subject` | `string` | No | The value to seek within the target email's subject line. |
| `body` | `string` | No | The value to seek within the target message's HTML or text body. |
| `match` | `string` | Yes | If set to ALL (default), then only results that match all specified criteria will be returned. If set to ANY, results that match any of the specified criteria will be returned. |

## Returns

Events emitted by Mailosaur.

## Run it

**TypeScript**

```ts
import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const deployed = await pd.triggers.deploy({
  id: "mailosaur-new-email-matching-criteria",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    mailosaur: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    serverId: "Server ID",
  },
  webhookUrl: "https://example.com/webhooks/mailosaur",
})

console.log(deployed.id)
```

**cURL**

```bash
curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
  -H "Content-Type: application/json" \
  -H "X-PD-Environment: production" \
  -H "Authorization: Bearer {access_token}" \
  -d '{
    "external_user_id": "{external_user_id}",
    "id": "mailosaur-new-email-matching-criteria",
    "webhook_url": "https://example.com/webhooks/mailosaur",
    "configured_props": {
      "mailosaur": { "authProvisionId": "apn_xxxxxxx" },
      "timer": { "intervalSeconds": 900 },
      "serverId": "Server ID"
    }
  }'
```

**MCP**

MCP servers expose Mailosaur actions as on-demand tools.

New Email Matching Criteria is an event source, so your application deploys it with the Connect SDK or API and then either receives each event at a webhook URL or retrieves events on demand with the trigger events API.

## Event delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source. Or: no webhook required — your app or agent can fetch recent events from the [trigger events API](https://pipedream.com/docs/connect/api-reference/list-trigger-events.md) instead.

---

- App: https://pipedream.com/apps/mailosaur.md · All apps: https://pipedream.com/apps