{"id":"8ccb1a08-53a5-45f3-adb4-07754e65a7fb","entityType":"agent","slug":"clawhub-hith3sh-lemlist-outreach","name":"Lemlist","canonicalUrl":"https://www.xpersona.co/agent/clawhub-hith3sh-lemlist-outreach","canonicalPath":"/agent/clawhub-hith3sh-lemlist-outreach","generatedAt":"2026-10-10T07:01:33.295Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T12:15:40.164Z","emptyReason":null},"description":"Run personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, an... Skill: Lemlist Owner: hith3sh Summary: Run personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, an... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:12:31.800Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic sourc","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.7K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:lemlist-outreach","sourceUrl":"https://clawhub.ai/hith3sh/lemlist-outreach","homepage":"https://clawhub.ai/hith3sh/skills/lemlist-outreach","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/hith3sh/lemlist-outreach","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/hith3sh/skills/lemlist-outreach","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":69,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Run personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, an..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:15:40.164Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:15:40.164Z","emptyReason":null},"stars":null,"forks":null,"downloads":2675,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"2.7K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:15:40.164Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T12:15:40.164Z","lastCrawledAt":"2026-10-09T12:15:40.164Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T12:15:40.164Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-06-09T07:12:31.800Z","changelog":"Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.","fileCount":3,"zipByteSize":6655},{"version":"1.0.4","createdAt":"2026-06-09T04:59:17.550Z","changelog":"- Removed the file: skill-card.md - No changes were made to core functionality or user-facing features.","fileCount":3,"zipByteSize":6725},{"version":"1.0.1","createdAt":"2026-06-08T16:39:03.912Z","changelog":"- Added a Lemlist brand logo to the top of the documentation. - Updated SKILL.md formatting to improve clarity and visual presentation. - Removed the file skill-card.md from the project.","fileCount":3,"zipByteSize":6740},{"version":"0.1.2","createdAt":"2026-06-07T13:32:33.288Z","changelog":"Full rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.","fileCount":3,"zipByteSize":6655},{"version":"0.1.1","createdAt":"2026-05-13T12:31:12.101Z","changelog":"Refresh public title to remove internal ClawLink branding from the skill name","fileCount":3,"zipByteSize":3448},{"version":"0.1.0","createdAt":"2026-05-05T17:30:58.970Z","changelog":"Initial publish","fileCount":2,"zipByteSize":2279}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:lemlist-outreach","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-lemlist-outreach/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-lemlist-outreach/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-lemlist-outreach/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-lemlist-outreach/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-lemlist-outreach/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-lemlist-outreach/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T07:01:33.293Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-lemlist-outreach/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-lemlist-outreach/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-lemlist-outreach/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-lemlist-outreach/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T12:15:40.164Z","emptyReason":null},"readme":"Skill: Lemlist\n\nOwner: hith3sh\n\nSummary: Run personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, an...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-06-09T07:12:31.800Z | user\n\nAdd UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.\n\nv1.0.4 | 2026-06-09T04:59:17.550Z | auto\n\n- Removed the file: skill-card.md\n- No changes were made to core functionality or user-facing features.\n\nv1.0.1 | 2026-06-08T16:39:03.912Z | auto\n\n- Added a Lemlist brand logo to the top of the documentation.\n- Updated SKILL.md formatting to improve clarity and visual presentation.\n- Removed the file skill-card.md from the project.\n\nv0.1.2 | 2026-06-07T13:32:33.288Z | user\n\nFull rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.\n\nv0.1.1 | 2026-05-13T12:31:12.101Z | user\n\nRefresh public title to remove internal ClawLink branding from the skill name\n\nv0.1.0 | 2026-05-05T17:30:58.970Z | user\n\nInitial publish\n\nArchive index:\n\nArchive v1.0.5: 3 files, 6655 bytes\n\nFiles: skill-card.md (2194b), SKILL.md (17626b), _meta.json (135b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: lemlist-outreach\ndescription: Run personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, and automate outreach workflows with labeling and scheduling.\n---\n\n# Lemlist\n\n\n\nRun personalized email outreach campaigns via Lemlist. Manage campaigns and sequences, track lead engagement, search people and company databases, handle tasks, and automate outreach with labels and schedules.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=lemlist-outreach) for hosted connection flows and credentials so you do not need to configure Lemlist API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Lemlist |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Lemlist API │\n│ (User Chat) │ │ (OAuth) │ │ (v1) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Lemlist│ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Lemlist │\n │ File │ │ Auth │ │ Campaigns│\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Lemlist again.\"\n\n## Quick Start\n\n```bash\n# List campaigns\nclawlink_call_tool --tool \"lemlist_get_list_campaigns\" --params '{}'\n\n# Get campaign stats\nclawlink_call_tool --tool \"lemlist_get_campaign_stats\" --params '{\"campaign_id\": \"CAMPAIGN_ID\"}'\n\n# Get team info\nclawlink_call_tool --tool \"lemlist_get_team_info\" --params '{}'\n```\n\n## Authentication\n\nAll Lemlist tool calls are authenticated automatically by ClawLink using the user's connected Lemlist team.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Lemlist API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=lemlist and connect Lemlist (requires an active Lemlist team).\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `lemlist` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration lemlist\n```\n\n**Response:** Returns the live tool catalog for Lemlist.\n\n### Reconnect\n\nIf Lemlist tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=lemlist\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration lemlist`\n\n## Security & Permissions\n\n- Access is scoped to the connected Lemlist team only.\n- **All write operations require explicit user confirmation.** Before executing any campaign, lead, or sequence action, confirm the target resource and intended effect with the user.\n- Destructive actions (delete schedule, unsubscribe lead, delete unsubscribed email) are marked as high-impact and must be confirmed.\n- Campaign creation returns IDs nested under `result['data']` — store campaignId, sequenceId, scheduleId from responses.\n- Lead status changes (mark interested/not interested, pause) affect ongoing outreach — confirm before executing.\n\n## Tool Reference\n\n### Campaigns\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_list_campaigns` | List all campaigns for the team with IDs, names, statuses | Read |\n| `lemlist_get_campaign_by_id` | Get campaign details by ID | Read |\n| `lemlist_get_campaign_stats` | Get campaign performance metrics within a date range | Read |\n| `lemlist_get_campaign_export_start` | Start async CSV export of all campaign statistics | Write |\n| `lemlist_get_campaign_export_status` | Check status of campaign export job | Read |\n| `lemlist_get_campaign_sequences` | Get all sequences for a campaign with steps and conditions | Read |\n| `lemlist_get_export_campaign_leads` | Export campaign leads with state filtering (JSON or CSV) | Read |\n| `lemlist_post_create_campaign` | Create a new campaign (returns campaignId, sequenceId, scheduleId) | Write |\n| `lemlist_patch_update_campaign` | Update campaign settings (name, stop-on behaviors, flags) | Write |\n| `lemlist_post_pause_campaign` | Pause a running campaign | Write |\n\n### Leads\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_retrieve_lead_by_email` | Get lead details by email address | Read |\n| `lemlist_post_create_lead_in_campaign` | Create a lead and add to a campaign with optional enrichment | Write |\n| `lemlist_post_mark_lead_as_interested` | Mark a lead as interested in all campaigns | Write |\n| `lemlist_post_mark_lead_as_interested_in_campaign` | Mark a lead as interested in a specific campaign | Write |\n| `lemlist_post_mark_lead_as_not_interested` | Mark a lead as not interested in all campaigns | Write |\n| `lemlist_patch_mark_lead_as_not_interested_in_campaign` | Mark a lead as not interested in a specific campaign | Write |\n| `lemlist_post_pause_lead` | Pause a lead in all campaigns or a specific campaign | Write |\n| `lemlist_delete_unsubscribe_lead_from_campaign` | Unsubscribe a lead from a specific campaign | Write |\n| `lemlist_post_add_variables_to_lead` | Add custom variables to a lead | Write |\n\n### Sequences\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_patch_update_sequence_step` | Update a sequence step (subject, message, delay) | Write |\n| `lemlist_post_add_step_to_sequence` | Add a new step (email, LinkedIn, conditional) to a sequence | Write |\n\n### Schedules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_post_create_schedule` | Create a new schedule (returns scheduleId — store for campaign association) | Write |\n| `lemlist_patch_update_schedule` | Update an existing schedule's days, time window, limits | Write |\n| `lemlist_delete_delete_schedule` | Permanently delete a schedule by ID | Write |\n| `lemlist_post_associate_schedule_with_campaign` | Associate a schedule with a campaign | Write |\n\n### Tasks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_list_tasks` | List all pending tasks assigned to team members | Read |\n| `lemlist_post_create_task` | Create a manual task associated with a contact, company, or lead | Write |\n| `lemlist_update_task` | Update task assignment, scheduling, and status | Write |\n| `lemlist_post_ignore_tasks` | Mark one or more tasks as ignored | Write |\n\n### Unsubscribes & Suppression\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_retrieve_unsubscribes` | List all unsubscribed people | Read |\n| `lemlist_get_get_unsubscribe_email` | Check if a specific email is unsubscribed | Read |\n| `lemlist_get_export_unsubscribes` | Download CSV of all unsubscribed email addresses | Read |\n| `lemlist_post_add_unsubscribe_email_domain` | Add an email or domain to the unsubscribed list | Write |\n| `lemlist_delete_delete_unsubscribe_email` | Remove an email from the unsubscribed list | Write |\n\n### Labels\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_list_labels` | List all labels for inbox organization | Read |\n| `lemlist_get_label` | Get label details by ID | Read |\n| `lemlist_post_create_label` | Create a new label for inbox conversations | Write |\n\n### Companies\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_list_companies` | List all companies in CRM with pagination | Read |\n| `lemlist_list_company_notes` | Get all notes for a specific company | Read |\n| `lemlist_create_company_note` | Add a note to a company record | Write |\n| `lemlist_search_companies_database` | Search companies database with filters and keywords | Read |\n| `lemlist_get_companies_schema` | Get schema definition for company records | Read |\n\n### People Database\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_search_people_database` | Search people database with filters, keywords, pagination | Read |\n| `lemlist_get_people_schema` | Get schema definition for people records | Read |\n| `lemlist_get_database_filters` | Discover available search filters for people and companies | Read |\n\n### Contact Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_contact_messages` | Get all messages exchanged with a specific contact | Write |\n\n### Activity & Analytics\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_retrieve_activities` | Get recent campaign activities filtered by campaign, type, limit | Read |\n\n### Team & Users\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_team_info` | Get team settings, members, webhooks, and enabled features | Read |\n| `lemlist_get_list_team_senders` | Get all team members and their associated campaigns | Read |\n| `lemlist_get_user` | Get user details by ID including LinkedIn settings and mailboxes | Read |\n| `lemlist_get_user_info` | Get authenticated user information | Read |\n| `lemlist_get_list_watchlist_signals` | Get paginated watchlist signals with filtering | Read |\n\n### Credits\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_team_credits` | Get remaining credits in the team | Read |\n\n### Webhooks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_all_webhooks` | List all configured webhooks for the team | Read |\n\n## Code Examples\n\n### List campaigns\n\n```bash\nclawlink_call_tool --tool \"lemlist_get_list_campaigns\" \\\n --params '{}'\n```\n\n### Get campaign stats\n\n```bash\nclawlink_call_tool --tool \"lemlist_get_campaign_stats\" \\\n --params '{\"campaign_id\": \"CAMPAIGN_ID\", \"start_date\": \"2024-01-01\", \"end_date\": \"2024-01-31\"}'\n```\n\n### Create a lead in campaign\n\n```bash\nclawlink_call_tool --tool \"lemlist_post_create_lead_in_campaign\" \\\n --params '{\"campaign_id\": \"CAMPAIGN_ID\", \"email\": \"lead@example.com\", \"first_name\": \"John\"}'\n```\n\n### Mark lead as interested\n\n```bash\nclawlink_call_tool --tool \"lemlist_post_mark_lead_as_interested\" \\\n --params '{\"lead_id\": \"LEAD_ID\"}'\n```\n\n### Create a task\n\n```bash\nclawlink_call_tool --tool \"lemlist_post_create_task\" \\\n --params '{\"contact_id\": \"CONTACT_ID\", \"title\": \"Follow up call\", \"due_date\": \"2024-12-15\"}'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Lemlist is connected.\n2. Call `clawlink_list_tools --integration lemlist` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `lemlist`.\n5. If no Lemlist tools appear, direct the user to https://claw-link.dev/dashboard?add=lemlist.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List campaigns → Get stats → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Preview lead create → User approves → Execute │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. 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.\n\n## Notes\n\n- Campaign creation returns IDs nested under `result['data']` (e.g., `result['data']['campaignId']`). Store these for subsequent operations.\n- Schedules return `scheduleId` — store it for association with campaigns or sequences.\n- Avoid creating unused schedules; delete them when no longer needed.\n- Lead status changes affect all campaigns or specific campaigns depending on the tool used.\n- Company notes are for tracking annotations and activities on company records.\n- People and companies database search supports free-text and structured filtering.\n- Verify returned `teamId` matches the intended workspace before passing to campaign-creation.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration lemlist`. |\n| Missing connection | Lemlist is not connected. Direct the user to https://claw-link.dev/dashboard?add=lemlist. |\n| Permission error | The authenticated user lacks permission for this operation. |\n| Campaign not found | The campaign ID does not exist. Verify with `lemlist_get_list_campaigns`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n## Resources\n\n- [Lemlist API Documentation](https://docs.lemlist.com/)\n- [Lemlist Campaign Management](https://help.lemlist.com/en/)\n- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=lemlist-outreach\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Instantly Campaigns](https://clawhub.ai/hith3sh/instantly-campaigns) — For Instantly cold email campaigns\n- [Kit Email Marketing](https://clawhub.ai/hith3sh/kit-email-marketing) — For Kit email broadcasts and sequences\n- [LinkedIn Social](https://clawhub.ai/hith3sh/linkedin-social) — For LinkedIn outreach and connection management\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=lemlist-outreach)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"lemlist-outreach\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1780989151800\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nRun personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, and automate outreach workflows with labeling and scheduling.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and sales teams use this skill to manage Lemlist outreach workflows, including campaigns, leads, sequences, schedules, tasks, suppression lists, analytics, and team information through a connected Lemlist account.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill depends on an unpinned external plugin for OAuth-backed Lemlist access.\n\nMitigation: Review the ClawLink plugin source, publisher, version, and update policy before installing or enabling it.\n\nRisk: Lemlist write operations can affect campaigns, lead statuses, schedules, unsubscribe or suppression settings, and exports.\n\nMitigation: Connect an account with the minimum needed permissions and verify previews before any write operation.\n\n## Reference(s):\n\n- [Lemlist API Documentation](https://docs.lemlist.com/)\n- [Lemlist Campaign Management](https://help.lemlist.com/en/)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/lemlist-outreach)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with inline shell commands and tool-call guidance]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May propose or execute Lemlist read and write operations through ClawLink after connection checks and user confirmation for writes.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 3 files, 6725 bytes\n\nFiles: skill-card.md (2585b), SKILL.md (17419b), _meta.json (135b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: lemlist-outreach\ndescription: Run personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, and automate outreach workflows with labeling and scheduling.\n---\n\n# Lemlist\n\n\n\nRun personalized email outreach campaigns via Lemlist. Manage campaigns and sequences, track lead engagement, search people and company databases, handle tasks, and automate outreach with labels and schedules.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Lemlist API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Lemlist |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Lemlist API │\n│ (User Chat) │ │ (OAuth) │ │ (v1) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Lemlist│ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Lemlist │\n │ File │ │ Auth │ │ Campaigns│\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Lemlist again.\"\n\n## Quick Start\n\n```bash\n# List campaigns\nclawlink_call_tool --tool \"lemlist_get_list_campaigns\" --params '{}'\n\n# Get campaign stats\nclawlink_call_tool --tool \"lemlist_get_campaign_stats\" --params '{\"campaign_id\": \"CAMPAIGN_ID\"}'\n\n# Get team info\nclawlink_call_tool --tool \"lemlist_get_team_info\" --params '{}'\n```\n\n## Authentication\n\nAll Lemlist tool calls are authenticated automatically by ClawLink using the user's connected Lemlist team.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Lemlist API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=lemlist and connect Lemlist (requires an active Lemlist team).\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `lemlist` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration lemlist\n```\n\n**Response:** Returns the live tool catalog for Lemlist.\n\n### Reconnect\n\nIf Lemlist tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=lemlist\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration lemlist`\n\n## Security & Permissions\n\n- Access is scoped to the connected Lemlist team only.\n- **All write operations require explicit user confirmation.** Before executing any campaign, lead, or sequence action, confirm the target resource and intended effect with the user.\n- Destructive actions (delete schedule, unsubscribe lead, delete unsubscribed email) are marked as high-impact and must be confirmed.\n- Campaign creation returns IDs nested under `result['data']` — store campaignId, sequenceId, scheduleId from responses.\n- Lead status changes (mark interested/not interested, pause) affect ongoing outreach — confirm before executing.\n\n## Tool Reference\n\n### Campaigns\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_list_campaigns` | List all campaigns for the team with IDs, names, statuses | Read |\n| `lemlist_get_campaign_by_id` | Get campaign details by ID | Read |\n| `lemlist_get_campaign_stats` | Get campaign performance metrics within a date range | Read |\n| `lemlist_get_campaign_export_start` | Start async CSV export of all campaign statistics | Write |\n| `lemlist_get_campaign_export_status` | Check status of campaign export job | Read |\n| `lemlist_get_campaign_sequences` | Get all sequences for a campaign with steps and conditions | Read |\n| `lemlist_get_export_campaign_leads` | Export campaign leads with state filtering (JSON or CSV) | Read |\n| `lemlist_post_create_campaign` | Create a new campaign (returns campaignId, sequenceId, scheduleId) | Write |\n| `lemlist_patch_update_campaign` | Update campaign settings (name, stop-on behaviors, flags) | Write |\n| `lemlist_post_pause_campaign` | Pause a running campaign | Write |\n\n### Leads\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_retrieve_lead_by_email` | Get lead details by email address | Read |\n| `lemlist_post_create_lead_in_campaign` | Create a lead and add to a campaign with optional enrichment | Write |\n| `lemlist_post_mark_lead_as_interested` | Mark a lead as interested in all campaigns | Write |\n| `lemlist_post_mark_lead_as_interested_in_campaign` | Mark a lead as interested in a specific campaign | Write |\n| `lemlist_post_mark_lead_as_not_interested` | Mark a lead as not interested in all campaigns | Write |\n| `lemlist_patch_mark_lead_as_not_interested_in_campaign` | Mark a lead as not interested in a specific campaign | Write |\n| `lemlist_post_pause_lead` | Pause a lead in all campaigns or a specific campaign | Write |\n| `lemlist_delete_unsubscribe_lead_from_campaign` | Unsubscribe a lead from a specific campaign | Write |\n| `lemlist_post_add_variables_to_lead` | Add custom variables to a lead | Write |\n\n### Sequences\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_patch_update_sequence_step` | Update a sequence step (subject, message, delay) | Write |\n| `lemlist_post_add_step_to_sequence` | Add a new step (email, LinkedIn, conditional) to a sequence | Write |\n\n### Schedules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_post_create_schedule` | Create a new schedule (returns scheduleId — store for campaign association) | Write |\n| `lemlist_patch_update_schedule` | Update an existing schedule's days, time window, limits | Write |\n| `lemlist_delete_delete_schedule` | Permanently delete a schedule by ID | Write |\n| `lemlist_post_associate_schedule_with_campaign` | Associate a schedule with a campaign | Write |\n\n### Tasks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_list_tasks` | List all pending tasks assigned to team members | Read |\n| `lemlist_post_create_task` | Create a manual task associated with a contact, company, or lead | Write |\n| `lemlist_update_task` | Update task assignment, scheduling, and status | Write |\n| `lemlist_post_ignore_tasks` | Mark one or more tasks as ignored | Write |\n\n### Unsubscribes & Suppression\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_retrieve_unsubscribes` | List all unsubscribed people | Read |\n| `lemlist_get_get_unsubscribe_email` | Check if a specific email is unsubscribed | Read |\n| `lemlist_get_export_unsubscribes` | Download CSV of all unsubscribed email addresses | Read |\n| `lemlist_post_add_unsubscribe_email_domain` | Add an email or domain to the unsubscribed list | Write |\n| `lemlist_delete_delete_unsubscribe_email` | Remove an email from the unsubscribed list | Write |\n\n### Labels\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_list_labels` | List all labels for inbox organization | Read |\n| `lemlist_get_label` | Get label details by ID | Read |\n| `lemlist_post_create_label` | Create a new label for inbox conversations | Write |\n\n### Companies\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_list_companies` | List all companies in CRM with pagination | Read |\n| `lemlist_list_company_notes` | Get all notes for a specific company | Read |\n| `lemlist_create_company_note` | Add a note to a company record | Write |\n| `lemlist_search_companies_database` | Search companies database with filters and keywords | Read |\n| `lemlist_get_companies_schema` | Get schema definition for company records | Read |\n\n### People Database\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_search_people_database` | Search people database with filters, keywords, pagination | Read |\n| `lemlist_get_people_schema` | Get schema definition for people records | Read |\n| `lemlist_get_database_filters` | Discover available search filters for people and companies | Read |\n\n### Contact Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_contact_messages` | Get all messages exchanged with a specific contact | Write |\n\n### Activity & Analytics\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_retrieve_activities` | Get recent campaign activities filtered by campaign, type, limit | Read |\n\n### Team & Users\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_team_info` | Get team settings, members, webhooks, and enabled features | Read |\n| `lemlist_get_list_team_senders` | Get all team members and their associated campaigns | Read |\n| `lemlist_get_user` | Get user details by ID including LinkedIn settings and mailboxes | Read |\n| `lemlist_get_user_info` | Get authenticated user information | Read |\n| `lemlist_get_list_watchlist_signals` | Get paginated watchlist signals with filtering | Read |\n\n### Credits\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_team_credits` | Get remaining credits in the team | Read |\n\n### Webhooks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_all_webhooks` | List all configured webhooks for the team | Read |\n\n## Code Examples\n\n### List campaigns\n\n```bash\nclawlink_call_tool --tool \"lemlist_get_list_campaigns\" \\\n --params '{}'\n```\n\n### Get campaign stats\n\n```bash\nclawlink_call_tool --tool \"lemlist_get_campaign_stats\" \\\n --params '{\"campaign_id\": \"CAMPAIGN_ID\", \"start_date\": \"2024-01-01\", \"end_date\": \"2024-01-31\"}'\n```\n\n### Create a lead in campaign\n\n```bash\nclawlink_call_tool --tool \"lemlist_post_create_lead_in_campaign\" \\\n --params '{\"campaign_id\": \"CAMPAIGN_ID\", \"email\": \"lead@example.com\", \"first_name\": \"John\"}'\n```\n\n### Mark lead as interested\n\n```bash\nclawlink_call_tool --tool \"lemlist_post_mark_lead_as_interested\" \\\n --params '{\"lead_id\": \"LEAD_ID\"}'\n```\n\n### Create a task\n\n```bash\nclawlink_call_tool --tool \"lemlist_post_create_task\" \\\n --params '{\"contact_id\": \"CONTACT_ID\", \"title\": \"Follow up call\", \"due_date\": \"2024-12-15\"}'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Lemlist is connected.\n2. Call `clawlink_list_tools --integration lemlist` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `lemlist`.\n5. If no Lemlist tools appear, direct the user to https://claw-link.dev/dashboard?add=lemlist.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List campaigns → Get stats → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Preview lead create → User approves → Execute │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. 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.\n\n## Notes\n\n- Campaign creation returns IDs nested under `result['data']` (e.g., `result['data']['campaignId']`). Store these for subsequent operations.\n- Schedules return `scheduleId` — store it for association with campaigns or sequences.\n- Avoid creating unused schedules; delete them when no longer needed.\n- Lead status changes affect all campaigns or specific campaigns depending on the tool used.\n- Company notes are for tracking annotations and activities on company records.\n- People and companies database search supports free-text and structured filtering.\n- Verify returned `teamId` matches the intended workspace before passing to campaign-creation.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration lemlist`. |\n| Missing connection | Lemlist is not connected. Direct the user to https://claw-link.dev/dashboard?add=lemlist. |\n| Permission error | The authenticated user lacks permission for this operation. |\n| Campaign not found | The campaign ID does not exist. Verify with `lemlist_get_list_campaigns`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n## Resources\n\n- [Lemlist API Documentation](https://docs.lemlist.com/)\n- [Lemlist Campaign Management](https://help.lemlist.com/en/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Instantly Campaigns](https://clawhub.ai/hith3sh/instantly-campaigns) — For Instantly cold email campaigns\n- [Kit Email Marketing](https://clawhub.ai/hith3sh/kit-email-marketing) — For Kit email broadcasts and sequences\n- [LinkedIn Social](https://clawhub.ai/hith3sh/linkedin-social) — For LinkedIn outreach and connection management\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"lemlist-outreach\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1780981157550\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:
\nRun personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, and automate outreach workflows with labeling and scheduling.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal sales, growth, and operations teams use this skill to manage Lemlist outreach campaigns, leads, sequences, schedules, suppression records, tasks, and performance reporting through a connected Lemlist team.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The connected Lemlist team can be modified through approved campaign, lead, schedule, task, label, and suppression actions.
\nMitigation: Review ClawLink previews carefully and confirm the target resource and intended effect before any write operation.
\nRisk: Destructive or high-impact actions can affect active outreach, including unsubscribes, schedule deletion, lead status changes, and campaign changes.
\nMitigation: Use read, list, get, and preview steps before execution, and require explicit confirmation for destructive or high-impact operations.
\nRisk: The skill requires sensitive credentials through a connected Lemlist account.
\nMitigation: Use the hosted ClawLink connection flow and verify the active Lemlist integration before running tool calls.
\n\n\n## Reference(s):
\n- [ClawHub Lemlist Release](https://clawhub.ai/hith3sh/lemlist-outreach)
\n- [Lemlist API Documentation](https://docs.lemlist.com/)
\n- [Lemlist Help Center](https://help.lemlist.com/en/)
\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, API calls, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires an active ClawLink Lemlist connection and explicit user confirmation before write or destructive operations.]
\n\n## Skill Version(s):
\n1.0.4 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 3 files, 6740 bytes\n\nFiles: skill-card.md (2681b), SKILL.md (17419b), _meta.json (135b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: lemlist-outreach\ndescription: Run personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, and automate outreach workflows with labeling and scheduling.\n---\n\n# Lemlist\n\n\n\nRun personalized email outreach campaigns via Lemlist. Manage campaigns and sequences, track lead engagement, search people and company databases, handle tasks, and automate outreach with labels and schedules.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Lemlist API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Lemlist |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Lemlist API │\n│ (User Chat) │ │ (OAuth) │ │ (v1) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Lemlist│ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Lemlist │\n │ File │ │ Auth │ │ Campaigns│\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Lemlist again.\"\n\n## Quick Start\n\n```bash\n# List campaigns\nclawlink_call_tool --tool \"lemlist_get_list_campaigns\" --params '{}'\n\n# Get campaign stats\nclawlink_call_tool --tool \"lemlist_get_campaign_stats\" --params '{\"campaign_id\": \"CAMPAIGN_ID\"}'\n\n# Get team info\nclawlink_call_tool --tool \"lemlist_get_team_info\" --params '{}'\n```\n\n## Authentication\n\nAll Lemlist tool calls are authenticated automatically by ClawLink using the user's connected Lemlist team.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Lemlist API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=lemlist and connect Lemlist (requires an active Lemlist team).\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `lemlist` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration lemlist\n```\n\n**Response:** Returns the live tool catalog for Lemlist.\n\n### Reconnect\n\nIf Lemlist tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=lemlist\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration lemlist`\n\n## Security & Permissions\n\n- Access is scoped to the connected Lemlist team only.\n- **All write operations require explicit user confirmation.** Before executing any campaign, lead, or sequence action, confirm the target resource and intended effect with the user.\n- Destructive actions (delete schedule, unsubscribe lead, delete unsubscribed email) are marked as high-impact and must be confirmed.\n- Campaign creation returns IDs nested under `result['data']` — store campaignId, sequenceId, scheduleId from responses.\n- Lead status changes (mark interested/not interested, pause) affect ongoing outreach — confirm before executing.\n\n## Tool Reference\n\n### Campaigns\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_list_campaigns` | List all campaigns for the team with IDs, names, statuses | Read |\n| `lemlist_get_campaign_by_id` | Get campaign details by ID | Read |\n| `lemlist_get_campaign_stats` | Get campaign performance metrics within a date range | Read |\n| `lemlist_get_campaign_export_start` | Start async CSV export of all campaign statistics | Write |\n| `lemlist_get_campaign_export_status` | Check status of campaign export job | Read |\n| `lemlist_get_campaign_sequences` | Get all sequences for a campaign with steps and conditions | Read |\n| `lemlist_get_export_campaign_leads` | Export campaign leads with state filtering (JSON or CSV) | Read |\n| `lemlist_post_create_campaign` | Create a new campaign (returns campaignId, sequenceId, scheduleId) | Write |\n| `lemlist_patch_update_campaign` | Update campaign settings (name, stop-on behaviors, flags) | Write |\n| `lemlist_post_pause_campaign` | Pause a running campaign | Write |\n\n### Leads\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_retrieve_lead_by_email` | Get lead details by email address | Read |\n| `lemlist_post_create_lead_in_campaign` | Create a lead and add to a campaign with optional enrichment | Write |\n| `lemlist_post_mark_lead_as_interested` | Mark a lead as interested in all campaigns | Write |\n| `lemlist_post_mark_lead_as_interested_in_campaign` | Mark a lead as interested in a specific campaign | Write |\n| `lemlist_post_mark_lead_as_not_interested` | Mark a lead as not interested in all campaigns | Write |\n| `lemlist_patch_mark_lead_as_not_interested_in_campaign` | Mark a lead as not interested in a specific campaign | Write |\n| `lemlist_post_pause_lead` | Pause a lead in all campaigns or a specific campaign | Write |\n| `lemlist_delete_unsubscribe_lead_from_campaign` | Unsubscribe a lead from a specific campaign | Write |\n| `lemlist_post_add_variables_to_lead` | Add custom variables to a lead | Write |\n\n### Sequences\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_patch_update_sequence_step` | Update a sequence step (subject, message, delay) | Write |\n| `lemlist_post_add_step_to_sequence` | Add a new step (email, LinkedIn, conditional) to a sequence | Write |\n\n### Schedules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_post_create_schedule` | Create a new schedule (returns scheduleId — store for campaign association) | Write |\n| `lemlist_patch_update_schedule` | Update an existing schedule's days, time window, limits | Write |\n| `lemlist_delete_delete_schedule` | Permanently delete a schedule by ID | Write |\n| `lemlist_post_associate_schedule_with_campaign` | Associate a schedule with a campaign | Write |\n\n### Tasks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_list_tasks` | List all pending tasks assigned to team members | Read |\n| `lemlist_post_create_task` | Create a manual task associated with a contact, company, or lead | Write |\n| `lemlist_update_task` | Update task assignment, scheduling, and status | Write |\n| `lemlist_post_ignore_tasks` | Mark one or more tasks as ignored | Write |\n\n### Unsubscribes & Suppression\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_retrieve_unsubscribes` | List all unsubscribed people | Read |\n| `lemlist_get_get_unsubscribe_email` | Check if a specific email is unsubscribed | Read |\n| `lemlist_get_export_unsubscribes` | Download CSV of all unsubscribed email addresses | Read |\n| `lemlist_post_add_unsubscribe_email_domain` | Add an email or domain to the unsubscribed list | Write |\n| `lemlist_delete_delete_unsubscribe_email` | Remove an email from the unsubscribed list | Write |\n\n### Labels\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_list_labels` | List all labels for inbox organization | Read |\n| `lemlist_get_label` | Get label details by ID | Read |\n| `lemlist_post_create_label` | Create a new label for inbox conversations | Write |\n\n### Companies\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_list_companies` | List all companies in CRM with pagination | Read |\n| `lemlist_list_company_notes` | Get all notes for a specific company | Read |\n| `lemlist_create_company_note` | Add a note to a company record | Write |\n| `lemlist_search_companies_database` | Search companies database with filters and keywords | Read |\n| `lemlist_get_companies_schema` | Get schema definition for company records | Read |\n\n### People Database\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_search_people_database` | Search people database with filters, keywords, pagination | Read |\n| `lemlist_get_people_schema` | Get schema definition for people records | Read |\n| `lemlist_get_database_filters` | Discover available search filters for people and companies | Read |\n\n### Contact Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_contact_messages` | Get all messages exchanged with a specific contact | Write |\n\n### Activity & Analytics\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_retrieve_activities` | Get recent campaign activities filtered by campaign, type, limit | Read |\n\n### Team & Users\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_team_info` | Get team settings, members, webhooks, and enabled features | Read |\n| `lemlist_get_list_team_senders` | Get all team members and their associated campaigns | Read |\n| `lemlist_get_user` | Get user details by ID including LinkedIn settings and mailboxes | Read |\n| `lemlist_get_user_info` | Get authenticated user information | Read |\n| `lemlist_get_list_watchlist_signals` | Get paginated watchlist signals with filtering | Read |\n\n### Credits\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_team_credits` | Get remaining credits in the team | Read |\n\n### Webhooks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_all_webhooks` | List all configured webhooks for the team | Read |\n\n## Code Examples\n\n### List campaigns\n\n```bash\nclawlink_call_tool --tool \"lemlist_get_list_campaigns\" \\\n --params '{}'\n```\n\n### Get campaign stats\n\n```bash\nclawlink_call_tool --tool \"lemlist_get_campaign_stats\" \\\n --params '{\"campaign_id\": \"CAMPAIGN_ID\", \"start_date\": \"2024-01-01\", \"end_date\": \"2024-01-31\"}'\n```\n\n### Create a lead in campaign\n\n```bash\nclawlink_call_tool --tool \"lemlist_post_create_lead_in_campaign\" \\\n --params '{\"campaign_id\": \"CAMPAIGN_ID\", \"email\": \"lead@example.com\", \"first_name\": \"John\"}'\n```\n\n### Mark lead as interested\n\n```bash\nclawlink_call_tool --tool \"lemlist_post_mark_lead_as_interested\" \\\n --params '{\"lead_id\": \"LEAD_ID\"}'\n```\n\n### Create a task\n\n```bash\nclawlink_call_tool --tool \"lemlist_post_create_task\" \\\n --params '{\"contact_id\": \"CONTACT_ID\", \"title\": \"Follow up call\", \"due_date\": \"2024-12-15\"}'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Lemlist is connected.\n2. Call `clawlink_list_tools --integration lemlist` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `lemlist`.\n5. If no Lemlist tools appear, direct the user to https://claw-link.dev/dashboard?add=lemlist.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List campaigns → Get stats → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Preview lead create → User approves → Execute │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. 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.\n\n## Notes\n\n- Campaign creation returns IDs nested under `result['data']` (e.g., `result['data']['campaignId']`). Store these for subsequent operations.\n- Schedules return `scheduleId` — store it for association with campaigns or sequences.\n- Avoid creating unused schedules; delete them when no longer needed.\n- Lead status changes affect all campaigns or specific campaigns depending on the tool used.\n- Company notes are for tracking annotations and activities on company records.\n- People and companies database search supports free-text and structured filtering.\n- Verify returned `teamId` matches the intended workspace before passing to campaign-creation.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration lemlist`. |\n| Missing connection | Lemlist is not connected. Direct the user to https://claw-link.dev/dashboard?add=lemlist. |\n| Permission error | The authenticated user lacks permission for this operation. |\n| Campaign not found | The campaign ID does not exist. Verify with `lemlist_get_list_campaigns`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n## Resources\n\n- [Lemlist API Documentation](https://docs.lemlist.com/)\n- [Lemlist Campaign Management](https://help.lemlist.com/en/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Instantly Campaigns](https://clawhub.ai/hith3sh/instantly-campaigns) — For Instantly cold email campaigns\n- [Kit Email Marketing](https://clawhub.ai/hith3sh/kit-email-marketing) — For Kit email broadcasts and sequences\n- [LinkedIn Social](https://clawhub.ai/hith3sh/linkedin-social) — For LinkedIn outreach and connection management\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"lemlist-outreach\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1780936743912\n}\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nRun personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, and automate outreach workflows with labeling and scheduling.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users, sales operators, and agent developers use this skill to manage Lemlist outreach campaigns, leads, sequences, schedules, tasks, suppression lists, and engagement analytics through a connected Lemlist team.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill requires a connected Lemlist team and sensitive credentials through ClawLink.
\nMitigation: Install only when the user intends to connect ClawLink to the Lemlist team, and verify the active connection before using Lemlist tools.
\nRisk: Write actions can change campaigns, leads, sequences, schedules, tasks, labels, suppression lists, exports, and outreach state.
\nMitigation: Preview and confirm the target resource and intended effect before every write action.
\nRisk: Destructive or high-impact actions can delete schedules, change unsubscribe state, or alter lead status for live outreach.
\nMitigation: Require explicit user confirmation for destructive actions and lead status changes, and prefer list/get calls first to verify the target.
\n\n\n## Reference(s):
\n- [ClawHub Lemlist Skill Page](https://clawhub.ai/hith3sh/lemlist-outreach)
\n- [Lemlist API Documentation](https://docs.lemlist.com/)
\n- [Lemlist Help Center](https://help.lemlist.com/en/)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Outputs may include read results, previews for write actions, and user-confirmed tool-call guidance for Lemlist operations.]
\n\n## Skill Version(s):
\n1.0.1 (source: release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.1.2: 3 files, 6655 bytes\n\nFiles: skill-card.md (2454b), SKILL.md (17308b), _meta.json (135b)\n\nFile v0.1.2:SKILL.md\n\n---\nname: lemlist-outreach\ndescription: Run personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, and automate outreach workflows with labeling and scheduling.\n---\n\n# Lemlist\n\nRun personalized email outreach campaigns via Lemlist. Manage campaigns and sequences, track lead engagement, search people and company databases, handle tasks, and automate outreach with labels and schedules.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Lemlist API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Lemlist |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Lemlist API │\n│ (User Chat) │ │ (OAuth) │ │ (v1) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Lemlist│ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Lemlist │\n │ File │ │ Auth │ │ Campaigns│\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Lemlist again.\"\n\n## Quick Start\n\n```bash\n# List campaigns\nclawlink_call_tool --tool \"lemlist_get_list_campaigns\" --params '{}'\n\n# Get campaign stats\nclawlink_call_tool --tool \"lemlist_get_campaign_stats\" --params '{\"campaign_id\": \"CAMPAIGN_ID\"}'\n\n# Get team info\nclawlink_call_tool --tool \"lemlist_get_team_info\" --params '{}'\n```\n\n## Authentication\n\nAll Lemlist tool calls are authenticated automatically by ClawLink using the user's connected Lemlist team.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Lemlist API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=lemlist and connect Lemlist (requires an active Lemlist team).\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `lemlist` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration lemlist\n```\n\n**Response:** Returns the live tool catalog for Lemlist.\n\n### Reconnect\n\nIf Lemlist tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=lemlist\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration lemlist`\n\n## Security & Permissions\n\n- Access is scoped to the connected Lemlist team only.\n- **All write operations require explicit user confirmation.** Before executing any campaign, lead, or sequence action, confirm the target resource and intended effect with the user.\n- Destructive actions (delete schedule, unsubscribe lead, delete unsubscribed email) are marked as high-impact and must be confirmed.\n- Campaign creation returns IDs nested under `result['data']` — store campaignId, sequenceId, scheduleId from responses.\n- Lead status changes (mark interested/not interested, pause) affect ongoing outreach — confirm before executing.\n\n## Tool Reference\n\n### Campaigns\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_list_campaigns` | List all campaigns for the team with IDs, names, statuses | Read |\n| `lemlist_get_campaign_by_id` | Get campaign details by ID | Read |\n| `lemlist_get_campaign_stats` | Get campaign performance metrics within a date range | Read |\n| `lemlist_get_campaign_export_start` | Start async CSV export of all campaign statistics | Write |\n| `lemlist_get_campaign_export_status` | Check status of campaign export job | Read |\n| `lemlist_get_campaign_sequences` | Get all sequences for a campaign with steps and conditions | Read |\n| `lemlist_get_export_campaign_leads` | Export campaign leads with state filtering (JSON or CSV) | Read |\n| `lemlist_post_create_campaign` | Create a new campaign (returns campaignId, sequenceId, scheduleId) | Write |\n| `lemlist_patch_update_campaign` | Update campaign settings (name, stop-on behaviors, flags) | Write |\n| `lemlist_post_pause_campaign` | Pause a running campaign | Write |\n\n### Leads\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_retrieve_lead_by_email` | Get lead details by email address | Read |\n| `lemlist_post_create_lead_in_campaign` | Create a lead and add to a campaign with optional enrichment | Write |\n| `lemlist_post_mark_lead_as_interested` | Mark a lead as interested in all campaigns | Write |\n| `lemlist_post_mark_lead_as_interested_in_campaign` | Mark a lead as interested in a specific campaign | Write |\n| `lemlist_post_mark_lead_as_not_interested` | Mark a lead as not interested in all campaigns | Write |\n| `lemlist_patch_mark_lead_as_not_interested_in_campaign` | Mark a lead as not interested in a specific campaign | Write |\n| `lemlist_post_pause_lead` | Pause a lead in all campaigns or a specific campaign | Write |\n| `lemlist_delete_unsubscribe_lead_from_campaign` | Unsubscribe a lead from a specific campaign | Write |\n| `lemlist_post_add_variables_to_lead` | Add custom variables to a lead | Write |\n\n### Sequences\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_patch_update_sequence_step` | Update a sequence step (subject, message, delay) | Write |\n| `lemlist_post_add_step_to_sequence` | Add a new step (email, LinkedIn, conditional) to a sequence | Write |\n\n### Schedules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_post_create_schedule` | Create a new schedule (returns scheduleId — store for campaign association) | Write |\n| `lemlist_patch_update_schedule` | Update an existing schedule's days, time window, limits | Write |\n| `lemlist_delete_delete_schedule` | Permanently delete a schedule by ID | Write |\n| `lemlist_post_associate_schedule_with_campaign` | Associate a schedule with a campaign | Write |\n\n### Tasks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_list_tasks` | List all pending tasks assigned to team members | Read |\n| `lemlist_post_create_task` | Create a manual task associated with a contact, company, or lead | Write |\n| `lemlist_update_task` | Update task assignment, scheduling, and status | Write |\n| `lemlist_post_ignore_tasks` | Mark one or more tasks as ignored | Write |\n\n### Unsubscribes & Suppression\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_retrieve_unsubscribes` | List all unsubscribed people | Read |\n| `lemlist_get_get_unsubscribe_email` | Check if a specific email is unsubscribed | Read |\n| `lemlist_get_export_unsubscribes` | Download CSV of all unsubscribed email addresses | Read |\n| `lemlist_post_add_unsubscribe_email_domain` | Add an email or domain to the unsubscribed list | Write |\n| `lemlist_delete_delete_unsubscribe_email` | Remove an email from the unsubscribed list | Write |\n\n### Labels\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_list_labels` | List all labels for inbox organization | Read |\n| `lemlist_get_label` | Get label details by ID | Read |\n| `lemlist_post_create_label` | Create a new label for inbox conversations | Write |\n\n### Companies\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_list_companies` | List all companies in CRM with pagination | Read |\n| `lemlist_list_company_notes` | Get all notes for a specific company | Read |\n| `lemlist_create_company_note` | Add a note to a company record | Write |\n| `lemlist_search_companies_database` | Search companies database with filters and keywords | Read |\n| `lemlist_get_companies_schema` | Get schema definition for company records | Read |\n\n### People Database\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_search_people_database` | Search people database with filters, keywords, pagination | Read |\n| `lemlist_get_people_schema` | Get schema definition for people records | Read |\n| `lemlist_get_database_filters` | Discover available search filters for people and companies | Read |\n\n### Contact Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_contact_messages` | Get all messages exchanged with a specific contact | Write |\n\n### Activity & Analytics\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_retrieve_activities` | Get recent campaign activities filtered by campaign, type, limit | Read |\n\n### Team & Users\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_team_info` | Get team settings, members, webhooks, and enabled features | Read |\n| `lemlist_get_list_team_senders` | Get all team members and their associated campaigns | Read |\n| `lemlist_get_user` | Get user details by ID including LinkedIn settings and mailboxes | Read |\n| `lemlist_get_user_info` | Get authenticated user information | Read |\n| `lemlist_get_list_watchlist_signals` | Get paginated watchlist signals with filtering | Read |\n\n### Credits\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_team_credits` | Get remaining credits in the team | Read |\n\n### Webhooks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `lemlist_get_all_webhooks` | List all configured webhooks for the team | Read |\n\n## Code Examples\n\n### List campaigns\n\n```bash\nclawlink_call_tool --tool \"lemlist_get_list_campaigns\" \\\n --params '{}'\n```\n\n### Get campaign stats\n\n```bash\nclawlink_call_tool --tool \"lemlist_get_campaign_stats\" \\\n --params '{\"campaign_id\": \"CAMPAIGN_ID\", \"start_date\": \"2024-01-01\", \"end_date\": \"2024-01-31\"}'\n```\n\n### Create a lead in campaign\n\n```bash\nclawlink_call_tool --tool \"lemlist_post_create_lead_in_campaign\" \\\n --params '{\"campaign_id\": \"CAMPAIGN_ID\", \"email\": \"lead@example.com\", \"first_name\": \"John\"}'\n```\n\n### Mark lead as interested\n\n```bash\nclawlink_call_tool --tool \"lemlist_post_mark_lead_as_interested\" \\\n --params '{\"lead_id\": \"LEAD_ID\"}'\n```\n\n### Create a task\n\n```bash\nclawlink_call_tool --tool \"lemlist_post_create_task\" \\\n --params '{\"contact_id\": \"CONTACT_ID\", \"title\": \"Follow up call\", \"due_date\": \"2024-12-15\"}'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Lemlist is connected.\n2. Call `clawlink_list_tools --integration lemlist` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `lemlist`.\n5. If no Lemlist tools appear, direct the user to https://claw-link.dev/dashboard?add=lemlist.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List campaigns → Get stats → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Preview lead create → User approves → Execute │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. 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.\n\n## Notes\n\n- Campaign creation returns IDs nested under `result['data']` (e.g., `result['data']['campaignId']`). Store these for subsequent operations.\n- Schedules return `scheduleId` — store it for association with campaigns or sequences.\n- Avoid creating unused schedules; delete them when no longer needed.\n- Lead status changes affect all campaigns or specific campaigns depending on the tool used.\n- Company notes are for tracking annotations and activities on company records.\n- People and companies database search supports free-text and structured filtering.\n- Verify returned `teamId` matches the intended workspace before passing to campaign-creation.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration lemlist`. |\n| Missing connection | Lemlist is not connected. Direct the user to https://claw-link.dev/dashboard?add=lemlist. |\n| Permission error | The authenticated user lacks permission for this operation. |\n| Campaign not found | The campaign ID does not exist. Verify with `lemlist_get_list_campaigns`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n## Resources\n\n- [Lemlist API Documentation](https://docs.lemlist.com/)\n- [Lemlist Campaign Management](https://help.lemlist.com/en/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Instantly Campaigns](https://clawhub.ai/hith3sh/instantly-campaigns) — For Instantly cold email campaigns\n- [Kit Email Marketing](https://clawhub.ai/hith3sh/kit-email-marketing) — For Kit email broadcasts and sequences\n- [LinkedIn Social](https://clawhub.ai/hith3sh/linkedin-social) — For LinkedIn outreach and connection management\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v0.1.2:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"lemlist-outreach\",\n \"version\": \"0.1.2\",\n \"publishedAt\": 1780839153288\n}\n\nFile v0.1.2:skill-card.md\n\n## Description:
\nRun personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, and automate outreach workflows with labeling and scheduling.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users, sales operators, and developers use this skill to manage Lemlist outreach campaigns, leads, schedules, tasks, unsubscribe records, and engagement analytics from an agent workflow.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill requires OAuth access to a connected Lemlist team.
\nMitigation: Install only when ClawLink should access that team and verify the intended Lemlist connection before tool use.
\nRisk: Write actions can create or alter campaigns, leads, schedules, tasks, labels, and suppression records.
\nMitigation: Review previews and confirm the target resource and intended effect before approving any write operation.
\nRisk: Destructive actions can delete schedules or change unsubscribe and suppression records.
\nMitigation: Treat destructive operations as high-impact and approve them only after checking identifiers and expected consequences.
\n\n\n## Reference(s):
\n- [Lemlist API Documentation](https://docs.lemlist.com/)
\n- [Lemlist Campaign Management](https://help.lemlist.com/en/)
\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/lemlist-outreach)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown guidance with inline shell commands and JSON parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May produce ClawLink tool-call instructions for Lemlist read and write workflows.]
\n\n## Skill Version(s):
\n0.1.2 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.1.1: 3 files, 3448 bytes\n\nFiles: skill-card.md (2304b), SKILL.md (5013b), _meta.json (135b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: lemlist-outreach\ndescription: Manage outreach campaigns, prospects, sequences, and lead activity in Lemlist — powered by ClawLink.\n---\n\n# Lemlist\n\nWork with Lemlist from chat — manage outreach campaigns, prospects, sequences, and lead activity.\n\nPowered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Lemlist API access yourself.\n\n## Quick start\n\n1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`\n2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet\n3. If ClawLink is not configured, call `clawlink_begin_pairing`\n4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device\n5. After the user confirms approval, call `clawlink_get_pairing_status`\n6. Tell the user to connect Lemlist at [claw-link.dev/dashboard?add=lemlist](https://claw-link.dev/dashboard?add=lemlist)\n7. When the user confirms Lemlist is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `lemlist` integration slug\n\n## Setup details\n\n### Installing the plugin\n\nIf the ClawLink plugin is not installed yet, tell the user to run:\n\n```\nopenclaw plugins install clawhub:clawlink-plugin\n```\n\nIf the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.\n\n### Pairing ClawLink\n\nIf ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.\n\n1. Call `clawlink_begin_pairing`.\n2. Tell the user to open the returned pairing URL in their browser.\n3. The user signs in to ClawLink if needed and approves the OpenClaw device.\n4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.\n\nThe resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.\n\n### Connecting Lemlist\n\nTell the user to open https://claw-link.dev/dashboard?add=lemlist and connect Lemlist there. The page opens the add-connection panel filtered to Lemlist. ClawLink's hosted page runs whichever provider flow is needed (hosted provider setup) — the user follows the hosted provider setup form. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `lemlist`.\n\n## Using Lemlist tools\n\nClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.\n\n### Discovery\n\n1. Call `clawlink_list_integrations` to confirm Lemlist is connected.\n2. Call `clawlink_list_tools` with integration `lemlist`.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `lemlist`.\n5. If no Lemlist tools appear, direct the user to https://claw-link.dev/dashboard?add=lemlist.\n\n### Execution\n\n1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.\n2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.\n3. Prefer read, list, search, and get operations before writes.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.\n5. Execute with `clawlink_call_tool`.\n6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## What you can do\n\nTypical Lemlist tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):\n\n- Inspect campaigns, sequences, and outreach performance\n- Search prospects and lead activity\n- Create or update leads after confirmation\n- Manage campaign state and related outreach operations carefully\n- Confirm before bulk outreach or sequence changes\n\n## Rules\n\n- Always use ClawLink tools for Lemlist. Do not ask the user for separate Lemlist credentials.\n- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.\n- Do not invent slash commands or ask the user to paste raw credentials.\n- Ask for confirmation before destructive, external-facing, or bulk write actions.\n- If Lemlist is not connected, direct the user to https://claw-link.dev/dashboard?add=lemlist.\n- Never echo or repeat the user's ClawLink credential.\n\n## Resources\n\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n- ClawLink Source: https://github.com/hith3sh/clawlink\n- Lemlist API: https://developer.lemlist.com/\n\nFile v0.1.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"lemlist-outreach\",\n \"version\": \"0.1.1\",\n \"publishedAt\": 1778675472101\n}\n\nFile v0.1.1:skill-card.md\n\n## Description:
\nManage outreach campaigns, prospects, sequences, and lead activity in Lemlist through ClawLink.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nSales, growth, and operations users use this skill to inspect Lemlist campaigns, search prospects and lead activity, and make confirmed updates through the connected ClawLink tool catalog.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Lemlist actions can change leads, campaigns, sequences, or external-facing outreach.
\nMitigation: Preview and confirm writes, destructive actions, bulk changes, and external-facing changes before execution.
\nRisk: Credentials or connection tokens could be exposed if users paste them into chat.
\nMitigation: Use ClawLink pairing and hosted connection flows, and do not ask users to paste raw Lemlist or ClawLink credentials.
\nRisk: Available Lemlist capabilities can vary by account permissions, scopes, and the current ClawLink catalog.
\nMitigation: List, search, and describe live ClawLink tools before claiming a capability or using an unfamiliar tool.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/lemlist-outreach)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n- [Lemlist API](https://developer.lemlist.com/)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, guidance]
\n**Output Format:** [Markdown with inline shell commands and user-facing guidance]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses live ClawLink tool discovery before describing or executing Lemlist actions.]
\n\n## Skill Version(s):
\n0.1.1 (source: server-resolved release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.1.0: 2 files, 2279 bytes\n\nFiles: SKILL.md (5026b), _meta.json (135b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: lemlist-outreach\ndescription: Manage outreach campaigns, prospects, sequences, and lead activity in Lemlist — powered by ClawLink.\n---\n\n# Lemlist via ClawLink\n\nWork with Lemlist from chat — manage outreach campaigns, prospects, sequences, and lead activity.\n\nPowered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Lemlist API access yourself.\n\n## Quick start\n\n1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`\n2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet\n3. If ClawLink is not configured, call `clawlink_begin_pairing`\n4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device\n5. After the user confirms approval, call `clawlink_get_pairing_status`\n6. Tell the user to connect Lemlist at [claw-link.dev/dashboard?add=lemlist](https://claw-link.dev/dashboard?add=lemlist)\n7. When the user confirms Lemlist is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `lemlist` integration slug\n\n## Setup details\n\n### Installing the plugin\n\nIf the ClawLink plugin is not installed yet, tell the user to run:\n\n```\nopenclaw plugins install clawhub:clawlink-plugin\n```\n\nIf the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.\n\n### Pairing ClawLink\n\nIf ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.\n\n1. Call `clawlink_begin_pairing`.\n2. Tell the user to open the returned pairing URL in their browser.\n3. The user signs in to ClawLink if needed and approves the OpenClaw device.\n4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.\n\nThe resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.\n\n### Connecting Lemlist\n\nTell the user to open https://claw-link.dev/dashboard?add=lemlist and connect Lemlist there. The page opens the add-connection panel filtered to Lemlist. ClawLink's hosted page runs whichever provider flow is needed (hosted provider setup) — the user follows the hosted provider setup form. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `lemlist`.\n\n## Using Lemlist tools\n\nClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.\n\n### Discovery\n\n1. Call `clawlink_list_integrations` to confirm Lemlist is connected.\n2. Call `clawlink_list_tools` with integration `lemlist`.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `lemlist`.\n5. If no Lemlist tools appear, direct the user to https://claw-link.dev/dashboard?add=lemlist.\n\n### Execution\n\n1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.\n2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.\n3. Prefer read, list, search, and get operations before writes.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.\n5. Execute with `clawlink_call_tool`.\n6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## What you can do\n\nTypical Lemlist tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):\n\n- Inspect campaigns, sequences, and outreach performance\n- Search prospects and lead activity\n- Create or update leads after confirmation\n- Manage campaign state and related outreach operations carefully\n- Confirm before bulk outreach or sequence changes\n\n## Rules\n\n- Always use ClawLink tools for Lemlist. Do not ask the user for separate Lemlist credentials.\n- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.\n- Do not invent slash commands or ask the user to paste raw credentials.\n- Ask for confirmation before destructive, external-facing, or bulk write actions.\n- If Lemlist is not connected, direct the user to https://claw-link.dev/dashboard?add=lemlist.\n- Never echo or repeat the user's ClawLink credential.\n\n## Resources\n\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n- ClawLink Source: https://github.com/hith3sh/clawlink\n- Lemlist API: https://developer.lemlist.com/\n\nFile v0.1.0:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"lemlist-outreach\",\n \"version\": \"0.1.0\",\n \"publishedAt\": 1778002258970\n}","readmeExcerpt":"Skill: Lemlist Owner: hith3sh Summary: Run personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, an... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:12:31.800Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic sourc","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Lemlist API │\n│ (User Chat) │ │ (OAuth) │ │ (v1) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Lemlist│ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Lemlist │\n │ File │ │ Auth │ │ Campaigns│\n └──────────┘ └──────────┘ └──────────┘"},{"language":"bash","snippet":"openclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart"},{"language":"bash","snippet":"# List campaigns\nclawlink_call_tool --tool \"lemlist_get_list_campaigns\" --params '{}'\n\n# Get campaign stats\nclawlink_call_tool --tool \"lemlist_get_campaign_stats\" --params '{\"campaign_id\": \"CAMPAIGN_ID\"}'\n\n# Get team info\nclawlink_call_tool --tool \"lemlist_get_team_info\" --params '{}'"},{"language":"bash","snippet":"clawlink_list_integrations"},{"language":"bash","snippet":"clawlink_list_tools --integration lemlist"},{"language":"bash","snippet":"clawlink_call_tool --tool \"lemlist_get_list_campaigns\" \\\n --params '{}'"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: lemlist-outreach\ndescription: Run personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, and automate outreach workflows with labeling and scheduling.\n---\n\n# Lemlist\n\n\n\nRun personalized email outreach campaigns via Lemlist. Manage campaigns and sequences, track lead engagement, search people and company databases, handle tasks, and automate outreach with labels and schedules.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=lemlist-outreach) for hosted connection flows and credentials so you do not need to configure Lemlist API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Lemlist |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Lemlist API │\n│ (User Chat) │ │ (OAuth) │ │ (v1) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Lemlist│ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Lemlist │\n │ File │ │ Auth │ │ Campaigns│\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Lemlist again.\"\n\n## Quick Start\n\n```bash\n# List campaigns\nclawlink_call_tool --tool \"lemlist_get_list_campaigns\" --params '{}'\n\n# Get campaign stats\nclawlink_call_tool --tool \"lemlist_get_campaign_stats\" --params '{\"campaign_id\": \"CAMPAIGN_ID\"}'\n\n# Get team info\nclawlink_call_tool --tool \"lemlist_get_team_info\" --params '{}'\n```\n\n## Authentication\n\nAll Lemlist tool calls are authentica"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"lemlist-outreach\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1780989151800\n}"},{"path":"skill-card.md","content":"## Description:\n\nRun personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, and automate outreach workflows with labeling and scheduling.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and sales teams use this skill to manage Lemlist outreach workflows, including campaigns, leads, sequences, schedules, tasks, suppression lists, analytics, and team information through a connected Lemlist account.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill depends on an unpinned external plugin for OAuth-backed Lemlist access.\n\nMitigation: Review the ClawLink plugin source, publisher, version, and update policy before installing or enabling it.\n\nRisk: Lemlist write operations can affect campaigns, lead statuses, schedules, unsubscribe or suppression settings, and exports.\n\nMitigation: Connect an account with the minimum needed permissions and verify previews before any write operation.\n\n## Reference(s):\n\n- [Lemlist API Documentation](https://docs.lemlist.com/)\n- [Lemlist Campaign Management](https://help.lemlist.com/en/)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/lemlist-outreach)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with inline shell commands and tool-call guidance]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May propose or execute Lemlist read and write operations through ClawLink after connection checks and user confirmation for writes.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Run personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, an... Skill: Lemlist Owner: hith3sh Summary: Run personalized email outreach campaigns via Lemlist. Manage campaigns, sequences, and tasks, track lead engagement, search people and company databases, an... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:12:31.800Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic sourc","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":902,"uniquenessScore":55,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T12:15:40.164Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T12:15:40.164Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T07:01:33.295Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}