Guide: Using Wrike with Databox (Custom API Integration)
IN THIS ARTICLE
Wrike Integration Details
IN THIS SECTION
Overview
Wrike is a digital work management tool that lets users track and coordinate projects, combining a simple user experience and interface with enough depth for power users.
The Wrike integration is designed for more tech-savvy users, as it syncs data through a Custom API integration. In order to create Wrike metrics in Databox, you’ll need to use the Metric Builder. Learn more about the basics of Metric Builder for Custom API Integrations here.
-
Custom API Integrations are available on Professional and Performer plans. Request a trial of Metric Builder by following
these steps.
-
If you’d like us to help you get set up with Wrike in Databox, please
fill out this request form or book a call with one of our product experts:
-
- Free Databox Users (or potential users) book a call
here.
-
- Paying Databox Customers book a call
here.
Integration basics
Integration status | Beta |
Type of Account access needed | Not specified |
Authorization type | OAuth2 |
Available endpoints | All REST endpoints |
Available requests | All GET requests |
Needed permissions (scopes) | Read-only |
Allowed API versions | All currently active API versions. Example: You can use a v1 of an API or v4, as long as they are both still supported. Deprecated APIs normally stop returning data. |
Timezone | UTC |
Dynamic date range support | Yes |
Pagination support | Yes |
Type of Pagination supported | Cursor based. Learn more here. |
Rate Limits | No |
Official documentation |
|
Follow the status of the API on the official changelog |
How to connect Wrike to Databox
IN THIS SECTION
How to connect Wrike to Databox
To connect a Wrike Account in Databox, go to Data Manager > + New connection. Type Wrike in the search bar and click on the Connect button. Next, click the green Connect now button.
This will open the Authorization window, where you will be prompted to enter your Wrike login credentials and authorize the Databox app.
What's the maximum amount of historical data initially available when you use a new Wrike Data Source Metric in Databox?
The amount of historical data available in Databox is dependent on the custom metric setup, API limitations, pagination limitations, and the user’s Databox plan:
- Custom Metric Setup: When a user creates a metric using an endpoint that supports date time parameters in the API request, those date time parameters determine the amount of historical data that will be pulled for the given metric. You can learn more about the date time parameters here.
- API Limitations: APIs may have limits set by the system itself on the amount of historical data that is stored/ can be accessed.
- Pagination Limitations: The pagination limit is set to 100 pages, which means that pagination will stop when the 100th page is reached. In cases where the metric is using pagination, of course, the interplay of date time parameters and pagination can have an impact on how much of the historical data the user can pull for a given metric.Learn more here.
- Databox Plan: The amount of historical data you're able to access in Databox is dependent on your Databox plan. Learn more here.
Pro Tip: In order to start syncing data for a Metric, you can add it to your Metrics screen, use it in a Scorecard, set a Goal around it, create an Alert for it, or add it to a Databoard. Learn more here.
What time zone does Wrike data sync in?
Wrike's data is synced in UTC. There are multiple parameters for specific endpoints such as "createdDate", "updatedDate" or "trackedDate" that have a start and an end date, where the timezone is applied to get results in your timezone.
What type of pagination is supported by Wrike Integration
The default number of items is set to 1000. The API uses cursor based pagination.
Learn more about pagination here.
How to use and create Wrike Metrics
IN THIS SECTION
How to access pre-built Wrike Metrics
How to create custom Wrike Metrics
Let’s walk through how to create a Custom Metric for Wrike.
In order to prepare API requests, you should reference API-specific documentation that can be found in the Databox app through the API Docs link in the top right of the Prepare API Request page. Or, use this direct link.
-
If you’re creating a GET request, define the Key and Value pair(s). The API documentation provides information on endpoints for a field/ argument, which will be the Key. The condition (i.e., an ID, true/ false, etc.) will be the Value.
-
If you’re creating a POST request, define the relevant JSON body.
Pro Tip: You can choose multiple Keys and Values for one Custom Metric. You can add an additional Key and Value by clicking on “+”.
-
To skip this step, select None.
- Use current time of storing data (Dynamic): Select this option if you don’t want to select a date field
- Use a field from response (optional): Select this if you want to select a date in order to see your data in predefined intervals.
-
You can customize the JSONata expression (optional) in the right editor panel.
-
Name your metric: Enter a name for your custom metric.
-
Data Aggregation: These selections determine how your data is handled. This especially impacts the way data is grouped and displayed for longer Date Ranges. Learn more here.
-
Favourable trend: You can select when "Trending UP is positive" or "Trending DOWN is positive," since some metrics are better (positive) when the value is lower (like Bounce rate, Churn rate, etc.). This will affect how comparison values and goal comparisons are calculated and calculated.
Additional Information
IN THIS SECTION
Integration Limitations
- Databox limits the use of its integrations to GET requests. This is because our integration only reads your data.
- Scopes: We use the following scopes: wsReadOnly, amReadOnlyUser, amReadOnlyGroup, amReadOnlyInvitation, amReadOnlyWorkSchedule, amReadOnlyUser, amReadOnlyAccessRole, Default
- Rate limits: Wrike limits the use of their API to 100 requests per minute per IP.
-
WARNING: If specific scopes of an integration allow you to create, change, delete or manipulate data in any other way, using such API calls can result in unexpected behavior. Databox is in no way liable for such API calls.