About the Wrike category

anon99371720 · October 23, 2023, 7:41am

Put topics about this connector package here.
Always check the ‘How to use the Alumio connector packages’ topic.

Extra information

System documentation: Wrike API Reference

Connector package documentation

1. Setting up HTTP Client Wrike

1.1 Steps

In the Alumio Dashboard, go to Clients → HTTP Clients. Create a new HTTP Client.
Select Wrike HTTP Client as PlatForm and click next step
Fill in the Base URI, Authorize URL, Access Token URL, Client ID and Client Secret.
(For more information, see Wrike Authentication Reference)
Click on “Grant access to Wrike” and you will be redirected to approve the grant.
You can optionally enable logging of request to get the log of the authentication.
Click next step, fill the name of the HTTP Client and finally you can save the HTTP Client for use.

2. Subscribing to Entities from Wrike

2.1 Steps

Go to Connections → Incoming and create a new incoming configuration and select “Wrike Subscriber” as the subscriber.
Select the entity you want to subscribe to from Wrike.
Add any request parameters needed to subscribe to the entity.
Select the Wrike HTTP Client to use.
You can optionally add a transformer to transform the request parameters into something you will request from Wrike.
You can also optionally enable pagination to allow Alumio fetches paginated entities.

2.2 General Concept

We follow Wrike documentation on building this connector, so you can easily use the connector based on Wrike API Reference.

Entity

The entity you want to subscribe to Wrike. Please refer to the entities from Wrike API Reference page.

Request Parameters

These are the parameters you can provide to get the needed entity based on the Wrike API Reference .

Please look at the example below on how to fill path field when subscribing “Users - Returns information about single user.” entity.

Based on the documentation, we can see that the end point require “userId” as a parameter. That is why we set the “userId” inside the path key in the Request Parameters.

Alumio will then make a request to Wrike with the URL /users/123

Path is the path parameter of the url. For example the {id}.
Query is defined set of parameters attached to the end of a url.
Example: www.url.com?type=true&start=0
Payload is the data contained within a request.

HTTP Client

The HTTP Client configuration you will use to access Wrike.

3. Publishing Entity to Wrike

3.1 Steps

Go to Connections → Outgoing, create a new outgoing configuration and select “Wrike Publisher” as the publisher.
Select the Method that you want the publisher to perform with the data.
Select the Wrike entity you want the data to be published to.
You can optionally add any query data to the request on the key query.
You can optionally add any payload data to the request on the key payload.
Select the HTTP Client to use.

3.2 General Concept

Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration), though you can also add or modify payload using the Request Transformer.

Method

Currently, we support HTTP Post method, HTTP Put method and HTTP Delete method on submitting data to Wrike.

Entity

We support publishing to most Wrike endpoints.
Please refer to Wrike API Reference page.

For example, we want to add a new contact. Please select “Post” as the Method and “Tasks - Create task in folder.” as the entity of the publisher.

Based on the documentation, it requires a path folderId and a request body. That is why we set the folderId inside the path key and the request body inside the payload key inside Alumio data.

Alumio will send an API request to Wrike with URL /folders/IEAF772LI5EUXAA7/tasks

Path is the path parameter of the url. For example the {id}.
Query is defined set of parameters attached to the end of a url.
Example: www.url.com?type=true&start=0
Payload is the data contained within a request.