Wrike

undefined

Detail	Value
Category	Project Management
Base URL	https://www.wrike.com/api/v4
Authentication	OAuth2
Endpoints	7
Connector key	wrike

Using Wrike in a workflow

1. Go to Connections and click New Connection.
2. Pick Wrike from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET	List Tasks
GET	Create Task
GET	Update Task
GET	List Folders
GET	List Contacts
GET	Create Comment
GET	List Timelogs

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

List Tasks

Detail	Value
Operation ID	list_tasks_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Wrike connection from the Connection dropdown.
3. In the Operation dropdown, select list_tasks_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Wrike API reference.

GET

Create Task

Detail	Value
Operation ID	create_task_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Wrike connection from the Connection dropdown.
3. In the Operation dropdown, select create_task_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Wrike API reference.

GET

Update Task

Detail	Value
Operation ID	update_task_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Wrike connection from the Connection dropdown.
3. In the Operation dropdown, select update_task_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Wrike API reference.

GET

List Folders

Detail	Value
Operation ID	list_folders_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Wrike connection from the Connection dropdown.
3. In the Operation dropdown, select list_folders_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Wrike API reference.

GET

List Contacts

Detail	Value
Operation ID	list_contacts_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Wrike connection from the Connection dropdown.
3. In the Operation dropdown, select list_contacts_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Wrike API reference.

GET

Create Comment

Detail	Value
Operation ID	create_comment_5
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Wrike connection from the Connection dropdown.
3. In the Operation dropdown, select create_comment_5.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Wrike API reference.

GET

List Timelogs

Detail	Value
Operation ID	list_timelogs_6
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Wrike connection from the Connection dropdown.
3. In the Operation dropdown, select list_timelogs_6.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Wrike API reference.