Mailosaur ACTION
Search Email
Search for received emails in a server matching specified criteria. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Mailosaur account once, then configure and run Search Email from your backend or agent.
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 result = await pd.actions.run({
id: "mailosaur-search-email",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
mailosaur: { authProvisionId: "apn_xxxxxxx" },
serverId: "Server ID",
receiveAfter: "Receive After",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "mailosaur-search-email",
"configured_props": {
"mailosaur": { "authProvisionId": "apn_xxxxxxx" },
"serverId": "Server ID",
"receiveAfter": "Receive After"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "mailosaur",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "mailosaur-search-email",
arguments: {
serverId: "Server ID",
receiveAfter: "Receive After",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
serverId Server ID | string | The identifier of the server from which the email should be sent. Required Dynamic |
receiveAfter Receive After | string | Limits results to only messages received after this date/time. Optional |
page Page | integer | Used in conjunction with itemsPerPage to support pagination. Optional |
itemsPerPage Items Per Page | integer | A limit on the number of results to be returned per page. Can be set between 1 and 1000 items, default is 50. Optional |
dir Direction | string | Optionally limits results based on the direction ( Sent or Received). Optional |
sentFrom Sent From | string | The full email address from which the target message was sent. Optional |
sentTo Sent To | string | The full email address to which the target message was sent. Optional |
subject Subject | string | The value to seek within the target email's subject line. Optional |
body Body | string | The value to seek within the target message's HTML or text body. Optional |
match Match | string | If set to ALL (default), only results matching all criteria will be returned. If set to ANY, results matching any criteria will be returned. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- mailosaur-search-email
- Version
- 0.0.3
- App
- Mailosaur
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗