Hi, I’m using connectedAccounts.initiate(userId, configId) where configId is created in Composio using my own Google client ID & secret. However, during the OAuth flow, the consent screen still shows “composio.dev wants to access your Google Account” (see attached screenshots), including “This will allow composio.dev to…”. Can you clarify: Why the consent screen branding is still composio.dev even when a custom client ID is configured? Is there a supported way today to have the consent screen show my app name (for Google verification), or is this flow always tied to Composio’s OAuth app? Just want to understand the current limitation vs configuration issue. Thanks! https://cdn.discordapp.com/attachments/1459599569984946461/1459599570433605724/image.png?ex=697a4707&is=6978f587&hm=b1335d8f39a78b8fb99103533af17bcdae4f3dad545ca5ae20e52c4e643ca8fe& https://cdn.discordapp.com/attachments/1459599569984946461/1459599570810966131/Screenshot_2026-01-10_224359.PNG?ex=697a4707&is=6978f587&hm=5db06456b5d6c068f3dd98c2b7eeecdbb57accd3715af5ed867c8d2a810a8297&

Hey @adityasingh321, "*using my own Google client ID & secret*"— you are halfway there! for Google toolkits you'll need to white label you auth consent screen by configuring your own redirectUri. You can refer this doc: https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen. Let me know if you need any help.

@Uday Thanks for the explanation. Just to confirm my understanding: Is the “white-labeling” doc suggesting that we create a custom redirect endpoint on our own domain (e.g. yourdomain.com/api/composio-redirect) which then 302-redirects to Composio’s callback (backend.composio.dev/...)? If we do this, will it also remove composio.dev from the OAuth consent screen, or does it only improve the redirect-URL UX while the consent screen app name remains the same? Basically want to confirm whether consent-screen branding removal is supported today, or if this is only redirect-level white-labeling.

@adityasingh321, Yes, you'll need to do 302 which redirects to our redirectUri to change the auth consent screen. As it is consent screen branding, make sure you use your own auth app credentials.

https://backend.composio.dev/api/v3/toolkits/auth/callback Need to redirect here with all the query params intact? Is that what you mean?

You can use this snippet:

from fastapi import FastAPI, Request
from fastapi.responses import RedirectResponse
from composio import Composio

# Create a FastAPI app
app = FastAPI()
# Create a Composio client
composio = Composio(api_key="<api-key>")

@app.get("/")
async def authorize_app(request: Request):

    composio_endpoint = 'https://backend.composio.dev/api/v3/toolkits/auth/callback'
    query_params = request.query_params
    redirect_url = f"{composio_endpoint}?{query_params}"
    
    return RedirectResponse(url=redirect_url, status_code=302)

if __name__ == "__main__":
    import uvicorn
    uvicorn.run(app, host="0.0.0.0", port=8002)

Thanks a lot for the clarification, it solved the issue and saved us a lot of time. Appreciate the help! 🙌

Awesome! We'd love to learn more about how you're using Composio and hear your feedback on how we can improve. Would you be open to a quick 15-minute chat with us? https://calendly.com/palash-composio/15-minute-meeting-support