Oauth authorization during app install - Monday.com NodeJS custom App

monday Apps & Developers
, , , , ,
1

Good morning, Sir, Madam,

I am building a custom monday.com application. I would like to make it mandatory to get customer oauth authorization during app install.

Do you have a guide that explains it?

2

Hello there @rmanga86 and welcome to the community!

I hope you like it here :muscle:

Regarding your question, the documentation about OAuth can be found here.

Depending on what app feature your app has, you can use different methods for showing the OAuth screen to get the OAuth token from the users.

If you have an integration feature, you can use the Authorization URL as described here.

If you have a view, you can use the OAuth request URL from your app’s OAuth tab in the app’s configuration page to display it in your view.

There is no way to show the OAuth scopes authorization screen automatically within the installation process.

Let me know if you have any other questions!

Cheers,
Matias

3

Good morning,

Thank you for your answer.

If I use the API token to authenticate my API, how can I get the different API token for each user who will download my application from the Marketplace?
This is the use case description:

  • Customer A has API Token A
  • Customer B has API Token B
  • Customer C has API Token C
    How can I configure my app to use right API Token for customer A, B and C?

Thank you for your help,

Regards,

4

Hello again @rmanga86,

Apps in our marketplace should not ask for personal API tokens. Instead, they should use OAuth or seamless authentication (Seamless authentication can also be used via the SDK).

If you use OAuth, you would need to follow the instructions in the link, to get the OAuth token from each user (each user will have a different OAuth token) and save those tokens on your end to then use them. Which seems, it might be what you are in need of.

If you use seamless authentication, as the documentation indicates, you would be using a shortLivedToken that belongs to each user. Each time you use it, you would be querying data or updating data “on behalf” of a specific user using that user’s shortLivedToken.

I hope that helps!

Cheers,
Matias