Test notification email

test_notification_email Explicitly queue a test to your saved verified recipient. Requires enabled delivery and preferences; limited to one per hour.

Name recorded in the 2026-10-27 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access still apply.

Access	Behavior
`events:read`, `notifications:write`	Writes or admits work; can change or remove existing state

This operation changes saved state. Review its inputs and retry behavior before calling.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "test_notification_email",
    "arguments": {
      "expectedRevision": 1
    }
  }
}

agentlinkops call test_notification_email --args '{"expectedRevision":1}'

curl --fail-with-body https://app.agentlinkops.com/v1/commands/test_notification_email \
  -H "Authorization: Bearer $AGENTLINKOPS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"expectedRevision":1}'

Returned result

Schema-validated example; IDs and dates are illustrative. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

{
  "id": "ntest_example",
  "state": "pending"
}

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Field	Type	Presence	Meaning and constraints
`expectedRevision`	integer	Required	Previously read revision; mismatches reject concurrent updates. minimum: `1`; maximum: `9007199254740991`

Validation and omitted values

Queues one test to the saved, enabled recipient at the supplied revision; limited to one per hour. Requires configured email delivery and preferences that are enabled and not suppressed.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.

Field	Type	Presence	Meaning and constraints
`id`	string	Required	Resource identifier returned by the operation.
`state`	string	Required	Saved lifecycle or evidence state, as enumerated for this record. must equal `"pending"`

Download input schema · Download output schema

Errors and retries

This write is not annotated idempotent. After a timeout, inspect existing state before repeating it. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

This operation has no separate resource alias. Use its generic command route in a matching environment.

Continue

list_notification_deliveries Follow the related workflow. See capability status for availability or the command index for another operation.

Overview

MCP, CLI and API commands

CLI client

HTTP and events

Optional local workflows

Test notification email

Example request

Returned result

Input fields

Validation and omitted values

Output fields

Errors and retries

HTTP resource routes

Continue

​Example request

​Returned result

​Input fields

​Validation and omitted values

​Output fields

​Errors and retries

​HTTP resource routes

​Continue

Example request

Returned result

Input fields

Validation and omitted values

Output fields

Errors and retries

HTTP resource routes

Continue