Ask Me Anything with Wrike Integrate: Part 2 - Intro to Postman and Webhooks

Pinned
This article is part 2 in an AMA series about Wrike Integrate. Check out part 1 before reading on.
 
Hi Community,
 
Miron here again for part 2 in our Wrike Integrate series and AMA. Please do leave any questions you have for me in the comments below 👇
 
So, you have watched the Wrike Integrate 101 video series in part 1 and you are now ready to start using Wrike Integrate. This article lists some of the key steps you can take to make your life easier.
 
STEP 1: Set up service accounts
 
One best practice is to create service accounts: user accounts dedicated to integrations. Integration flows need to run all the time, so you will need to ensure that the user accounts used are immune to disruptions like password changes or users leaving your company. A password change or an account deletion will break your integration flows. And because they will probably need access to all the data you have in Wrike, you will need to share everything with the account your flows use. In other words, dedicated accounts are more robust and more secure.
 
This Wrike Integrate Service Account Primer will provide you more details about the benefits of using service accounts, and this Wrike Integrate Account Setup guide will take you through the steps required to set it all up.
 
STEP 2: Set up Postman
 
Postman is a full-blown a collaboration platform for API development, but in the context of Wrike Integrate, it has an API client which is a great tool to:
  • Familiarise yourself with the Wrike - or any other – API.
  • Test various API calls.
  • Figure out what is the syntax for an API call you need to make, in case you need to use custom calls (i.e. API calls which are not built into the Wrike Integrate connector you are using).
  • Check what the response for a specific call is. This is necessary if you are using custom calls (Wrike Integrate connectors do not already know what the response looks like when it is a custom call).
  • Debug and troubleshoot recipes by comparing the same call in Wrike Integrate and Postman.
You can download the Postman API client from https://www.postman.com/downloads/
 
We are excited to be able to provide you several assets that will make your life easier while working with Postman. These are:
  • A Wrike API collection: this is a collection of examples for most of the Wrike API calls.
  • A Wrike environment: this is a definition file you load into Postman containing your authentication token and API URL.
  • A video explaining how to set Postman up for use with the Wrike API.
Watch the video first and then download and install Postman. Once done, you can download the Wrike API Collection and the Wrike Environment and import them using the ‘File;Import’ menu.
 
STEP 3: Get up to speed with Webhooks
 
Wrike Integrate allows you to ‘listen’ to events in Wrike and react to them. These are known as triggers. For example, you might want to take some action if a task status has been updated. The built-in triggers allow you to poll Wrike or react in real-time to project/task updates, but not define what specific update you want to react to. For example, updating a task's dates or its status both count as an ‘update’ and both will cause the trigger to fire. But if you are only interested in the status update, your recipe will need to check what exactly was updated. Webhooks allow you to be more granular. They allow you to set up – in Wrike - triggers that are both real-time and granular. For example;
  1. Project Custom Field changed
  2. Task assignees changed in a specific folder
  3. A comment was added to a task in a specific space
This allows you to be very specific about what you want to react to. Webhooks are a more advanced feature of the Wrike API, but one that can be easily mastered with the help of this Webhooks primer video. Let me know if you need any more assistance after having watched this.  
 
That's it for our series and AMA on Wrike Integrate. Ready for your questions! 👍
 

Miron Mizrahi Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Miron Mizrahi Wrike Team member Become a Wrike expert with Wrike Discover

2
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
4 comments

Thank you for this excellent two part walkthrough.  It was vital to getting the Webhooks established that I'm looking for.  After receiving the JSON TaskDateChange payload in the recipe, what is the best way to parse the TaskID out of the received message for use in further recipe steps?  Do you recommend setting the payload to be a string so a JSON parse step can read through the data?  I'm having trouble getting that received webhook message to passthrough.  Thank you!

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Ben,

Thanks for your question and your comments.

When you set up the webhook, you need to specify the payload. Once you do that, every element in the payload will be available for you as a data pill just like any other action you have in Wrike Integrate. I am covering this towards the end of my video. So try these steps:

  1. Start the recipe and in Wrike generate an event which will trigger the webhook, i.e. change dates on a task
  2. Check the job log in Wrike Integrate and check the output of the webhook step. Copy the JSON payload
  3. Stop the recipe, edit it and in the webhook step, under payload schema, paste, click generate schema and save
  4. This will create the structure with all elements directly under the Payload object. you need to add an intermediary object to get the structure shown below. So click add field, add a field of type array with the name 'array' and then drag and drop all the other fields onto it 
  5. Now in the recipe in subsequent actions you should be able to pick the task ID as a data pill from the recipe data widget

Miron Mizrahi Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Miron Mizrahi Wrike Team member Become a Wrike expert with Wrike Discover

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi,
I am not able to create app using the create new app button.
And I don't find APP directory and App access in the side bar, can you please tell what to do.
I have tried the form which is in the API overview page, by using that I am able to create one app but, it also took so much of time to create. While I am using the postman to trigger the API using permanent access token for some if I add some properties it is giving Operation is not allowed due insufficient user rights or account license limitations.

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Raghu Ram Dhigajarla thanks for your comments. What you can do with the API will depend on your subscription levels and access rights. for example, if you are on the Business subscription then you cannot use Job Roles API because Job Roles are only available in the Pinnacle subscription. similarly, if you do not have permission to create a project in a specific location, you will get an error if you try and do so using the API.

It is not really feasible for me to troubleshoot specific issues you are seeing. I suggest you submit a support ticket.

Miron Mizrahi Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Miron Mizrahi Wrike Team member Become a Wrike expert with Wrike Discover

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Ask Me Anything with Wrike Integrate: Part 2 - Intro to Postman and Webhooks
[this list is visible for admins and agents only]

Top
Didn’t find what you were looking for? Write new post