-
Using Unito
-
Items in Sync, Account Management, and Billing
-
Integration Documentation
- Airtable
- Asana
- Azure DevOps
- Basecamp
- Bitbucket
- ClickUp
- Favro
- GitHub
- GitLab
- Google Calendar
- Google Contacts
- Google Sheets
- HubSpot
- Intercom
- Jira
- Mailchimp
- MeisterTask
- Microsoft Excel
- Microsoft Outlook
- Miro
- monday.com
- Notion
- Pipedrive
- Salesforce
- Slack
- Smartsheet
- Teamwork
- Trello
- Wrike
- Zendesk
- Zoho Projects
-
Troubleshooting and FAQs
-
Unito's Trello Power-Ups
-
Data Privacy & Security
Limitations of Unito's Wrike Integration
Here's a breakdown of what Unito's Wrike integration can't do yet — and a few other considerations.
Unito's Wrike integration is designed to get crucial data out of your projects and into other tools. You've seen what Unito can do for Wrike users, so this article will cover what it can't do — yet.
-
Dependencies: You won't be able to sync dependencies quite yet.
-
Multiple subtask hierarchy: Unito will only sync the first subtask for each work item. This will not affect the subtask hierarchy that already exists in your tool, it just means you can’t sync that information over.
-
Time spent: Wrike’s Time spent field is incremental and as such can only increase in value. The field it is mapped to will be able to update it as long as its value is greater than the current time spent in Wrike. If the value in the field is less than Wrike’s Time spent, it will not be updated.
- Filtering by the Checkbox custom field: You won't be able to use the Checkbox custom field in your rules.
- Date+Time custom field: This field isn't supported by this integration.
- Wrike workflow status: Only one Wrike workflow status can be supported in a single flow.