WotoHub Automation — WotoHub 自动化

WotoHub 自动化

WotoHub 自动化 is a real 创建器 outreach 技能 with OpenClaw-era integration roots and current in-place compatibility for existing 工作流s.

It connects:

product understanding 创建器 搜索 short列出 and recommendation outreach emAIl drafting batch 发送 inbox review 防护ed reply assist

Best fit:

TikTok Shop campAIgns Amazon 创建器 outreach Shopify product 种子ing recurring 创建器 prospecting and follow-up

Core de签名:

the host 模型 handles understanding and judgment the scripts handle deterministic compilation, API execution, and 状态

This 技能 is intentionally conservative around 发送ing and reply 自动化.

Release note:

wotohub-自动化 is the only canonical publish directory wotohub-自动化-release is a mirror/reference copy, not the primary release source

If you need deeper integration detAIls, read:

references/integration-contract.md references/运行time-防护rAIls.md 环境 and 凭证s

安装 dependencies:

pip 安装 -r requirements.txt

环境 variables:

WOTOHUB_API_KEY, required for 认证d actions such as 发送, inbox 访问, reply handling, and campAIgn cycles WOTOHUB_BASE_URL, optional explicit API base override, defaults to production WOTOHUB_状态_DIR, optional 状态/记录 输出 directory

凭证 scope:

WOTOHUB_API_KEY grants 访问 to 认证d WotoHub user-状态 operations treat it as a 发送 and inbox 凭证, not a harmless 搜索-only 令牌 搜索 can still 运行 without a 令牌 through open搜索, but 认证d 端点s cannot

运行time expectations:

Python with ssl avAIlable TLS verification stays enabled by default only disable TLS verification in a controlled 调试 环境 What this 技能 can do

• Product understanding

输入 can come from:

plAIn product descriptions product URLs, including TikTok Shop, Amazon, Shopify, and brand sites

Typical 输出s:

product name key selling points tar获取 audience 创建器 direction structured 搜索-ready understanding

• 创建器 搜索

Supports:

product-led 搜索 generation 过滤器s for region, language, follower count, emAIl avAIlability keyword-assisted 搜索 category-assisted 搜索 过滤器ing out already-contacted 创建器s by default

搜索 modes:

no 令牌, uses open搜索 令牌 present, uses claw搜索

• Recommendation and short列出

Supports:

ranking 搜索 结果s returning a short列出 suggesting next-step selection

Default behavior is to 停止 after recommendation and wAIt for explicit 创建器 selection before emAIl generation.

• Outreach emAIl drafting

Supports:

创建器-specific outreach draft generation host-模型-first personalized drafts HTML normalization and subject 验证 before 发送

Minimum campAIgn brief usually needs:

productName 发送erName or 签名off offerType, such as sample, pAId, or affiliate

• Batch 发送

Default 发送 path is batch-oriented.

Characteristics:

multiple 创建器s prefer a single batch API 请求 emAIl structure is normalized before execution HTML body is preferred when present

• Inbox and reply assist

Supports:

inbox 列出ing emAIl detAIl lookup thread detAIl lookup safe reply assistance conservative low-risk auto-reply handling

Anything involving price, payment, contract terms, exclusivity, shipping promises, or timing commitments should stay human-reviewed by default.

• CampAIgn cycle

Supports:

manual single 运行s cron or 调度器 single-cycle execution scheduled 搜索 understanding bridge campAIgn 状态 persistence cycle summary, 状态 summary, and human summary 输出s 成功, blocked, and fAIled exit semantics 工作流 overview Step 0, auth and 令牌 rules

搜索 does not require 记录in by default.

without 令牌, 搜索 uses open搜索 with 令牌, 搜索 uses claw搜索

These user-side steps require WOTOHUB_API_KEY:

发送 inbox replies campAIgn cycle

If you publish, 安装, or review this 技能, treat the 凭证 requirement as part of the primary operating contract, not an optional convenience.

Optional preflight 检查:

python3 scripts/preflight.py --令牌 YOUR_API_KEY

For auth detAIls, read 应用endix-auth.md.

技能 entry

Single entrypoint:

python3 wotohub_技能.py

导入ant execution note:

default host executors are auto-wired through the 技能 entry / 路由r wr应用er flow, and scripts/build_搜索_payload.py now also injects 路由r executor defaults before resolving URL 输入 in low-confidence URL cases, product_resolve.py may emit hostUrlAnalysis请求; scripts/build_搜索_payload.py now attempts automatic host URL analysis execution + writeback before continuing if host analysis still cannot be resolved, scripts/build_搜索_payload.py returns a structured needsUser输入 / error payload instead of crashing on analysis=None callers can still explicitly provide hostAnalysis / productSummary to bypass bridge execution when they already have host-side understanding

Minimal 请求 example:

{ "请求Id": "task-1", "action": "task", "type": "product_analysis",