Why does my calendar booking agent execute four times instead of once?

It sounds like your workflow is processing multiple items—each triggering the Google Calendar event creation node. In n8n a node (such as the Google Calendar node) will execute for every incoming item. If your chat agent returns four items (for example, one for each part of your interpretation of “book an event tomorrow between 11am–12pm”), then the subsequent node will run four times and book the same event four times.

Here are a few things to check:

1. Input Items: Inspect the output of the node before your Google Calendar node (e.g. your parsing or chatbot node). If that node returns an array with four items, then n8n will process each one individually. You may need to adjust your logic if you only want one event to be created.

2. Workflow Structure: Verify if you have inadvertently duplicated a trigger or if the command is being sent multiple times. For instance, if a trigger node or webhook receives the command more than once, that would start several workflow executions.

3. Item Consolidation: If the multiple items are not intentional, consider using a “Set” or “Merge” node to consolidate or filter out duplicate items before they reach the Google Calendar node.

Reviewing the execution data in n8n’s workflow execution view should help identify which node is passing multiple items forward. Adjusting your workflow to handle or reduce incoming items should resolve the issue of duplicate event creation.

Hope this helps you narrow down the cause!