Agents can sign plugins, rotate credentials without losing identity, and publicly attest to behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage LinkedIn outreach leads from Google Sheets — search by name, read live conversation threads, update status, and send contextual follow-up messages. Use after linkedin-dm to move leads through the pipeline (Sent → Replied → Call Scheduled → Demo Done → Closed).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Manage ongoing LinkedIn conversations from a central Google Sheet CRM. Read threads, draft context-aware replies, send messages, and keep the sheet updated — all from one skill.
Before doing anything:
linkedin-dm setup). Default: 1eEZDGcr1dIbSC782mNkxvD7pVrF8rOFySWCVZ1RXkhM, tab: Sheet1 (or Outreach if renamed).gog auth list. If no tokens: see gog auth setup below./feed/ first.The CRM sheet uses these columns (A–P):
| Col | Field | Notes |
|---|---|---|
| A | Date Sent | ISO date |
| B | Person Name | Full name |
| C | Role / Title | |
| D | Company | |
| E | LinkedIn URL | Profile URL |
| F | Relationship Hook | Hook used in opener |
| G | Opener Sent | Message 1 text |
| H | Pitch Sent | Message 2 text |
| I | Campaign | Batch label |
| J | Status | Current pipeline stage |
| K | Notes | Context and history |
| L | Last Updated | ISO timestamp |
| M | Last Reply Date | When they last replied |
| N | Last Reply (preview) | First 200 chars of their last reply |
| O | Conversation Log | Full thread (see format below) |
| P | Next Action | What to do next (agent or human) |
Status values:
Sent → Replied → Call Scheduled → Demo Done → Follow Up Sent → No Response → Closed Won → Closed Lost
Conversation Log format (column O):
[2026-02-13 17:05 SENT] Hey Rishabh, we both had stints at CRED...
[2026-02-13 17:05 SENT] I'm building an AI calling agent...
[2026-02-15 09:30 RECEIVED] Hey! Sounds interesting, tell me more.
[2026-02-15 09:45 SENT] Happy to show you a live demo — are you free Thursday?
If columns M–P don't exist yet, add them first:
gog sheets update <SHEET_ID> "Sheet1!M1:P1" \
--values-json '[["Last Reply Date","Last Reply (preview)","Conversation Log","Next Action"]]' \
--input USER_ENTERED
User says: "Mark Rishabh as Replied" or "Rishabh got back to me, he's interested"
Find the row — Search the sheet for the person:
gog sheets get <SHEET_ID> "Sheet1!A:P" --json
Match by name (col B) or LinkedIn URL (col E). Get the row number.
Update status (col J) and last updated (col L):
gog sheets update <SHEET_ID> "Sheet1!J<ROW>:L<ROW>" \
--values-json '[["Replied","","<ISO_TIMESTAMP>"]]' \
--input USER_ENTERED
If the user provides reply content, also update:
Confirm update to user.
User says: "Follow up with Rishabh" or "Send a follow-up to everyone who replied"
gog sheets get <SHEET_ID> "Sheet1!A:P" --json
Find their row. Load: Name, Company, Role, LinkedIn URL, Opener Sent, Pitch Sent, Status, Notes, Conversation Log, Next Action.
Always go to feed first (anti-detection):
https://www.linkedin.com/feed/
Wait 2–4 seconds. Then navigate to their profile URL (col E).
Click the Message button on their profile. Wait for the conversation bubble to load.
Scrape the full thread with JavaScript:
const events = Array.from(document.querySelectorAll('.msg-s-message-list__event'));
const messages = [];
events.forEach(el => {
const groups = el.querySelectorAll('.msg-s-event-listitem');
groups.forEach(g => {
const nameEl = g.closest('.msg-s-message-group')?.querySelector('.msg-s-message-group__profile-link');
const bodyEl = g.querySelector('.msg-s-event-listitem__body');
const timeEl = g.closest('.msg-s-message-group')?.querySelector('.msg-s-message-group__timestamp');
if (bodyEl?.textContent?.trim()) {
messages.push({
sender: nameEl?.textContent?.trim() || 'unknown',
time: timeEl?.textContent?.trim() || '',
text: bodyEl.textContent.trim()
});
}
});
});
return JSON.stringify(messages);
If the thread is empty or not loading, scroll up in the conversation bubble to load older messages.
With the full thread loaded + their profile data, determine:
Write a response that:
Show the draft to the user and ask for approval before sending:
Draft reply to [Name]: [message]
Send this? (y / edit / skip)
Same JS evaluate method as linkedin-dm:
const active = document.querySelector('.msg-overlay-conversation-bubble--is-active .msg-form__contenteditable');
if (active) { active.focus(); document.execCommand('insertText', false, '<message>'); }
Then find and click Send.
After sending:
gog sheets update <SHEET_ID> "Sheet1!J<ROW>:P<ROW>" \
--values-json '[["<new_status>","<last_reply_date>","<last_reply_preview>","<updated_conversation_log>","<next_action>","<ISO_TIMESTAMP>"]]' \
--input USER_ENTERED
User says: "Who needs a follow-up?" or "Check my outreach"
Sent older than 3 days → candidate for "No Response" or gentle follow-upReplied → needs a responseFollow Up Sent older than 5 days → consider "No Response"Call Scheduled → check if call happened, update statusName Status Last Updated Suggested Action
Rishabh Nayan Replied 2026-02-14 Reply to their message
Shorya Saini Sent 2026-02-10 Follow-up nudge (4 days)
Shantam Mohata Sent 2026-02-13 Too soon (today)
Use these as a guide — always adapt to the actual conversation:
| They said | Intent | Your move |
|---|---|---|
| "Sounds interesting, tell me more" | Curious | Short explanation + offer a specific demo slot |
| "How does it work?" | Exploring | 2-line description + invite to a 15-min call |
| "We already use [X]" | Objection | Acknowledge, explain differentiation, offer demo |
| "Send me more details" | Soft interest | Share a Loom/deck/link + follow up in 2 days |
| "Not relevant right now" | Soft no | Respect it, leave door open: "No worries, I'll ping you in a few months" |
| "Who else is using it?" | Trust-building | Share a relevant use case, offer intro to a user |
| [No reply in 4 days] | Silence | Light nudge: "Hey [Name], just checking — any thoughts?" |
| [No reply in 8 days] | Cold | One final message, then mark No Response |
Same rules as linkedin-dm:
/feed/ before navigating to a profileIf gog auth list returns empty, the user needs to set up Google OAuth credentials:
client_secret_<id>.jsongog auth credentials set /path/to/client_secret.json
gog auth add your@gmail.com --services sheets
gog auth listFallback (no gog): All sheet reads/writes can be done manually via browser — open the sheet in the openclaw browser and update cells directly. Less automated but functional.
linkedin_followup_log.json and sync to sheet next session아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Agents can sign plugins, rotate credentials without losing identity, and publicly attest to behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query historical crypto market data from 0xArchive across Hyperliquid, Lighter.xyz, and HIP-3. Covers orderbooks, trades, candles, funding rates, open interest, liquidations, and data quality. Use when the user asks about crypto market data, orderbooks, trades, funding rates, or historical prices on Hyperliquid, Lighter.xyz, or HIP-3.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Calculate ROI for AI-as-a-Service (managed AI agents). Estimates cost savings, efficiency gains, and payback period for deploying AI agents across business operations. Use when evaluating whether managed AI agents make financial sense for a company.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, build, deploy, and operate production AI agent systems — single agents, multi-agent teams, and autonomous swarms. Complete methodology from agent architecture through orchestration, memory systems, safety guardrails, and operational excellence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, build, test, document, and secure production-grade APIs. Covers the full lifecycle from schema design through deployment, monitoring, and versioning. Use when designing new APIs, reviewing existing ones, generating OpenAPI specs, building test suites, or debugging production issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn your AI agent into a business automation architect. Design, document, implement, and monitor automated workflows across sales, ops, finance, HR, and support — no n8n or Zapier required.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.