Google Calendar Update Event succeeds but no changes are applied (n8n + AI Agent)

Hi everyone,

I’m building an AI-driven scheduling agent in n8n that manages delivery events using Google Calendar (create, consult, update, delete).

The workflow is working correctly for:

  • Creating events

  • Finding events (I can retrieve the correct event by ID)

However, I’m running into a consistent issue with updating events.

The problem

The Update Event node executes successfully (status = success), but no changes are actually applied to the event.

For example:

  • I try to change the event date or the event title (summary).

  • The workflow finds the correct event.

  • The Update Event node runs without errors.

  • The event in Google Calendar remains unchanged.

What I’ve already confirmed

  • I am passing the correct Event ID to the Update Event node.

  • The node execution shows Success.

  • The issue happens even when updating simple fields like summary (event title).

  • Create and Delete operations work as expected.

Observation

When I inspect the input of the Update Event node, it often contains:

  • eventId

  • session / agent metadata

…but no explicit updated fields (like summary, start, end, etc.), which makes me suspect the update is effectively a no-op.

My questions

  1. Does the Google Calendar → Update Event node require all changed fields to be explicitly passed, even if only one field is being updated?

  2. If a field is omitted, does the API silently keep the original value?

  3. Is there a known best practice for updating events when the data comes from an AI agent (dynamic fields)?

  4. Is it recommended to use a Set / Edit Fields node before Update Event to ensure updated values are always present?

Any insight or real-world examples would be greatly appreciated.
Thanks in advance!

The issue might be related to how the update fields are being passed to the Google Calendar node. Ensure you’re explicitly setting the fields you want to update (like `summary`, `start`, `end`) in the node’s parameters. Also, verify that the `Send Update Notifications` option is enabled if you want changes to be reflected immediately.

If the problem persists, try testing with a simpler workflow that only updates one field at a time to isolate the issue. Share your workflow JSON if you need further help!