Integration Auth

Hello Guys,

Me and my developer are facing a rather tough issue for us. Most likely something very simple and silly.

We want to replicate the ability seen in other integrations to store multiple auths inside the “Pre auth screen”. We have AUTH setup in the integration however it only allows the user to use one account. We could not seem to find the documentation on this if anyone can direct us that would be great.

Hey @jackjack2202 :wave:

Thanks for allowing us to help out with this issue!

I was just wondering if you were able to take a look at our OAuth reference guid? it provides two different ways to construct the OAuth flow for the user, and one of them will provide the option to see multiple accounts in the dropdown menu in the top-right corner:

Here’s the link to the article on this that goes into further detail on the setup steps:

I hope this is helpful :slight_smile: Let me know if this sheds more light on the configuration here!


@AlexSavchuk I have read through all of these documents. However in further research with another developer of mine I was able to figure out I believe its an external react page to manage the auths. Can you confirm this? Ive added a screenshot.


Ah, got it. Just to make sure we’re on the same page here, are you looking to recreate this kind of look? This seems to be related to a native integration that built with Gmail, where you are able to use different accounts to connect to different inboxes. I’d love to learn a bit more about how this would be applicable to your app - could you shed a bit more light on this?


Ok and thats what we figured based on the fact that all built apps share a similar UI to their auth page. We are trying to do something very similar. We are working on building an integration for . When the user auths we want the integrations to be able to work for any users account within PB. Many employees inside of may also have there own PB account. This is why we need to be able to some how select witch Auth to use.


Got it, thanks for clarifying further!

In that case, this would be handled by your app’s Authorization URL. You would then get the JWT token and verify them in your app’s logic. Every time a user installs the app or adds a new recipe, you’d send them to your app’s Authorization URL, or if they already have a token, to the Back To URL.

You can find more info on this here:

Let me know if this helps clarify :slight_smile:


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.