# About the Google Calendar category **URL:** \ **Category:** Google Calendar\ **Created:** [July 23, 2024, 6:50am UTC](https://forum.alumio.com/t/about-the-google-calendar-category/1236 "2024-07-23T06:50:50Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![o.plokha](https://forum.alumio.com/user_avatar/forum.alumio.com/o.plokha/32/337_2.png) [@o.plokha](https://forum.alumio.com/u/o.plokha)\ **Post date:** [July 23, 2024, 6:50am UTC](https://forum.alumio.com/t/about-the-google-calendar-category/1236/1 "2024-07-23T06:50:50Z")
Put topics about this connector package here. Always check the [‘How to use the Alumio connector packages’](https://forum.alumio.com/t/how-to-use-the-alumio-connector-packages/219) topic. ## Extra information System documentation: [Google Calendar API Reference](https://developers.google.com/calendar/api/guides/overview) ## Connector package documentation ### ​​Table of Contents - **1.** Setting up HTTP Client [Google](https://google.com) Calendar - **1.1** Steps - **2.** Subscribing to entities from [Google](https://google.com) Calendar - **2.1** Steps - **2.2** General concept - **3.** Publishing entity to [Google](https://google.com) Calendar - **3.1** Steps - **3.2** General concept ### 1. Setting up HTTP Client Google Calendar **1.1 Steps** 1. In the Alumio Dashboard, go to Clients → HTTP Clients. Create a new HTTP Client. 2. Select [Google](https://google.com) Calendar HTTP Client as PlatForm and click next step 3. Fill in the Base URI, Token URL, Authorize URL, Client ID, Client Secret and Scopes. (See the [Google Calendar Authentication Documentation](https://developers.google.com/calendar/api/auth) for more information) 4. Click on “Grant access to [Google](https://google.com) Calendar” and you will be redirected to [Google](https://google.com) Authentication to get the key for the client. 5. You can optionally enable logging of request to get the log of the authentication. 6. Click next step, fill the name of the HTTP Client and finally you can save the HTTP Client for use. ![image](https://alumio-forum.s3.dualstack.eu-central-1.amazonaws.com/uploads/original/2X/4/49108c11f29365914f2fcbf0d6c85e5e426ac4ff.png) ### 2. Subscribing to Entities from Google Calendar **2.1 Steps** 1. Go to Connections → Incoming and create a new incoming configuration and select “[Google](https://google.com) Calendar Subscriber” as the subscriber. 2. Select the Method that you want the subscriber to fetch the data. 3. Select the entity you want to subscribe to from [Google](https://google.com) Calendar. 4. Add any request parameters needed to subscribe to the entity. 5. Select the [Google](https://google.com) Calendar HTTP Client to use. 6. You can optionally add a transformer to transform the request parameters into something you will request from [Google](https://google.com) Calendar. 7. You can also optionally enable pagination to allow Alumio fetches paginated entities. **2.2 General Concept** We follow [Google](https://google.com) Calendar documentation on building this connector, so you can easily use the connector based on [Google Calendar API Reference](https://developers.google.com/calendar/api/guides/overview). **Entity** The entity you want to subscribe to [Google](https://google.com) Calendar. Please refer to the entities from [Google Calendar API Reference](https://developers.google.com/calendar/api/guides/overview) page. **Request Parameters** These are the parameters you can provide to get the needed entity based on the [Google Calendar API Reference](https://developers.google.com/calendar/api/guides/overview). Please look at the example below on how to fill path field when we want retrieve a Calendar by subscribing [“Calendar - Get Calendar”](https://developers.google.com/calendar/api/v3/reference/calendars/get) entity. ![image](https://alumio-forum.s3.dualstack.eu-central-1.amazonaws.com/uploads/original/2X/7/7657aeb7f10088e4f7ce4766d2dd7a51c9f3dca4.png) ![image](https://alumio-forum.s3.dualstack.eu-central-1.amazonaws.com/uploads/original/2X/5/5f0574c5a5693ce55f18abc4d6c66c690b452087.png) From the end point, we can see that we need to set the calendar id as parameters. That is why we set the “calendarId” inside the path key in the Request Parameters. Alumio will then make a request to [Google](https://google.com) Calendar with the URL `/calendars/12345` - Path is the path parameter of the url. For example the {id}. - Query is defined set of parameters attached to the end of a url. Example: `www.url.com?type=true&start=0` - Payload is the data contained within a request. **HTTP Client** The HTTP Client configuration you will use to access [Google](https://google.com) Calendar. ### 3. Publishing Entity to Google Calendar **3.1 Steps** 1. Go to Connections → Outgoing, create a new outgoing configuration and select “[Google](https://google.com) Calendar Publisher” as the publisher. 2. Select the Method that you want the publisher to perform with the data. 3. Select the [Google](https://google.com) Calendar entity you want the data to be published to. 4. You can optionally add any query data to the request on the key query. 5. You can optionally add any payload data to the request on the key payload. 6. Select the HTTP Client to use. **3.2 General Concept** Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration), though you can also add or modify payload using the Request Transformer. **Method** Currently, we support HTTP Post method and HTTP Delete method on submitting data to [Google](https://google.com) Calendar. **Entity** We support publishing to most [Google](https://google.com) Calendar endpoints. Please refer to [Google Calendar API Reference](https://developers.google.com/calendar/api/guides/overview) page. For example, we want to create a calendar. Please select “Create data using POST” as the Method and [“Calendar - Create Calendar”](https://developers.google.com/calendar/api/v3/reference/calendars/insert). ![image](https://alumio-forum.s3.dualstack.eu-central-1.amazonaws.com/uploads/original/2X/e/e4b201188c7cb92ed53f632c92a7c9a044ed639b.png) ![image](https://alumio-forum.s3.dualstack.eu-central-1.amazonaws.com/uploads/original/2X/6/6855054ac1cbaacca91aea94e31e1f7948addc7b.png) From the documentation, we can see that we need to set a body parameters. That is why we set the body parameters inside the payload key in the data. ![image](https://alumio-forum.s3.dualstack.eu-central-1.amazonaws.com/uploads/original/2X/0/0c21159cb5346bbfa3018b0f22c21ef90c79a418.png) Alumio will send an API request to [Google](https://google.com) Calendar with URL `/calendars` - Path is the path parameter of the url. For example the {id}. - Query is defined set of parameters attached to the end of a url. Example: `www.url.com?type=true&start=0` - Payload is the data contained within a request. **HTTP Client** The HTTP Client configuration you will use to access [Google](https://google.com) Calendar.