Google Calendar Source
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Stable"
Receive event data from Google Calendar.
Configuration Options
The following table summarizes the configuration options available for the google-calendar-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
Access Token | Required The OAuth 2 access token for the Google Calendar application. This token typically expires after an hour. For long term usage, set the | string | |||
Application name | Required The Google Calendar application name. | string | |||
Calendar ID | Required The calendar ID to use as the source of event data. | string | |||
Client Id | Required The Client ID of the Google Calendar application. | string | |||
Client Secret | Required The Client secret of the Google Calendar application. | string | |||
Index | Required An index for the Google Calendar endpoint. | string | |||
Refresh Token | Required The OAuth 2 refresh token for the Google Calendar application. The Google Calendar component can obtain a new | string | |||
Consume from now | Specfies to consume events in the calendar from now on. | boolean | true | ||
Delay | The number of milliseconds before the next poll. | integer | 500 | ||
Sync Flow | Specifies to sync events for incremental synchronization. | boolean | false |
Dependencies
At runtime, the google-calendar-source
Kamelet relies upon the presence of the following dependencies:
-
camel:jackson
-
camel:google-calendar
-
camel:kamelet
Camel JBang usage
Prerequisites
-
You’ve installed JBang.
-
You have executed the following command:
jbang app install camel@apache/camel
Supposing you have a file named route.yaml with this content:
- route:
from:
uri: "kamelet:google-calendar-source"
parameters:
.
.
.
steps:
- to:
uri: "kamelet:log-sink"
You can now run it directly through the following command
camel run route.yaml