Google Calendar trigger not fetching test events šŸ˜•

Questions
1

Describe the problem/error/question

The Google Calendar trigger for Update or Created events is not fetching test events correctly. Sometimes no output at all.

Itā€™s the first node of the workflow. I havenā€™t even built anything yet.

When I change to another calendar, I can get some events from YEARS ago. Like 2014 and 2019.

Iā€™ve already checked the credentials and everything seems to be authorized. I can even create events and update them.

What is the error message (if any)?

ERROR: No data with the current filter could be found
{

"message": "No data with the current filter could be found"

}

NodeApiError: No data with the current filter could be found
    at Object.poll (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Calendar/GoogleCalendarTrigger.node.js:188:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:664:32)
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:631:53

image
image1882Ɨ779 47.7 KB

Information on your n8n setup

  • n8n version:1.4.1
  • Database (default: SQLite)
  • Running n8n via: Docker
  • Operating system: Ubuntu
4

Hi @solomon, I am very sorry for the trouble. Can you confirm if you own this calendar and how exactly youā€™ve created this calendar (e.g. is this a freshly created regular calendar, a calendar share by someone else, a calendar created through URL import)?

And are you also seeing problems for production executions?

5

This calendar was created by me. Itā€™s brand new and I own it.

I donā€™t know about the production executions because I couldnā€™t build the workflow. Without a test event to examine the data structure, itā€™s currently beyond my capabilities.

6

Perhaps you can simply activate your workflow, then create a new even in your Google Calendar and once the polling interval has passed check your execution list to see if the execution was successful? Your workflow doesnā€™t need to do anything productive just yet, having the trigger node by itself should be enough :slight_smile:

I am just trying to understand if this problem is limited to manual executions or also affecting production executions for you.

7

Got it!

It works:

image
image287Ɨ248 5.8 KB

The event was retrieved successfully

8

Great news! In this case Iā€™d suggest you do the following:

  1. Copy the JSON data from your production execution
  2. Open the workflow for editing, then click on ā€œinsert test dataā€ on your trigger node:
    image
    image1479Ɨ871 36.1 KB
  3. Paste the JSON data copied in step 1 and click Save

Afterwards you should have testing data for your manual executions, even if n8n itself is not getting any test data from Google during the manual executions.

Hope this helps :slight_smile:

9

It sure does! Thank you.

But about the test eventā€¦ is it a bug thatā€™s gonna be addressed or thereā€™s nothing that can be done?

10

Hm, I would love to see this fixed, but wasnā€™t able to reproduce the problem so far. As soon as the test calendars I have created had at least one event, I could fetch this test event through n8n :frowning: