Reply.io integration

Quick start

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

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

• REPLY_IO_ADD_CONTACT_TO_SEQUENCE
• REPLY_IO_ARCHIVE_SEQUENCE
• REPLY_IO_CLEAR_CONTACT_STATUS
• REPLY_IO_CONNECT_EXCHANGE_ACCOUNT
• REPLY_IO_CONNECT_GMAIL_ACCOUNT
• REPLY_IO_CREATE_CONTACT
• REPLY_IO_CREATE_SEQUENCE_STEP
• REPLY_IO_DELETE_CONTACT
• REPLY_IO_DELETE_EMAIL_ACCOUNT
• REPLY_IO_DELETE_SCHEDULE
• REPLY_IO_DELETE_SEQUENCE
• REPLY_IO_DELETE_USER