lemlist official
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill is coherent for Lemlist, but it gives an agent broad API-key authority to send outreach and change or export business data without clear in-skill approval boundaries.
Install only if you trust the publisher and are comfortable giving the agent Lemlist account access. Use a dedicated key if possible, start with a test campaign, and require the agent to preview and get explicit confirmation before sending messages, starting campaigns, deleting or changing records, exporting data, or creating webhooks.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A broad or misunderstood request could cause the agent to send outreach messages, start campaigns, or alter lead and campaign records in Lemlist.
The skill teaches a generic raw API helper and documents high-impact send and mutation endpoints, but it does not add confirmation, preview, dry-run, or scoping rules for those operations.
def api(path, method="GET", data=None): ... urllib.request.Request(f"{BASE}{path}", data=body, method=method) ... Inbox ... POST email/linkedin/whatsapp/smsRequire explicit user confirmation and previews for message sends, campaign starts, deletes/removals, imports, exports, webhooks, and bulk changes; constrain calls to specific user-approved campaign and lead IDs.
Anyone or any agent using the configured key may be able to act on the connected Lemlist account according to that key's permissions.
The Lemlist API key is expected for the integration, but it represents delegated account access and the registry credential metadata does not fully reflect that requirement.
metadata: Primary credential: none; SKILL.md: primaryEnv: LEMLIST_API_KEY ... Authorization: Basic base64(:LEMLIST_API_KEY)
Use a dedicated or least-privilege Lemlist key if available, rotate it when no longer needed, and only install the skill from a publisher you trust.
If a webhook is pointed at the wrong or untrusted endpoint, lead and campaign data could be exposed outside Lemlist.
Webhook creation can transmit lead/contact details to an external URL, and the documented verification is a shared-secret equality check rather than stronger request signing.
"targetUrl": "https://your-endpoint.com/webhook" ... "email": "...", "firstName": "...", "variables": {} ... Verification: payload.secret === your_configured_secret (no HMAC).Create webhooks only to trusted HTTPS endpoints, use a unique shared secret, validate incoming events carefully, and delete unused webhooks.
A user might trust the integration more than warranted and provide a Lemlist API key without independently verifying the publisher.
The artifact presents itself as an official integration, but the supplied metadata does not include a source or homepage that verifies that provenance.
Name: lemlist official ... Source: unknown ... Homepage: none
Verify the publisher or installation source through Lemlist or trusted marketplace channels before providing credentials.