Google calendar node malfunction

I’ve been debugging this for hours now without success. I’ve checked through the docs, used GPT, YouTube, etc, and can’t seem to get it right. I keep getting “Could not get parameter” with no further explanation of what the error is about. All the variables are specified correctly by the AI agent to the left in ISO 8601 format. This should be the easiest thing in the world to get right, but I’ve got no idea what I’m missing. I’ve even used the built in chatbot inside n8n, and the only solutions it provides are solutions I’ve already implemented.

Hello @George_Tasan, how are you?

Could you provide the workflow code so I can better understand the flow?

did you used as tool or as node the Calendar node when you have connected with the agent?

You mentioned you’ve tried some things already, but have you tried defining the Start and End fields manually, not through the :sparkles: button?

{{$fromAI('Start', 'The start timestamp for the event')}}
{{$fromAI('End', 'The end timestamp for the event')}}

Sure thanks, here’s the JSON file https://drive.google.com/file/d/1OSXqQSpni9H6i89knN1c9tbuKv1f75gZ/view?usp=sharing

It’s a tool connected to the AI agent node

Yeah, and it’s even in the correct ISO 8601 format

Thank you for the workflow. I fixed it on accident:

  1. Went into the bookAppointment tool
  2. Fixed credentials and email (calendar)
  3. Removed the :sparkles: option everywhere, so {{$fromAI}} is used instead
  4. Clicked Execute on the tool
  5. Provided example values and the meeting was booked.
  6. From then on the AI had no issues using it.
  7. I also simplified the AI prompts a bit

Then, I noticed the AI outputs a string and not a JSON (could be an issue on my end as I use Gemini). I did that by switching the AI node to Continue on Error in the settings. I replace spaces in the Structured Output node with underscores, just as the AI outputs them (best practice in naming variables is to not use spaces). The AI seems to like that and started outputting everything normally. I also recommend updating N8N as your AI node is a few versions behind the latest one.

I genuinely don’t even know anymore, I’ve copy + pasted your exact instructions and I’m still having issues. Truly makes no sense. I’ve used n8n for a few months now and I’ve never stumbled upon something like this. It’s not that it’s difficult to solve, it’s that I don’t even know what’s causing it in the first place because it makes no sense to me. Everything is correct on my end in terms of settings and wiring.




Hey, I updated the flow a few times - could you grab the latest version? Sorry didn’t realize you are online :slight_smile:

Also, when you run just the tool, with the provided example values in the popup, do you still get the same error?

Tried running the tool on its own as well. Do I have to adjust some settings inside calendar.google.com?

Thanks for confirming, but I still need to know if you get the exact same error when you just run the tool itself? Or the error changes?

For now I don’t think you need to make changes in the Calendar, no.

Same exact error, “Could not get parameter”. The error message makes no sense either, doesn’t tell me anything at all.

What’s your current version of n8n? Are you ok with trying to update? I didn’t ask earlier, but are you self hosted (and how)?

I’m using the cloud version. Checking for new updates on the daily.

Sorry for the delay, could you please try the following so we can validate if the current workflow or node is somehow corrupted:

  1. Start a fresh workflow with Manual Trigger
  2. Add an AI Agent
  3. Add a calendar tool
  4. Configure the tool from scratch to do the same as the original one (again, use the {{$fromAI}} functions)
  5. Try to open the tool, run just the tool, provide sample values.
  6. If successful, try to move over the AI Prompt as well
  7. Go to your old workflow’s Webhook node → copy the JSON data from the webhook output
  8. Go to the new workflow → open the manual trigger → click the pen (top-right) → paste JSON
  9. Try to trigger the workflow with this sample data

The order of these steps is important. If you have the time to do those and let me know if anything breaks and after which step exactly, we could gain some more insight or hopefully fix it.