One of the shortcomings of the usual Wrike search API endpoint is that it does not allow you to search by Parent Folder ID or Parent Project ID. This means that if you want to find all the tasks inside a particular folder or project, you’re out of luck unless you learn to use the HTTP Request card.
The HTTP Request card is built in to the Wrike connector (and others) and allows users to skip the authentication part of hitting API endpoints and just worry about the data they’re sending. In the connectors we provide this for, this allows you to try anything the API lets you do without needing us to make a particular card for the action.
The Wrike API does have an endpoint that allows you to get the list of tasks inside a particular project or ID, but that’s all it does so we haven’t added a particular card for it. Instead, let’s see how you could construct your HTTP Request card in order to get this information.
When you initially create the Wrike HTTP Request card, you’re going to want to select “GET” as the Request Type in the options. Then, as you can see above, the relative URL you construct to get this list of all tasks is simple. You just insert your Folder or Project ID in between “/folders/” and “/tasks”. And that’s it! You don’t need to put anything in the query or in the headers.
The body output of the card will return something that looks like this:
"title": "Wrike HTTP Demo Folder Task 1",
"title": "Wrike HTTP Demo Folder Task 2",
You can just grab the “data” list of objects out of there and use that information however you’d like.
For example, I could take that list and filter it down by status to find out how many of my current tasks are Active. This would work with any of the other Wrike statuses as well.
That filtering on the task status is just one of the many ways you can utilize the Wrike data unlocked by the HTTP Request card. You could perform an operation on every single task in a project if you wanted. You could use that list of tasks and create corresponding tasks in another app like Workfront or JIRA. You could even just take that data and put it in a simple spreadsheet.
The entire Wrike API documentation is linked below so if you’re looking for some other ideas of functionality to enable with this card, it’s a good place to start.
If you have any questions or follow up ideas on what to use these HTTP request cards for, just post them here!