← 返回
沟通协作 中文

Ironclaw Outreach Sequencer

Create and manage multi-step outreach sequences — LinkedIn messages, cold emails, and follow-ups with personalization. Use when asked to "send outreach", "cr...
创建并管理多步骤外展流程,包括LinkedIn消息、冷邮件和个性化跟进。适用于要求“发送外展”等指令时。
aspenas
沟通协作 clawhub v1.0.0 1 版本 100000 Key: 无需
★ 0
Stars
📥 1,110
下载
💾 17
安装
1
版本
#latest

概述

Outreach Sequencer — Multi-Step Personalized Campaigns

Design, schedule, and execute multi-step outreach sequences across LinkedIn and email. Each message is personalized per lead using their profile data from DuckDB.

Sequence Templates

Template 1: LinkedIn Connection + Message

Day 0: Send LinkedIn connection request (with note)
Day 1: If accepted → Send intro message
Day 3: If no reply → Follow-up message
Day 7: If no reply → Break-up / value-add message

Template 2: Cold Email Sequence

Day 0: Initial cold email
Day 3: Follow-up (reply to original thread)
Day 7: Value-add email (case study, resource)
Day 14: Break-up email ("closing the loop")

Template 3: Multi-Channel

Day 0: LinkedIn connection request
Day 2: Cold email (if not connected on LinkedIn)
Day 4: LinkedIn message (if connected) OR email follow-up
Day 7: Final touch (whichever channel they engaged on)

Personalization Engine

Each message is generated per-lead using their DuckDB profile data. Use these variables:

VariableSourceExample
---------------------------
{first_name}Name field (split)"Jane"
{company}Company field"Acme Corp"
{title}Title field"CTO"
{mutual}Shared connections/background"Stanford"
{trigger}Why reaching out now"saw your Series A"
{value_prop}What you offer them"AI-powered analytics"
{pain_point}Their likely challenge"scaling engineering team"

Personalization Rules

  • Never use generic openers like "I hope this finds you well"
  • Reference something specific: recent post, company news, shared background
  • Keep LinkedIn messages under 300 chars (connection note limit)
  • Keep cold emails under 150 words (respect attention)
  • Vary language across leads — don't send identical messages to people at the same company
  • Match tone to seniority: C-suite gets concise/strategic, ICs get technical/peer-level

Message Generation Pattern

1. Read lead profile from DuckDB
2. Identify personalization hooks:
   - Shared background (school, company, location)
   - Recent company news (web search if needed)
   - Role-specific pain points
3. Select message template for sequence step
4. Generate personalized message
5. Store message + status in DuckDB

Execution

LinkedIn Messages (via Browser)

browser → open LinkedIn messaging
browser → search for recipient
browser → open conversation
browser → type personalized message
browser → send
→ Update DuckDB status: "Sent"

Email (via gog CLI)

gog gmail send \
  --to "{email}" \
  --subject "{subject}" \
  --body "{personalized_body}" \
  --account patrick@candlefish.ai

For follow-ups (reply to thread):

gog gmail reply \
  --thread-id "{thread_id}" \
  --body "{follow_up_body}"

Sequence Status Tracking

Track in DuckDB with these status fields:

FieldValuesNotes
----------------------
Outreach StatusQueued, Sent, Replied, Converted, Bounced, Opted OutMain status
Sequence Step1, 2, 3, 4Current step in sequence
Last OutreachdateWhen last message was sent
Next OutreachdateWhen next step is due
Outreach ChannelLinkedIn, Email, BothActive channel
Reply ReceivedbooleanTrue if they responded
Thread IDtextGmail thread ID for email chains
-- Find leads due for next sequence step
SELECT "Name", "Email", "Outreach Status", "Sequence Step", "Next Outreach"
FROM v_leads
WHERE "Outreach Status" = 'Sent'
  AND "Reply Received" = false
  AND "Next Outreach" <= CURRENT_DATE
ORDER BY "Next Outreach";

Cron Integration

Set up automated sequence execution:

Schedule: Every 2 hours during business hours (9am-5pm Mon-Fri)
Action:
1. Query leads due for next step
2. For each due lead:
   a. Generate personalized message for their current step
   b. Send via appropriate channel
   c. Update status + advance step
   d. Set next outreach date
3. Report: "Sent 12 messages (8 LinkedIn, 4 email). 3 replies received."

Cron Job Setup (for OpenClaw)

{
  "name": "Outreach Sequencer",
  "schedule": { "kind": "cron", "expr": "0 9,11,13,15 * * 1-5", "tz": "America/Denver" },
  "sessionTarget": "isolated",
  "payload": {
    "kind": "agentTurn",
    "message": "Run outreach sequence check. Query DuckDB for leads with Next Outreach <= today. Send personalized messages for their current sequence step. Update statuses. Report results.",
    "timeoutSeconds": 300
  }
}

Safety & Compliance

  • Daily send limits: Max 50 LinkedIn connection requests/day, 100 messages/day
  • Email limits: Max 100 cold emails/day (avoid spam flags)
  • Opt-out handling: If someone replies "not interested" / "unsubscribe", immediately set status to "Opted Out" and never contact again
  • Bounce handling: If email bounces, mark as "Bounced" and try alternate email patterns
  • CAN-SPAM compliance: Include sender identity, physical address option, and opt-out mechanism in emails
  • LinkedIn ToS: Keep connection notes professional, don't spam InMails
  • Cool-down: If a lead hasn't replied after full sequence, wait 90 days before any re-engagement

Analytics

After each sequence run, track:

Active Sequences: 85 leads
├── Step 1 (Initial): 20 leads
├── Step 2 (Follow-up): 35 leads
├── Step 3 (Value-add): 18 leads
├── Step 4 (Break-up): 12 leads
│
Outcomes:
├── Replied: 23 (27% reply rate)
├── Converted: 8 (9.4% conversion)
├── Opted Out: 3 (3.5%)
├── Bounced: 2 (2.4%)
└── No Response (completed): 15 (17.6%)

版本历史

共 1 个版本

  • v1.0.0 当前
    2026-03-29 07:11 安全 安全

安全检测

腾讯云安全 (Keen)

安全,无风险
查看报告

腾讯云安全 (Sanbu)

安全,无风险
查看报告

🔗 相关推荐

communication-collaboration

Himalaya

lamelas
{"answer":"通过IMAP/SMTP管理邮件的CLI。可在终端使用 `himalaya` 收发、回复、转发、搜索及整理邮件。支持多账户与MML(MIME元语言)编写邮件。"}
★ 68 📥 45,592
communication-collaboration

imap-smtp-email

gzlicanyi
使用IMAP/SMTP读取和发送邮件;检查新/未读邮件、获取内容、搜索邮箱、标记已读/未读、发送带附件的邮件。支持...
★ 114 📥 52,429
data-analysis

Ironclaw Pipeline Analytics

aspenas
根据CRM数据生成交互式分析仪表板。当用户要求“展示管道统计”、“创建报告”、“分析潜在客户”或“显示转化率”时使用。
★ 0 📥 1,123