Enginemailer integration

Quick start

Call Enginemailer from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Enginemailer'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(
  "ENGINEMAILER_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 Enginemailer 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

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

• ENGINEMAILER_ACTIVATE_SUBSCRIBER
• ENGINEMAILER_ADD_UPDATE_SUBSCRIBER
• ENGINEMAILER_BATCH_UPDATE_STATUS
• ENGINEMAILER_BATCH_UPDATE_SUBSCRIBERS
• ENGINEMAILER_CHECK_EXPORT_STATUS_V2
• ENGINEMAILER_CONNECT
• ENGINEMAILER_CREATE_CAMPAIGN
• ENGINEMAILER_DELETE_CAMPAIGN
• ENGINEMAILER_DELETE_RECIPIENT_LIST
• ENGINEMAILER_DELETE_SUBSCRIBER
• ENGINEMAILER_EXPORT_CSV_REPORT_V2
• ENGINEMAILER_FIND_SUBSCRIBER