Reply integration

Quick start

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

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

• REPLY_CREATE_LIST
• REPLY_DELETE_EMAIL_ACCOUNT
• REPLY_DELETE_LIST_BY_ID
• REPLY_DELETE_SEQUENCE
• REPLY_DELETE_USER
• REPLY_GENERATE_ULID
• REPLY_GET_ALL_LISTS
• REPLY_GET_BLACKLIST_ALL
• REPLY_GET_CAMPAIGN_SCHEDULES_ALL
• REPLY_GET_CAMPAIGNS_FOR_CONTACT
• REPLY_GET_CONTACTS_IN_LIST_BY_ID
• REPLY_GET_LIST_BY_ID