Zerobounce integration

Quick start

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

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

• ZEROBOUNCE_ACTIVITY_DATA
• ZEROBOUNCE_AI_SCORING_SINGLE
• ZEROBOUNCE_ALLOW_BLOCK_LIST
• ZEROBOUNCE_BATCH_VALIDATE_EMAILS
• ZEROBOUNCE_DELETE_AI_SCORING_FILE
• ZEROBOUNCE_DELETE_FILE
• ZEROBOUNCE_DOMAIN_SEARCH_FILE_STATUS
• ZEROBOUNCE_DOMAIN_SEARCH_GET_FILE
• ZEROBOUNCE_DOMAIN_SEARCH_SEND_FILE
• ZEROBOUNCE_DOMAIN_SEARCH_SINGLE
• ZEROBOUNCE_EMAIL_FINDER_DELETE_FILE
• ZEROBOUNCE_EMAIL_FINDER_FILE_STATUS