Problem with delete an event in Google Calendar node

Describe the problem/error/question

What is the error message (if any)? im facing some difficulty when it comes on to cancelling my appointment in Google Calendar. THE delete an event in Google Calendar node states that the information cannot be found or 404 not found, something like that I need help asap

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

{
“nodes”: [
{
“parameters”: {
“httpMethod”: “POST”,
“path”: “c07ee3f2-2f97-48a3-a1eb-51325b5543af”,
“responseMode”: “responseNode”,
“options”: {}
},
“type”: “n8n-nodes-base.webhook”,
“typeVersion”: 2.1,
“position”: [
96,
32
],
“id”: “1c3cf015-4ef8-4459-bd00-f375d9d78e10”,
“name”: “Webhook”,
“webhookId”: “c07ee3f2-2f97-48a3-a1eb-51325b5543af”
}
],
“connections”: {
“Webhook”: {
“main”: [

]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “1ed05c6c1071fd3e7f8855acb4846b43bfa9c1970632a2d20fc7715336613583”
}
}Information on your n8n setup

{
“nodes”: [
{
“parameters”: {
“httpMethod”: “POST”,
“path”: “c07ee3f2-2f97-48a3-a1eb-51325b5543af”,
“responseMode”: “responseNode”,
“options”: {}
},
“type”: “n8n-nodes-base.webhook”,
“typeVersion”: 2.1,
“position”: [
96,
32
],
“id”: “1c3cf015-4ef8-4459-bd00-f375d9d78e10”,
“name”: “Webhook”,
“webhookId”: “c07ee3f2-2f97-48a3-a1eb-51325b5543af”
}
],
“connections”: {
“Webhook”: {
“main”: [

]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “1ed05c6c1071fd3e7f8855acb4846b43bfa9c1970632a2d20fc7715336613583”
}
}n8n version:

  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

@shadrach_Shand

Since the JSON you shared only contains the Webhook node and not the Google Calendar node, I cannot see exactly how you’ve configured it. Please check for the following errors and how to fix them:

1)The “Event ID” is a long, unique string generated by Google (e.g., 7p2...).

  • The Mistake: Using an internal database ID or a “Meeting ID” from another system instead of the actual Google Calendar Event ID​.
  • The Fix: Ensure the value being passed into the Event ID field is exactly the one returned by a “Get Event” or “List Events” node earlier in your workflow.

2)If the event exists on a secondary or shared calendar but the node is set to your “Primary” calendar, Google will return a 404 because it’s looking for that Event ID in the wrong place.

  • The Fix: Check the Calendar field in your node. If the event isn’t on your main calendar, make sure you have selected the correct calendar from the dropdown or provided the correct Calendar ID (usually an email address).

3)If the workflow runs twice or another process has already removed the event, the second attempt to delete it will result in a 404.

  • The Fix: Check your Google Calendar trash to see if the event is already gone.

4)If you are mapping the ID from a Webhook or another node using an expression, there might be a hidden space or a newline character at the end of the string.

  • The Fix: Try using .trim() in your expression.
    Example: {{ $json.eventId.trim() }}

Hey sorry I took this long to respond , so the problem is the delete an event in google calendar node , the AI agent is having a hard time to extract event ID from ( get an event in google calendar node ) tool . So it’s not deleting the event because it cannot extract the ID . I don’t know how else to prompt it

AI Agents can be inconsistent. If this is a critical business process, don’t let the AI Agent handle the “Delete” logic internally. Instead:

  1. Create a separate “Cancellation Workflow”: This workflow should take an eventId as an input and perform the deletion.
  2. Expose this as a Tool​: Give the AI Agent a tool called cancel_appointment.
  3. Simplify the Tool’s Job​: Instead of the agent having to “Get” then “Delete,” the cancel_appointment tool should handle the lookup and deletion internally via standard n8n nodes.

The cancellation workflow pattern from kjooleng is the right direction. One thing that helps the AI agent extract the event ID reliably: when you expose the “Get Event” node as a tool, explicitly tell the AI in the tool description that the id field in the response is what it needs to pass to the delete tool — not iCalUID, not summary, just id.

Also check whether your “List Events” node output includes recurring event instances. Those have a compound ID like eventId_date (e.g., abc123_20250721T090000Z). If the agent strips or truncates that suffix, the delete will fail with a 404 even though the base event exists.

Simplest test: in a non-agent workflow, manually chain “Get Event” → “Delete Event” and confirm the id value flows correctly. Once you’ve verified that path works, the agent version should too.

Thanks for letting us know about this, We have created CV-20 as the internal dev ticket to look into it.