Wrike integration

Quick start

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

OverSkill hosts the OAuth application for Wrike. End-users click Connect on the integration card in your app, complete the OAuth flow with Wrike, and OverSkill stores the access token scoped to their account. No client_id / client_secret configuration needed on your side.

Supported auth schemes: OAUTH2.

Available actions

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

• WRIKE_BULK_MODIFY_GROUPS
• WRIKE_COPY_FOLDER
• WRIKE_COPY_FOLDER_ASYNC
• WRIKE_CREATE_ACCOUNT_WEBHOOKS
• WRIKE_CREATE_ASSETS
• WRIKE_CREATE_CUSTOMFIELD
• WRIKE_CREATE_FOLDER
• WRIKE_CREATE_FOLDER_BOOKING
• WRIKE_CREATE_FOLDERS_APPROVALS
• WRIKE_CREATE_FOLDERS_COMMENTS
• WRIKE_CREATE_FOLDERS_TIMELOG_LOCK_PERIOD
• WRIKE_CREATE_FOLDER_WEBHOOK