Wrike plugin

• Three regional hosts. Wrike runs the same v4 API on www.wrike.com, app-eu.wrike.com and app-us2.wrike.com, and an account lives on exactly one. Nothing in a token says which, so pass host: 'eu' or 'us2'; the default is www. A test asserts the routing.
• Both auth failures are a 401 not_authorized. The errorDescription is what separates them: Authorization method unknown means no header was sent at all, and Access token is unknown or invalid means one was sent and is wrong. Both are auth errors, but the distinction tells you whether a credential was configured.
• There is no account-level task create. A task always lives in a folder, so tasks.create takes a folderId and posts to /folders/{folderId}/tasks. For the account root, use the rootFolderId that account.get returns — it is a virtual folder, which is why reading the account once is worth doing.
• Every response is { kind, data: [...] }. Even a single task comes back inside an array, so the output schemas unwrap by index rather than pretending a get returns one object.
• Ids carry a prefix. IEAA… is a task, IEA… a folder, KU… a contact, TL… a timelog. The prefix is part of the id and is never stripped or rewritten.
• List filters are JSON arrays. status, responsibles and authors go in the query string as JSON (status=["Active"]); Wrike refuses a comma-joined value as invalid, so the plugin encodes the array for you. Date filters take a date or a start,end range.
• Folder paging needs a filter. With no filter folders.list returns the whole folder tree, which Wrike does not page; set project, title or permalink to page with pageSize and nextPageToken. Comments and contacts have no paging: comments.list takes a limit instead.
• Dates go in one dates object. Wrike has no top-level start or due parameter, so startDate and dueDate on tasks.create and tasks.update are folded into dates; dates: { type: 'Backlog' } clears a schedule.
• A task delete is recoverable. Wrike moves it to the recycle bin, and tasks.update with restore: true brings it back — which is why it is destructive but undoable.
• A folder delete takes its contents with it. Wrike moves the folder and every folder and task inside it to the recycle bin unless they have parents outside the deleted folder. There is no flag that refuses a non-empty folder. Check folders.tasks first if that matters.
• A timelog needs trackedDate, hours and comment. The date is the day the work belongs to, not when it was entered, and hours is what every report totals. Wrike requires the comment, though it may be empty.
• Comments are plain text. The plugin sends plainText: true, so Wrike strips HTML tags instead of rendering them, and the text comes back as written. A comment can be edited only in the 5 minutes after it is posted.
• No webhooks here. Wrike has REST routes for webhooks, but this plugin does not implement them.

• 23 typed API operations

​

Setup

npm install corsair @corsair-dev/wrike better-sqlite3
npm install --save-dev @types/better-sqlite3

yarn add corsair @corsair-dev/wrike better-sqlite3
yarn add --dev @types/better-sqlite3

pnpm install corsair @corsair-dev/wrike better-sqlite3
pnpm install --save-dev @types/better-sqlite3

bun add corsair @corsair-dev/wrike better-sqlite3
bun add --dev @types/better-sqlite3

import Database from 'better-sqlite3';
import { createCorsair } from 'corsair';
import { wrike } from '@corsair-dev/wrike';

export const corsair = createCorsair({
	plugins: [
		wrike(),
	],
	database: new Database('corsair.db'),
	kek: process.env.CORSAIR_KEK!,
	multiTenancy: true,
	hub: {
		projectApiKey: process.env.CORSAIR_API_KEY!,
		signingSecret: process.env.CORSAIR_SIGNING_SECRET!,
	},
});

wrike()

const { connectUrl } = await corsair.manage.connect.createLink({
	plugin: 'wrike',
	tenantId: 'acme',
});
// redirect the user's browser to connectUrl

​

Example API calls

const tenant = corsair.withTenant('acme');
await tenant.wrike.api.tasks.list({ pageSize: 25 });

const tenant = corsair.withTenant('acme');
await tenant.wrike.api.tasks.create({ folderId: 'IEAABCDEF12345', title: 'Ship the new checkout' });

​

What’s next