Wrike

Read and write Wrike spaces, folders, projects, tasks, subtasks, dependencies, comments, timelogs and custom fields.

Keep project plans, assignments and logged hours in Wrike aligned with delivery, finance and CRM systems.

Build a flow with Wrike Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

attachments

List task attachments
Source
Attachment metadata for a task; file contents are not transferred.

comments

Add task comment
Destination
Not retried automatically
Adds a comment to a task.
List task comments
Source
Comments on a task as plain text.
Edit comment
Destination
Duplicate protected
Replaces the text of a comment created in the last five minutes.

contacts

List contacts
Source
Users, groups and collaborators that can be assigned work.

custom fields

List custom fields
Source
Custom field definitions with their types and settings.

dependencies

Create task dependency
Destination
Not retried automatically
Links the task to a predecessor or a successor task.
List task dependencies
Source
Predecessor and successor links of a task.
Update task dependency
Destination
Duplicate protected
Changes the relation type or lag of a dependency.

folders

Create folder
Destination
Not retried automatically
Creates a folder below a parent folder or the space root folder.
List folders
Source
Incremental
Folders and projects in the account, a space or below a folder.
Update folder
Destination
Duplicate protected
Updates the title, description or custom fields of a folder.

projects

Create project
Destination
Not retried automatically
Creates a project with owners, status and dates below a parent folder.
List projects
Source
Incremental
Projects in the account, a space or below a folder, with status, owners, dates and custom fields.
Update project
Destination
Duplicate protected
Updates project title, status, owners, dates or custom fields.

spaces

List spaces
Source
Spaces visible to the token owner.

tasks

Create task or subtask
Destination
Not retried automatically
Creates a task in a folder or project. Provide parent task IDs to create a subtask; omit dates to create a backlog task.
Get task
Source
A single task with its full description.
List tasks
Source
Incremental
Tasks and subtasks in the account or a folder or project, with assignees, dependencies and custom fields.
Update task
Destination
Duplicate protected
Updates supplied fields. Assignees, parent tasks and folders are added or removed explicitly.

timelog categories

List timelog categories
Source
Categories that can be assigned to timelogs.

timelogs

Log time
Destination
Not retried automatically
Records hours against a task.
List timelogs
Source
Incremental
Time logged in the account or on a task.
Update timelog
Destination
Duplicate protected
Updates hours, date, comment or category of a timelog.

workflows

List workflows
Source
Account workflows and their custom statuses.

Authentication

Wrike permanent access token

Plans and access

All Wrike plans with API access; custom fields and timelogs depend on plan features. Results follow the permissions of the user who generated the permanent token.

Test environment

Use a Wrike trial account; Wrike has no separate sandbox.

Rate limits

Approximately 400 requests per minute per user or IP; HTTP 429 on excess.

Provider events

Wrike webhooks signed with X-Hook-Signature (HMAC-SHA256). Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Wrike documents parameters in the query string; Nexra sends the same parameters as an application/x-www-form-urlencoded body with JSON-encoded arrays and objects, as in Wrike's curl examples.
The nextPageToken position in the response envelope is not in Wrike's published response schema; Nexra reads it next to kind and data.
Comments can only be edited within five minutes of creation (Wrike rule).
Attachment metadata is read; file contents and temporary download URLs are not transferred.
Wrike has no idempotency key; uncertain creates are not repeated automatically.
Deletes, approvals and custom-field administration are not implemented.