WorqHat
Utility

Calendar Fetch Events

Category
Utility
Node Type
Calendar Integration

Overview

The Calendar Fetch Events node retrieves a list of events from a connected calendar within a specific date range. It allows you to automatically collect event data such as titles, times, participants, meeting links, and organizers.

This node is ideal for building workflows that depend on upcoming or past events — for example, generating daily reports, summarizing meetings, or syncing event details with external systems like CRMs or chat tools.

Description

Retrieve calendar data.

The Calendar Fetch Events node connects to your calendar service and pulls event information based on your defined criteria.

Fetch by Range

Get all events within a specific start and end date.

Sync Data

Retrieve event details to sync with other tools.

Once executed, this node returns a structured list of events, including details such as event titles, descriptions, locations, participants, meeting links, and creation timestamps.

Input Parameters

The Calendar Fetch Events node requires the following parameters to define which events to retrieve.

calendarIdstringRequired
The unique identifier of the calendar (e.g., 'primary').
Example
"primary"
startDatestringRequired
ISO-formatted start date and time.
Example
"2025-11-01T00:00:00Z"
endDatestringRequired
ISO-formatted end date and time.
Example
"2025-11-07T23:59:59Z"

Output Parameters

The node returns a list of events matching the criteria.

eventsarrayOptional
A list of all retrieved events.
totalEventsnumberOptional
The total count of events retrieved.
Example
5
timezonestringOptional
The time zone of the calendar.
Example
"Asia/Kolkata"
Event Object Structure

Each item in the events array contains:

  • eventId, title, description
  • startDate, endDate
  • location, meetLink
  • organizer, attendees

Output Type

Output Type: JSON

The node returns data in a structured JSON format, making it easy to use in downstream nodes for filtering, summaries, or reporting.

Example Usage

Example 1: Fetch Events for the Current Week

Get a weekly schedule.

{  "calendarId": "primary",  "startDate": "2025-11-01T00:00:00Z",  "endDate": "2025-11-07T23:59:59Z"}
{  "totalEvents": 2,  "timezone": "Asia/Kolkata",  "events": [    {      "eventId": "evt_23456",      "title": "Team Standup",      "startDate": "2025-11-02T09:00:00Z",      "meetLink": "https://meet.google.com/..."    },    {      "eventId": "evt_23457",      "title": "Product Review",      "startDate": "2025-11-04T13:00:00Z"    }  ]}

Example 2: Fetch Specific Calendar

Get events from a marketing calendar.

{  "calendarId": "marketing_team",  "startDate": "2025-11-10T00:00:00Z",  "endDate": "2025-11-15T23:59:59Z"}
{  "totalEvents": 1,  "events": [    {      "title": "Campaign Kickoff",      "organizer": "lead@company.com",      "location": "Conference Room 3"    }  ]}

How to Use in a No-Code Workflow

1

Add the Node

Add the Calendar Fetch Events node to your workflow.

2

Connect Trigger

Link a trigger (e.g., Time Trigger) to decide when to fetch events (e.g., every morning).

3

Configure Range

Set the calendarId, startDate, and endDate.

4

Process Data

Use the events output in downstream nodes (e.g., send a summary to Slack).

5

Run Workflow

Run a test to verify the fetched data.

Best Practices

  • Use valid ISO 8601 date formats.
  • Keep the date range short (e.g., one week) for better performance.
  • Use the timezone output to align events across regions.

Do / Don’t

Do
  • ✔️ Use this node to generate daily summaries.
  • ✔️ Filter the output array if you only need specific events.
  • ✔️ Refresh calendar credentials regularly.
Don’t
  • ❌ Don’t fetch huge date ranges (e.g., 10 years) at once.
  • ❌ Don’t ignore the time zone; it can cause scheduling confusion.
  • ❌ Don’t assume the events list is sorted; sort it if needed.

Common Errors

Invalid calendarIdErrorOptional
The specified calendar ID is incorrect or inaccessible.
Invalid date formatErrorOptional
Dates are not in ISO 8601 format.
No events foundWarningOptional
The date range or calendar is empty.

Example Workflow Integration

Use Case 1: Daily Meeting Summary

Post a summary of today's meetings to Slack.

  1. Time Trigger: Runs every morning at 8 AM.
  2. Calendar Fetch Events: Retrieves meetings for today.
  3. Text Generation: Summarizes the list.
  4. Slack Message: Sends the summary.

Workflow Data Flow:

{{calendarFetchEvents.events}} →  {{textGeneration.prompt}}
{{textGeneration.content}}     →  {{slackMessage.message}}