Skip to main content

Good morning, Sir, Madam,


I built an app (nodejs) that I am about to submit in the marketplace.


The challenge that I face is that my app is supposed to require OAuth consent just before the installation. When I launch the installation of the app, I can give the Oauth consent, BUT after the user gives the Oauth permissions, the install never happens.


Please, can you give me an example where OAuth consent is requested during the install and user cannot complete the installation?


Regards,


Richard .

Good question and welcome to the community!


In the monday apps framework, we differentiate between the install process and the OAuth process.


The install process can only be initiated by clicking an install link (which you can get in the app management section). It looks similar to the OAuth flow, but they are for totally different permissions.


The OAuth flow is intended for after someone installs the app, and gives an app permission to access the account data via API.

Good morning,

Thank you for your answer. Please, I am still facing some challenges, and I need your help:




  • Where should I put the redirect url?




  • The application is being installed successfully (when I add /install in the url), but call back url is never triggered (see attached)

    image (8)




  • If we install first and we request the authorization then we make a second call and we request the authorization again, it works. Our problem in this scenario is that we need to request to the user to validate the authorization twice. Please can you help us understand how we install, we get the the authorization and we get the code in a single call?




Regards,

You cannot do installation and OAuth in a single call. They are two unrelated processes.


Installation process

When the installation process finishes, the user will be redirected to the admin apps page or marketplace (depending on how they installed the app). They will not be redirected to your OAuth callback URL.


OAuth flow

If you want to initiate the OAuth flow, you can only do it when a user has opened your app. This means –



  • Board/dashboard view: Navigated to the board/dashboard and opened your view

  • Doc Action: Opened a doc and invoked your action

  • Integration: Clicked your integration recipe and redirected to your “Authorization URL”


Once the user has opened your app, you can redirect them to the OAuth Request URL and start the OAuth flow.


Let me know if that explanation makes sense – it can be confusing since these flows are so similar!

Reply


Terms & ConditionsCookie settings