feat(calendar): introduce EventCreatedTrigger

[Shadterra]

Closes #275.

Google Calendar EventCreated Trigger Implementation

Adds a new trigger that monitors Google Calendar for newly created events and executes workflows automatically when new events are detected.

FEATURES

• Monitor single or multiple calendars
• Filter by organizer, keywords, or event status
• Configurable polling intervals (minimum 1 minute)
• Access to complete event data
• Automatic duplicate prevention
• Rich event metadata available in workflow variables

COMPONENTS

• AbstractCalendarTrigger.java - Base class for calendar triggers with flexible scope support
• EventCreatedTrigger.java - Main trigger implementation with inline @Schema documentation
• EventCreatedTriggerTest.java - Test suite with CI compatibility

USAGE EXAMPLES

Simple example - Watch your main calendar:

id: calendar_event_monitor
namespace: company.team

tasks:
  - id: log_new_event
    type: io.kestra.plugin.core.log.Log
    message: "New event: {{ trigger.summary }} at {{ trigger.start.dateTime }}"

triggers:
  - id: watch_primary_calendar
    type: io.kestra.plugin.googleworkspace.calendar.EventCreatedTrigger
    serviceAccount: "{{ secret('GCP_SERVICE_ACCOUNT_JSON') }}"
    calendarIds:
      - primary
    interval: PT5M

Advanced example - Multiple calendars with filtering:

id: team_meeting_monitor
namespace: company.team

tasks:
  - id: notify_slack
    type: io.kestra.plugin.notifications.slack.SlackIncomingWebhook
    url: "{{ secret('SLACK_WEBHOOK') }}"
    payload: |
      {
        "text": "New meeting: {{ trigger.summary }}\nOrganizer: {{ trigger.organizer.displayName }}\nTime: {{ trigger.start.dateTime }}"
      }

triggers:
  - id: watch_team_meetings
    type: io.kestra.plugin.googleworkspace.calendar.EventCreatedTrigger
    serviceAccount: "{{ secret('GCP_SERVICE_ACCOUNT_JSON') }}"
    calendarIds:
      - "[email protected]"
      - "[email protected]"
    searchQuery: "meeting"
    organizerEmail: "[email protected]"
    eventStatus: CONFIRMED
    interval: PT10M

SETUP REQUIREMENTS

• Google Cloud project with Calendar API enabled
• Service account with calendar read permissions (scope: https://www.googleapis.com/auth/calendar)
• Service account JSON key stored as Kestra secret
• Share target calendars with the service account's email address

AVAILABLE EVENT DATA

When the trigger fires, your workflow gets access to complete event information including:
• id, summary, description, location, status, htmlLink
• created and updated timestamps
• start/end times with timezone information
• organizer details (email, displayName)
• visibility and eventType

Access this data in workflows using {{ trigger.summary }}, {{ trigger.organizer.email }}, etc.

[MilosPaunovic]

Just a small note for the future, if you could use GitHub Keywords when opening PRs to connect it to the proper issue (to automate the entire process a bit more), it would be super helpful to us. You can read a bit more about it here (I've added closing keyword for this particular issue).

[Shadterra]

When can i expect feedback ?

[Malaydewangan09]

Hey @Shadterra, thanks for your contribution, we'll review this shortly!

[Shadterra]

Damn. Hmm I'm not sure i understand the problem why the checks have failed. Would you please enlighten me ?

[fdelbrayelle]

Checks failed because you need a review approval @Shadterra :)

[fdelbrayelle]

Hello @Shadterra 👋 Did you have time to address the feedback please 🙏 ?

[Shadterra]

Sorry i will do it tomorrow. I was busy with school these last 2 days and i didn't have time

[Shadterra]

I fixed all things pointed out in review 👀

[Malaydewangan09]

Hey @Shadterra 👋, thanks for the contribution!

• Could you please, mark as "Resolved" the discussions where you did the changes.
• I see most of the tests dont actually run maybe you could take some ref from here, on how we test Triggers?
• Also, would be great if you could provide some QA/test screenshots of the plugin using UI.

[Shadterra]

Resolved discussions and i updated tests.

[Malaydewangan09]

Hey @Shadterra, it seems CI is failing could you please have a look at it? Thanks!

[Shadterra]

Hello @Malaydewangan09 , I don't know what the problem is. And all errors i see on github are: no JSON input found. Could you send me your CI output ?

[Shadterra]

#286 (comment)

i just found that have similar errors like here but i dont think i can do anything about it

[fdelbrayelle]

Hi @Shadterra 👋
The "no JSON input found" is normal because you don't have the service account on your fork repository.
This error will disappear once merged on the main CI.

[Shadterra]

Hi @fdelbrayelle
I see you have closed the issue
So is everything good and does it work as intended ?