[BUG] Dynamic redirect URI generation causes mismatch in GoogleCalendarToolkit

[Tanuj-Taneja1]

Required prerequisites

• I have read the documentation https://camel-ai.github.io/camel/camel.html.
• I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
• Consider asking first in a Discussion.

What version of camel are you using?

0.2.79a0

System information

3.10.18 (main, Sep 18 2025, 19:42:01) [MSC v.1944 64 bit (AMD64)] win32
0.2.79a0

Problem description

Hi @Wendong-Fan
So I was trying to use GoogleCalendarToolkit and was getting redirect URI mismatch error during authentication, ideally the user in this case I should match the redirect uri in the app registery in google console that camel ai uses but the redirect uri generated by GoogleCalendarToolkit is not fixed and dynamically generated.

I have looked at the GoogleCalendarToolkit code and based on that this should be really easy fix we just have to set number to the port instead of 0 and it should solve the issue.
Once you approve if the issue is legit I will create a pr for it

For reference

Also on side note can we add a basic whom to tag discription in issue template
Like for issue in toolkit tag xyz and so on
I think this will make it easier for new contributors as well as maintainers

Reproducible example code

The Python snippets:

from camel.toolkits import GoogleCalendarToolkit
import dotenv
dotenv.load_dotenv()
calendar_toolkit = GoogleCalendarToolkit()
calendar_tool = calendar_toolkit.get_tools()

1. Go to Google Cloud Console and from APIs & Services create Calender api .
   2 From the created calender api get client id and client secret credential and add them to env
2. Then run the above code

Traceback

Expected behavior

No response

Additional context

No response

[fengju0213]

@Tanuj-Taneja1 thanks for opening this issue！when use our team api，it works ，i will register a new api for testing this issue！will give you feedback later.

[Wendong-Fan]

thanks @Tanuj-Taneja1 for reporting this issue!

[fengju0213]

@Tanuj-Taneja1 Thanks for reporting this issue! I was able to reproduce it — it seems that the root cause might be a mismatch between the redirect URL configured in the Google Console and the one used in CAMEL.
If you already have some ideas on this, feel free to help with a fix!

[Tanuj-Taneja1]

@Tanuj-Taneja1 Thanks for reporting this issue! I was able to reproduce it — it seems that the root cause might be a mismatch between the redirect URL configured in the Google Console and the one used in CAMEL. If you already have some ideas on this, feel free to help with a fix!
@Tanuj-Taneja1 thanks for opening this issue！when use our team api，it works ，i will register a new api for testing this issue！will give you feedback later.

Hi @fengju0213 — my initial suggestion was to use a fixed port instead of a dynamically assigned one.

However, since you mentioned that the team API works, its redirect URI likely matches what CAMEL uses internally.
I think that if the new app’s redirect URI is set to http://localhost/, the error disappears.

Can you confirm whether the working app indeed uses http://localhost/ as its redirect URI?
If so, my original issue no longer applies — we should simply update the example or other documentation to state that http://localhost/ must be used as the redirect URI.

[fengju0213]

@Tanuj-Taneja1 Thanks for reporting this issue! I was able to reproduce it — it seems that the root cause might be a mismatch between the redirect URL configured in the Google Console and the one used in CAMEL. If you already have some ideas on this, feel free to help with a fix!
@Tanuj-Taneja1 thanks for opening this issue！when use our team api，it works ，i will register a new api for testing this issue！will give you feedback later.

Hi @fengju0213 — my initial suggestion was to use a fixed port instead of a dynamically assigned one.

However, since you mentioned that the team API works, its redirect URI likely matches what CAMEL uses internally. I think that if the new app’s redirect URI is set to http://localhost/, the error disappears.

Can you confirm whether the working app indeed uses http://localhost/ as its redirect URI? If so, my original issue no longer applies — we should simply update the example or other documentation to state that http://localhost/ must be used as the redirect URI.

yeah,actually，the redirect url in google console is http://localhost/ ，after i set http://localhost/ in my own Google console，it works

[Tanuj-Taneja1]

@Tanuj-Taneja1 Thanks for reporting this issue! I was able to reproduce it — it seems that the root cause might be a mismatch between the redirect URL configured in the Google Console and the one used in CAMEL. If you already have some ideas on this, feel free to help with a fix!
@Tanuj-Taneja1 thanks for opening this issue！when use our team api，it works ，i will register a new api for testing this issue！will give you feedback later.

Hi @fengju0213 — my initial suggestion was to use a fixed port instead of a dynamically assigned one.
However, since you mentioned that the team API works, its redirect URI likely matches what CAMEL uses internally. I think that if the new app’s redirect URI is set to http://localhost/, the error disappears.
Can you confirm whether the working app indeed uses http://localhost/ as its redirect URI? If so, my original issue no longer applies — we should simply update the example or other documentation to state that http://localhost/ must be used as the redirect URI.

yeah,actually，the redirect url in google console is http://localhost/ ，after i set http://localhost/ in my own Google console，it works

Thats great, it means this is not a bug.
But I think we must add this somewhere in the docs that GoogleCalendarToolkit requires http://localhost/ as the redirect URI in Google Console.

[fengju0213]

@Tanuj-Taneja1 Thanks for reporting this issue! I was able to reproduce it — it seems that the root cause might be a mismatch between the redirect URL configured in the Google Console and the one used in CAMEL. If you already have some ideas on this, feel free to help with a fix!
@Tanuj-Taneja1 thanks for opening this issue！when use our team api，it works ，i will register a new api for testing this issue！will give you feedback later.

Hi @fengju0213 — my initial suggestion was to use a fixed port instead of a dynamically assigned one.
However, since you mentioned that the team API works, its redirect URI likely matches what CAMEL uses internally. I think that if the new app’s redirect URI is set to http://localhost/, the error disappears.
Can you confirm whether the working app indeed uses http://localhost/ as its redirect URI? If so, my original issue no longer applies — we should simply update the example or other documentation to state that http://localhost/ must be used as the redirect URI.

yeah,actually，the redirect url in google console is http://localhost/ ，after i set http://localhost/ in my own Google console，it works

Thats great, it means this is not a bug. But I think we must add this somewhere in the docs that GoogleCalendarToolkit requires http://localhost/ as the redirect URI in Google Console.

or do you think its a good idea that we set redirect url as a parameter？

[Tanuj-Taneja1]

We can do that and make the redirect_uri optional to keep it backwards compatable
But wouldnt it be an issue if a user uses some port of local host that is being already used somewhere else

[fengju0213]

We can do that and make the redirect_uri optional to keep it backwards compatable But wouldnt it be an issue if a user uses some port of local host that is being already used somewhere else

Okay, then it seems best for us to add some documentation. maybe we can add it in the example code, @Tanuj-Taneja1 If you'd like, perhaps you could help implement it.