AI Agent "Create Event" tool not responding properly

Questions
,
1

:bullseye: What is your goal?

I´m currently trying to make my AI agent to create event in my google calendar and send me a notification when it’s done.

:thinking: What is the problem & what have you tried?

The event is created with the right name but it´s is always allocated to a wrong time.

i.e.: I give the prompt "Create a 3-hour Hold with the name Meeting on 9 Mar 2026 from 1:00–4:00 PM AEST.”. My AI agent creates the event and sends me a link to my google calendar to check it out and it is created with the right name but it´s set for 9:26pm.

I tried to make sure I set up my current location right (as I am in Melbourne, Australia) and also tried giving the prompt in diferent ways but I always get the same output.

Any ideas on how to fix it?

Thank you everyone!

3

Hey Miquel,

9:26 is a too specific time and doesn’t seem to be timezone related at all. Can you show how the agent is setup at the moment?

Also, is that prompt static? Like, it will just block off a time on your calendar at a specific date for a specific time? That’s a bit too deterministic to warrant an AI agent for, no? I’m pretty sure you can have a flow where you send this message to a slack bot or a whatsapp bot to trigger the scenario and it can be setup to block the slot for you without the need for an AI.

4

Hello,

Thank you for your response! I ended up solving it on my own.

the issue was the the time in my google calendar was set up in UTC 0 and as I´m in Australia now, I had to add a +11 at the end so it could be properly red by google calendar.

This is how it looks now that it works:

  1. create_event
  • Description: Places a calendar hold for me.
  • VERY IMPORTANT: For created events, only the name/title is required and should be filled. Other details (description, guests, location, etc.) should be left for me to handle.
  • Inputs:
{
  "title": "Hold: Strategy call with Acme",
  "start": "2026-03-09T15:00:00+11:00Z",
  "end": "2026-03-09T16:00:00+11:00Z"
}

note the +11 at the end.

Thank you!

5

This sounds like a timezone parsing issue more than a Calendar module issue.

If the agent is creating the right title but the wrong time, I’d check what timezone the AI tool is actually passing in the event payload. “1:00–4:00 PM AEST” may be getting converted incorrectly, especially if the agent, scenario, or Google Calendar connection is using a different timezone.

I’d test with a more explicit prompt like:

Create an event on 2026-03-09 from 13:00 to 16:00 Australia/Melbourne

That usually makes it much clearer for the agent. Also worth checking the scenario timezone and the Google Calendar timezone so they all match.