Wrike is a digital work management tool that helps users track and coordinate projects.

Data integration: Skyvia supports importing data to and from Wrike, exporting Wrike data to CSV files, replicating Wrike data to relational databases and synchronizing Wrike data with other cloud apps and relational databases.

Backup: Skyvia Backup does not support Wrike.

Query: Skyvia Query supports Wrike.

Wrike-Specific Features and Limitations

Skyvia has the following limitations for Wrike:

  • In the Data Integration product, Wrike connections are supported only for packages, which use a new data integration runtime.

    Make sure that the Use new runtime checkbox is selected on the tab bar if you want to use Wrike in your package.

  • Skyvia supports DML operations for such Wrike objects:
    • INSERT, UPDATE, DELETE: Approvals, Comments, Groups, Invitations, Spaces, Tasks, Timelogs, UserScheduleExclusions, WorkScheduleExclusions, Workschedules.
    • INSERT, UPDATE: CustomFields, Workflows.
    • UPDATE, DELETE: Folders.
    • UPDATE: Contacts, Users.
    • DELETE: Attachments.
  • Skyvia supports Replication with Incremental Updates for such Wrike objects: Account, Approvals, Attachments, Comments, Tasks, Timelogs.

  • Skyvia supports Synchronization for such Wrike objects: Approvals, Timelogs.

  • Users object. You can get data from this object only by the specified Id.

  • Invitations object. When performing the Delete operation, records are not physically deleted, their status are simply changed to Canceled.

  • AuditLog object is in the list of other Wrike objects, but data can only be retrieved for the users with Enterprise plan.

  • Spaces object. When getting data from the Spaces object, the following fields are used: Members, SuggestedProjectWorkflowIds, SuggestedTaskWorkflowIds.

    The value in the MembersAdd, MembersUpdate, MembersRemove, SuggestedProjectWorkflowsAdd, SuggestedProjectWorkflowsRemove, SuggestedTaskWorkflowsAdd, SuggestedTaskWorkflowsRemove fields are used for the Update operation.

    When performing an Insert operation, the Members field should have the following format: [{"id":"KUFK5PNB","accessRoleId":"IEC7PGVEND777777","isManager":true}].

    When performing an Update operation, the MembersAdd, MembersUpdate fields should have the same format. Meantime, in the MembersRemove field, you need to specify only the list of Ids you want to remove (for example, ["KUFK5PNB", "KUFK5PN8"]).

  • WorkSchedule object. When getting data from the WorkSchedule object, data in the Workweek field will be displayed as [{"workDays":["Mon","Tue","Wed","Thu","Fri"]}].

    When performing Insert and Update operations, the Workweek field should look like below:

    [{"dayOfWeek":"Mon","isWorkDay":true},{"dayOfWeek":"Tue","isWorkDay":true},{"dayOfWeek":"Wed","isWorkDay":true},{ "dayOfWeek":"Thu","isWorkDay":false},{"dayOfWeek":"Fri","isWorkDay":false},{"dayOfWeek":"Sat","isWorkDay":false},{"dayOfWeek ":"Sun","isWorkDay":false}]

    Data about users is returned to the UserIds field, the AddUsers and RemoveUsers fields will be empty.

    You should use the AddUsers field when performing Insert and Update operations.

    You should use the RemoveUsers field when performing an Update operation.

    Field example looks like: ["KUAHVFPE"].

  • Tasks object. When getting data from the Tasks object, data will be displayed in the ParentIds, SharedIds, ResponsibleIds, FollowerIds, SuperTaskIds fields. These fields are also used for performing Insert operations.

    Such fields as AddParents, AddShareds, AddResponsibles, AddFollowers, AddSuperTasks, RemoveParents, RemoveShareds, RemoveResponsibles, RemoveSuperTasks will remain empty as they are only used when performing an Update operation.

  • Comments object. To obtain information from the Comments object, you need to specify the period for which these comments must be received. To do this, you have to specify the period in the Start and End fields. These fields are used only to set the filter and will stay empty after query execution. The maximum period for a condition is 7 days.

    A comment can be inserted to a folder via a usual INSERT operation or to a task through a stored procedure with parameters: call CreateTaskComment(:task1,:text).

    You can update comments only within 5 minutes after their creation. When you try to update comments later, you will get an error.

  • Approvals object. An approval can be inserted to a task via a usual INSERT operation or to a folder through a stored procedure with parameters call CreateFolderApproval(:FolderId,:Description,:DueDate,:Approvers,:Attachments,:AutoFinishOnApprove,:AutoFinishOnReject).

  • Dependencies object. You can perform Update and Delete operations, using stored procedures with parameters shown below:

    call UpdateDependencies(:dependencyId,:RelationType). Valid values for the RelationType field are "StartToStart","StartToFinish","FinishToStart""FinishToFinish".

    call DeleteDependencies(:dependencyId).

Wrike Connections

To create a connection to Wrike, you simply need to enter it via OAuth 2.0. The OAuth authentication token is stored on the Skyvia server. Your Wrike account login and password are not stored on the Skyvia server.

To start creating a connection, follow the below steps:

  1. Click +NEW in the top menu.
  2. Click Connection in the menu on the left to open the Select Connector page.
  3. In the opened pane, click Wrike.
  4. In the Connection Editor page, specify a connection name that will be used to identify the connection.
  5. Click Sign In with Wrike.
  6. In the opened window, enter your email used when signing in to Wrike.

    Login window

  7. Next, enter your password.
  8. Click Accept to give permission to Skyvia.
  9. The authentication token is generated.

    Connection Editor window

  10. Optionally, you can select the Suppress Extended Requests checkbox to reduce the number of API calls. However, beforehand read more about this option below.
  11. Use the Test Connection button to make sure that the connection is successful and then click Create Connection.

Suppressing Extended Requests

For some objects, Wrike API returns only part of the fields when querying multiple records. In order to query values of additional fields, Skyvia performs additional extended requests. Such API requests can be performed for each record of such object. However, this can decrease performance and significantly increase the number of API calls used.

To reduce the number of API calls, you can select the Suppress Extended Requests checkbox. However, please note that some of the fields in such objects will not be available in Skyvia (will return empty values) even if they have values in Wrike because Wrike API does not return them without extended requests.

Supported Actions and Actions Specifics

Wrike connector supports the following actions: