sendookRead and send emails from an existing Sendook inbox. Use when an AI agent needs to check for new emails, read messages, reply to conversations, or send new emails from a pre-configured inbox. Limited to message operations only β no inbox creation, domain management, or webhook configuration.
Install via ClawdBot CLI:
clawdbot install obaid/sendookRead and send emails from an existing Sendook inbox.
Scope Limitations: This skill can ONLY read and send emails from a pre-configured inbox. You CANNOT create or delete inboxes, manage domains, manage webhooks, or manage API keys. Do not attempt these operations β they are not available.
Install the skill into your OpenClaw workspace:
clawhub install sendook-openclaw
This adds the skill to your workspace's skills/ directory. OpenClaw will automatically pick it up on the next session start.
Set these in your OpenClaw workspace or shell environment:
SENDOOK_API_KEY β Your Sendook API keySENDOOK_INBOX_ID β The inbox ID this agent is allowed to useInstall the SDK (npm | source):
npm install @sendook/node
import Sendook from "@sendook/node";
const client = new Sendook(process.env.SENDOOK_API_KEY);
const INBOX_ID = process.env.SENDOOK_INBOX_ID;
Both environment variables are required. Use a least-privileged API key scoped to the target inbox only.
// List all messages in the inbox
const messages = await client.inbox.message.list(INBOX_ID);
// Search messages (regex-based search across to/from/cc, subject, and body)
const results = await client.inbox.message.list(INBOX_ID, "invoice");
# List all messages
curl https://api.sendook.com/v1/inboxes/$SENDOOK_INBOX_ID/messages \
-H "Authorization: Bearer $SENDOOK_API_KEY"
# Search messages
curl "https://api.sendook.com/v1/inboxes/$SENDOOK_INBOX_ID/messages?query=invoice" \
-H "Authorization: Bearer $SENDOOK_API_KEY"
const message = await client.inbox.message.get(INBOX_ID, "msg_def456");
curl https://api.sendook.com/v1/inboxes/$SENDOOK_INBOX_ID/messages/msg_def456 \
-H "Authorization: Bearer $SENDOOK_API_KEY"
Response:
{
"id": "msg_def456",
"from": "sender@example.com",
"to": ["support@yourdomain.com"],
"subject": "Question about my order",
"text": "Hi, I have a question about order #12345...",
"html": "<p>Hi, I have a question about order #12345...</p>",
"labels": [],
"threadId": "thread_ghi789",
"createdAt": "2025-01-15T10:35:00Z"
}
const threads = await client.inbox.thread.list(INBOX_ID);
curl https://api.sendook.com/v1/inboxes/$SENDOOK_INBOX_ID/threads \
-H "Authorization: Bearer $SENDOOK_API_KEY"
Retrieve a full conversation with all messages.
const thread = await client.inbox.thread.get(INBOX_ID, "thread_ghi789");
// thread.messages contains all messages in the conversation
curl https://api.sendook.com/v1/inboxes/$SENDOOK_INBOX_ID/threads/thread_ghi789 \
-H "Authorization: Bearer $SENDOOK_API_KEY"
await client.inbox.message.send({
inboxId: INBOX_ID,
to: ["recipient@example.com"],
subject: "Hello from Sendook",
text: "Plain text body",
html: "<h1>Hello</h1><p>HTML body</p>",
});
curl -X POST https://api.sendook.com/v1/inboxes/$SENDOOK_INBOX_ID/messages/send \
-H "Authorization: Bearer $SENDOOK_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": ["recipient@example.com"],
"subject": "Hello from Sendook",
"text": "Plain text body"
}'
Important: Always confirm with the user before reading any local file to attach. Only attach files the user has explicitly requested. Never read files outside the current working directory or project scope (e.g., no~/.ssh,~/.env,/etc, or credential files).
import { readFileSync } from "fs";
import { resolve } from "path";
// Only attach files explicitly provided by the user
const filePath = resolve("./reports/report.pdf");
await client.inbox.message.send({
inboxId: INBOX_ID,
to: ["recipient@example.com"],
subject: "Report attached",
text: "Please find the report attached.",
attachments: [
{
content: readFileSync(filePath).toString("base64"),
name: "report.pdf",
contentType: "application/pdf",
},
],
});
await client.inbox.message.reply({
inboxId: INBOX_ID,
messageId: "msg_def456",
text: "Thanks for your email! We'll look into this.",
html: "<p>Thanks for your email! We'll look into this.</p>",
});
curl -X POST https://api.sendook.com/v1/inboxes/$SENDOOK_INBOX_ID/messages/msg_def456/reply \
-H "Authorization: Bearer $SENDOOK_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text": "Thanks for your email! We'\''ll look into this."}'
List recent emails, read the latest, and reply:
import Sendook from "@sendook/node";
const client = new Sendook(process.env.SENDOOK_API_KEY);
const INBOX_ID = process.env.SENDOOK_INBOX_ID;
// 1. List recent messages
const messages = await client.inbox.message.list(INBOX_ID);
if (messages.length > 0) {
// 2. Read the latest message
const latest = await client.inbox.message.get(INBOX_ID, messages[0].id);
console.log(`From: ${latest.from}`);
console.log(`Subject: ${latest.subject}`);
console.log(`Body: ${latest.text}`);
// 3. Reply to it
await client.inbox.message.reply({
inboxId: INBOX_ID,
messageId: latest.id,
text: `Thanks for reaching out! We received your message about "${latest.subject}".`,
});
}
// 4. Send a new email
await client.inbox.message.send({
inboxId: INBOX_ID,
to: ["team@example.com"],
subject: "Daily inbox summary",
text: `Processed ${messages.length} messages today.`,
});
try {
await client.inbox.message.send({
inboxId: INBOX_ID,
to: ["recipient@example.com"],
subject: "Hello",
text: "Body",
});
} catch (error) {
if (error.response) {
console.error(error.response.status, error.response.data);
} else if (error.request) {
console.error("No response:", error.request);
} else {
console.error("Error:", error.message);
}
}
| Status | Meaning |
|---|---|
| 400 | Bad request β check parameters (missing to, subject, etc.) |
| 401 | Unauthorized β invalid or missing API key |
| 404 | Message or thread not found |
| 429 | Rate limit exceeded β retry with backoff |
| 500 | Internal server error |
| Method | Description |
|---|---|
| client.inbox.message.list(inboxId, query?) | List or search messages |
| client.inbox.message.get(inboxId, messageId) | Get a specific message |
| client.inbox.message.send(options) | Send a new email |
| client.inbox.message.reply(options) | Reply to a message |
| client.inbox.thread.list(inboxId) | List conversation threads |
| client.inbox.thread.get(inboxId, threadId) | Get thread with all messages |
No other methods are available in this skill. Do not attempt to create/delete inboxes, manage domains, configure webhooks, or manage API keys.
AI Usage Analysis
Analysis is being generated⦠refresh in a few seconds.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Query the DeepWiki MCP server for GitHub repository documentation, wiki structure, and AI-powered questions.
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Use when reviewing pull requests, checking for security issues,...
Essential Git commands and workflows for version control, branching, and collaboration.
Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.