Postmark Email

Access Postmark's transactional email platform via the Postmark API. Inspect outbound messages, templates, and delivery events. Review bounce, spam, and engagement statistics. Manage webhooks and message streams.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Postmark API access yourself.

Setup in 3 Steps

Step 1: Install	Step 2: Pair Account	Step 3: Connect Postmark
		App-specific connection GIF coming soon
Run the install command in OpenClaw	Sign in and approve the device	Open the dashboard and connect Postmark

How It Works

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│  Postmark API   │
│   (User Chat)   │     │   (API Key)  │     │                  │
└─────────────────┘     └──────────────┘     └──────────────────┘
          │                       │                       │
          │  1. Install Plugin   │                       │
          │2. Pair Device      │                       │
          │3. Connect Postmark  │                       │
          │                      │  4. Secure Proxy      │
          │                      │  5. API Requests      │
          │                      │                       │
          ▼ ▼                       ▼
    ┌──────────┐           ┌──────────┐           ┌──────────┐
    │  SKILL   │           │ Dashboard│           │ Postmark │
    │  File    │           │ Auth     │           │ Platform │
    └──────────┘           └──────────┘           └──────────┘

Install

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Postmark again."

Quick Start

# Get outbound overview
clawlink_call_tool --tool "postmark_get_outbound_overview" --params '{}'

# Search outbound messages
clawlink_call_tool --tool "postmark_search_outbound_messages" --params '{"status": "sent"}'

# List templates
clawlink_call_tool --tool "postmark_list_templates" --params '{}'

Authentication

All Postmark tool calls are authenticated automatically by ClawLink using the user's Postmark account.

No API key is required in chat. ClawLink stores the API key securely and injects it into every Postmark API request on the user's behalf.

Getting Connected

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=postmark and connect Postmark.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management

List Connections

clawlink_list_integrations

Response: Returns all connected integrations. Look for postmark in the list.

Verify Connection

clawlink_list_tools --integration postmark

Response: Returns the live tool catalog for Postmark.

Reconnect

If Postmark tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=postmark
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration postmark

Security& Permissions

• Access is scoped to messages, templates, streams, and webhooks within the connected Postmark server.
• All write operations require explicit user confirmation. Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
• Destructive actions (delete template, delete webhook, archive stream) must be confirmed.
• Server configuration changes affect all email sending on that server.

Tool Reference

Message Streams

Outbound Messages

Inbound Messages

Templates

Bounces & Spam

Statistics & Engagement

Suppressions

Webhooks

Inbound Rules

Server Configuration

Code Examples

Get outbound overview

clawlink_call_tool --tool "postmark_get_outbound_overview" \
  --params '{
    "from": "2024-01-01",
    "to": "2024-01-31"
  }'

Search outbound messages

clawlink_call_tool --tool "postmark_search_outbound_messages" \
  --params '{
    "recipient": "customer@example.com",
    "status": "sent",
    "tag": "welcome"
  }'

Get template details

clawlink_call_tool --tool "postmark_get_template" \
  --params '{
    "template_id": "TEMPLATE_ID"
  }'

Create a webhook

clawlink_call_tool --tool "postmark_create_webhook" \
  --params '{
    "url": "https://example.com/webhook/postmark",
    "triggers": {
      "open": true,
      "click": true,
      "bounce": true,
      "spam_complaint": true
    },
    "http_headers": {
      "Authorization": "Bearer secret_token"
    }
  }'

List suppressions

clawlink_call_tool --tool "postmark_list_suppressions" \
  --params '{
    "message_stream": "outbound"
  }'

Discovery Workflow

1. Call clawlink_list_integrations to confirm Postmark is connected.
2. Call clawlink_list_tools --integration postmark to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration postmark.
5. If no Postmark tools appear, direct the user to https://claw-link.dev/dashboard?add=postmark.

Execution Workflow

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → search → describe → call                      │
│                                                             │
│  Example: Get outbound overview → List templates → Report  │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                     │
│  list → get → describe → preview → confirm → call           │
│                                                             │
│  Example: Describe tool → Preview changes → User approves   │
│           → Execute update                                  │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.
4. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Notes

• Postmark API has rate limits. Use exponential backoff when encountering 429 errors.
• SpamComplaint suppressions cannot be removed from the suppression list — only HardBounce and ManualSuppression can be deleted.
• Archived message streams are permanently deleted after 45 days.
• Webhook triggers require link tracking to be enabled for click and open events.
• Date range filters use ISO 8601 format (YYYY-MM-DD).

Error Handling

Troubleshooting: Tools Not Visible

1. Check that the ClawLink plugin is installed:

   openclaw plugins list
   

2. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.
3. If a fresh chat does not help, run:

   openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
   openclaw gateway restart
   

4. After restart, tell the user to send /new again and retry.

Troubleshooting: Invalid Tool Call

1. Ensure the integration slug is exactly postmark.
2. Use clawlink_describe_tool to verify parameter names and types before calling.
3. For write operations, always call clawlink_preview_tool first.

Resources

• Postmark API Documentation
• Message Streams API
• Templates API
• Webhooks API
• ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=postmark-email
• ClawLink Docs: https://docs.claw-link.dev/openclaw
• ClawLink Verification: https://claw-link.dev/verify

Related Skills

• Postmark — For this skill's native documentation

Powered by ClawLink — an integration hub for OpenClaw