How to Capture the "code" Parameter After Facebook Social Login in Weweb?

[Vitorporanga]

Hello everyone!

I’m implementing Facebook social login in my Weweb x Supabase application and I’m struggling to capture the “code” parameter that Facebook sends after authentication.

##What I’m trying to do:

I need to capture the “code” parameter from the URL after the OAuth redirect to make subsequent calls to the Meta Ads API. In Bubble, this functionality is simple to implement using the “Get code from page URL” action (as shown in the screenshot), but I haven’t found an equivalent solution in Weweb.

The challenge:

The main issue is that the “code” parameter doesn’t appear visibly in the URL bar after the OAuth redirect. In Bubble, this seems to be handled automatically, but I need a Weweb-specific solution.

What I’ve already tried:

I’ve attempted several JavaScript approaches in my workflows:

1. Using URLSearchParams to parse the query string
2. Checking both query parameters and URL fragments

However, none of these methods have successfully captured the “code” parameter consistently.

My question to you:

Has anyone successfully implemented capturing the “code” parameter after Facebook login in Weweb? How did you do it?

Specifically, I’d like to know: What is the recommended way to capture OAuth redirect parameters in Weweb?

Thank you! And here’s the link to the software: https://agencifyapp.com/app

[Broberto]

If you know the parameter’s name you can simply go and create a query variable. You can also manipulate it as you would any other variable.

Then once you have the query string parameter in your editor’s URL, you can simply go and use it as a variable anywhere. For example this is my URL:

https://editor.weweb.io/3b0d5d51-1589-4759-b376-9b1b71334244?mySecretCode=broberto_is_tha_goat