Backtourl pass token for dynamic multi auth

Hello All,

My team is working hard to integrate a new multi auth system into our 3rd party integration for . This would allow for users to select what phoneburner account they would like a given integration to be bound to. The flow is as follows.

Upon Selection of a new integration our app does a lookup in our database based on token (account ID and User ID). After this lookup the user is redirected to an external react page in witch the current auths (Lookup values) are displayed / option to add new accounts. After the user selects an account from the list of auths they are redirected to the back url to complete the integration.

The issue we are facing is once this user is sent to the backurl, to complete the integration, we are not able to send the selected account through the url. We need to pass something from the external page back to the integration button as upon completing the integration it will add a webhook in our database. We need a way to tie this webhook to the phoneburner account they selected on the external page.

If anyone has figured out a fix or has any ideas for this please let me know!

Hey @mclaughlin5360!

Can you explain a bit more about what data your app needs from the user before they set up the integration?

Also, are you using a custom action/trigger in your integration recipe?

I assume you need to 1) get user credentials, and 2) subscribe to webhooks. I’d suggest getting the credentials in the auth step, but subscribing to the webhooks in your trigger or action.

Here’s a typical auth flow that an integration would implement:

  1. User clicks recipe
  2. User is redirected to login page for app
  3. User selects credentials
  4. Server stores these credentials against their user ID (so the same user uses the same credentials each time)
  5. User redirects to backToUrl

Now, if you need to subscribe to some webhooks, it sounds like your recipe goes from PhoneBurner > In this case, I assume you are building a custom trigger. I would recommend subscribing to the webhooks only after your trigger subscribe URL is called (ie, not in the authorization step).

In this explanation I made a couple of assumptions about your current app’s design. Let me know if they’re incorrect, or I missed anything!

1 Like