Lemlist integration

Quick start

Call Lemlist from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Lemlist's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "LEMLIST_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

End-users supply their own Lemlist API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

54 actions exposed via the Lemlist integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• LEMLIST_CREATE_COMPANY_NOTE
• LEMLIST_DELETE_DELETE_SCHEDULE
• LEMLIST_DELETE_DELETE_UNSUBSCRIBE_EMAIL
• LEMLIST_DELETE_UNSUBSCRIBE_LEAD_FROM_CAMPAIGN
• LEMLIST_GET_ALL_WEBHOOKS
• LEMLIST_GET_CAMPAIGN_BY_ID
• LEMLIST_GET_CAMPAIGN_EXPORT_START
• LEMLIST_GET_CAMPAIGN_EXPORT_STATUS
• LEMLIST_GET_CAMPAIGN_SEQUENCES
• LEMLIST_GET_CAMPAIGN_STATS
• LEMLIST_GET_COMPANIES_SCHEMA
• LEMLIST_GET_CONTACT_MESSAGES