Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Wrike

Wrike integration for Flows360 workflows.

CategoryProductivity
AuthenticationOAuth 2.0
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Wrike with Flows360

Wrike integration for Flows360 workflows.

Use the Wrike connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 9 actions and 3 triggers.

Available actions

  • Create Task
  • Update Task
  • Create Folder
  • Create Project
  • Add Comment
  • Upload Attachment
  • Find Task
  • Find Folder / Project
  • Plus 1 additional declared action.

Available triggers

  • New Task
  • New Folder
  • New Subtask Created

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Wrike
  • Package: @activepieces/piece-wrike@0.2.0
  • Exact artifact digest: sha256:5877fb8984dac20aa560f1a9c4e18797f94c82a43ffa83e7c2c13ea4fecd1942
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Task (create_task), Create a new task in Wrike Classification: read.
  • Update Task (update_task), Update fields of an existing task in Wrike Classification: read.
  • Create Folder (create_folder), Create a new folder in Wrike Classification: read.
  • Create Project (create_project), Create a new project in Wrike Classification: read.
  • Add Comment (add_comment), Add a comment or internal note to a task or folder Classification: read.
  • Upload Attachment (upload_attachment), Upload a file and attach it to a task or folder Classification: read.
  • Find Task (find_task), Retrieve a task by its ID or lookup fields Classification: read.
  • Find Folder / Project (find_folder), Retrieve folder / project metadata by ID or name Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Task, webhook.
  • New Folder, webhook.
  • New Subtask Created, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects12
Supported actions9
Triggers3

Authentication

Authentication method: OAuth 2.0

Authentication profiles

connection · oauth2

Supported objects

ObjectReadWriteNotes
Create Task Yes No Create a new task in Wrike
Update Task Yes No Update fields of an existing task in Wrike
Create Folder Yes No Create a new folder in Wrike
Create Project Yes No Create a new project in Wrike
Add Comment Yes No Add a comment or internal note to a task or folder
Upload Attachment Yes No Upload a file and attach it to a task or folder
Find Task Yes No Retrieve a task by its ID or lookup fields
Find Folder / Project Yes No Retrieve folder / project metadata by ID or name
Custom API Call Yes No Make a custom API call to a specific endpoint
New Task Yes No webhook trigger declared by the pinned package.
New Folder Yes No webhook trigger declared by the pinned package.
New Subtask Created Yes No webhook trigger declared by the pinned package.

Supported actions

Create Task · Read

Create a new task in Wrike

create_task · Risk: low · Retry: safe

Inputs

  • folderId · string · Required, The ID of the folder where the task will be created
  • title · string · Required, The title of the task
  • description · string · Optional, The description of the task
  • status · string · Optional, The status of the task
  • importance · string · Optional, The importance/priority of the task
  • assignees · array · Optional, User IDs to assign to the task
  • start_date · string · Optional, Task start date (format: YYYY-MM-DD)
  • due_date · string · Optional, Task due date (format: YYYY-MM-DD)
  • duration · number · Optional, Task duration in minutes
  • customFields · array · Optional, Custom field values for the task
Update Task · Read

Update fields of an existing task in Wrike

update_task · Risk: low · Retry: safe

Inputs

  • taskId · string · Required, The ID of the task to update
  • title · string · Optional, The new title of the task
  • description · string · Optional, The new description of the task
  • status · string · Optional, The new status of the task
  • importance · string · Optional, The new importance/priority of the task
  • assignees · array · Optional, User IDs to assign to the task (replaces existing assignees)
  • start_date · string · Optional, Task start date (format: YYYY-MM-DD)
  • due_date · string · Optional, Task due date (format: YYYY-MM-DD)
  • duration · number · Optional, Task duration in minutes
  • customFields · array · Optional, Custom field values to update for the task
Create Folder · Read

Create a new folder in Wrike

create_folder · Risk: low · Retry: safe

Inputs

  • parentFolderId · string · Optional, The ID of the parent folder where the new folder will be created. Leave empty to create at root level.
  • title · string · Required, The title of the folder
  • description · string · Optional, The description of the folder
  • shareds · array · Optional, User IDs to share the folder with
  • project · boolean · Optional, Whether this folder should be created as a project with additional project settings
  • projectOwnerId · string · Optional, The ID of the user who will own the project (required when creating as project)
  • projectStartDate · string · Optional, The start date of the project (format: YYYY-MM-DD)
  • projectEndDate · string · Optional, The end date of the project (format: YYYY-MM-DD)
Create Project · Read

Create a new project in Wrike

create_project · Risk: low · Retry: safe

Inputs

  • parentFolderId · string · Optional, The ID of the parent folder where the project will be created. Leave empty to create at root level.
  • title · string · Required, The title of the project
  • description · string · Optional, The description of the project
  • ownerIds · array · Optional, User IDs who will own the project
  • shareds · array · Optional, User IDs to share the project with
  • start_date · string · Optional, Project start date (format: YYYY-MM-DD)
  • end_date · string · Optional, Project end date (format: YYYY-MM-DD)
Add Comment · Read

Add a comment or internal note to a task or folder

add_comment · Risk: low · Retry: safe

Inputs

  • entityType · string · Required, Select whether you want to add the comment to a task or folder
  • entityId · string · Required, The ID of the task or folder to add the comment to
  • text · string · Required, The text content of the comment
  • plainText · boolean · Optional, Whether the comment should be treated as plain text (no HTML formatting). Default is HTML formatting.
Upload Attachment · Read

Upload a file and attach it to a task or folder

upload_attachment · Risk: low · Retry: safe

Inputs

  • entityType · string · Required, Select whether to attach the file to a task or folder
  • entityId · string · Required, The ID of the task or folder to attach the file to
  • file · object · Required, The file to upload and attach
  • fileName · string · Optional, Optional custom name for the uploaded file
Find Task · Read

Retrieve a task by its ID or lookup fields

find_task · Risk: low · Retry: safe

Inputs

  • taskId · string · Optional, The ID of the task to retrieve. If provided, other search criteria will be ignored.
  • title · string · Optional, Search for tasks by title (partial match)
  • folderId · string · Optional, Search for tasks within a specific folder
  • status · string · Optional, Filter tasks by status
  • importance · string · Optional, Filter tasks by importance/priority
  • assignees · array · Optional, Filter tasks by assignee user IDs
  • authors · array · Optional, Filter tasks by author user IDs
  • pageSize · number · Optional, Maximum number of tasks to return (max 1000)
  • sortField · string · Optional, Field to sort tasks by
  • sortOrder · string · Optional, Sort order for results
Find Folder / Project · Read

Retrieve folder / project metadata by ID or name

find_folder · Risk: low · Retry: safe

Inputs

  • folderId · string · Optional, The ID of the folder/project to retrieve. If provided, other search criteria will be ignored.
  • title · string · Optional, Search for folders/projects by title (partial match)
  • parentIds · array · Optional, Search for folders/projects within specific parent folders
  • project · boolean · Optional, Filter to only return projects (folders marked as projects)
  • pageSize · number · Optional, Maximum number of folders/projects to return (max 1000)
  • authors · array · Optional, Filter by authors (users who created the folders)
  • owners · array · Optional, Filter by owners (users who own the projects)
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Task · Webhook

Fires when a new task is created in Wrike (optionally within a folder).

Inputs

  • folderId · string
New Folder · Webhook

Fires when a new folder (or project) is created in Wrike.

Inputs

  • parentFolderId · string
New Subtask Created · Webhook

Triggers when a subtask is created.

Inputs

  • parentTaskId · string

Setup

Setup

  1. Add the Wrike connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-wrike@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 9 actions and 3 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Wrike connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-wrike@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com