What can we help you with?

e.g. Gantt chart, Creating tasks, Sharing folders

Submit Request Form via API?

5 comments

  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Daniel Schoenbach

    So I just found an old post I made that I had forgotten about, where Pavel M recommended the "external" Request Form feature. I'll look into that and try it out, and see if it meets my needs.

    https://help.wrike.com/hc/en-us/articles/209603169-Requests#external

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Daniel Schoenbach

    Looks like the external Requests feature doesn't work either, because it requires a CAPTCHA.

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Serge S

    Hi, Daniel! Thanks for posting your questions here!

    Currently, there's no API method to submit a Request form. The solution may be to create a separate user and use it as an API bot. Give this user access to the necessary Folders/Projects and issue a permanent access token for it.ย This is the best way to go besides the Request forms.

    On the other hand, could you pleaseย clarify how API makes things easier for you in this particular case? Right now it seems the approach with the external Request forms is the most viable option.

    Serge S Community Team at Wrike ๐ŸŒŽDiscover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Daniel Schoenbach

    Hi Serge, thanks for the reply.

    Creating an API bot user is definitely one option we are considering.ย The downside is that then anyone who works on the source code for the app (and thus has access to the permanent access token) effectively has access to all folders that the API bot user does. If the application is a native application whose source code can be disassembled, this means multiple API bots may be required, each with carefully-controlled permissions.

    I am trying to use the API in this case because it's much easier for my software to fill out the form than for the user to do it by hand.

    Imagine you are auditing a warehouse using an app running on a tablet. The app displays all the items that should be on each shelf location (as tracked by a database). As you walk past a shelf, you notice an item is missing.

    With the request forms, you must pull up Wrike, select the appropriate form, fill in the shelf number, the item number, the item description, and theย date and time you noticed the item was missing.

    All this information is already present in the app. With a simple click of a button marked "Report as Missing", the app could fill out the request form and submit it much more easily and accurately.

    Of course, the app could also create the task from scratch, rather than using the Request Form. However, then the app user must have access to the folder. This might be undesirable; for example, an unscrupulous auditor might begin stealing items from the warehouse, and then deleting the missing items reports before their crimes were discovered.

    I understand that there are pitfalls in allowing automated creation of tasks in folders that a user does not have access to, but I think there are compelling reasons to allow it.

    One possibility would be an API call that simply used WrikeBot to add the task to the appropriate folder.

    e.g.

    App calls API and creates new (private) task, with title, body, etc. Task is created.

    App calls API with the Task ID and a new Folder ID (one that the user does not have access to)

    The API shares the Task with Wrike Bot, then engages Wrike Bot to add the Task to the Folder specified by Folder ID.

    ย 

    This would avoid a complex API call to submit a request form, but still allow the same functionality, and could re-use the existing functionality of Wrike Bot (used by the Request Forms).

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Operations Manager

    We dealt with this problem by creating an Apache Reverse Proxy that auto inserts the appropriate token in the headers. App Developers make calls on the reverse proxy without any knowledge of the token and it all works. Then all that needs to be done is control on what the App users have access to. The reverse proxy can be a seperate piece of infrastructure which can be as tightly controlled as you wish.

    Is this helpful? 1
    Comment actions Permalink

Please sign in to leave a comment.

Folllowing List for Post: Submit Request Form via API?
[this list is visible for admins and agents only]

Community

Welcome ๐Ÿ––

Hi there! ๐Ÿ™‚ Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome ๐Ÿ–– Have you checked out this week's Release Notes yet?

Hey! ๐Ÿ‘‹ Curious about something? Visit How To to search and ask the Community for answers.

Welcome! ๐Ÿ‘‹ Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.