Google Calendar Connector for Informatica
In this article you will learn how to integrate Using Google Calendar Connector you will be able to connect, read, and write data from within Informatica. Follow the steps below to see how we would accomplish that. The driver mentioned above is part of ODBC PowerPack which is a collection of high-performance Drivers for various API data source (i.e. REST API, JSON, XML, CSV, Amazon S3 and many more). Using familiar SQL query language you can make live connections and read/write data from API sources or JSON / XML / CSV Files inside SQL Server (T-SQL) or your favorite Reporting (i.e. Power BI, Tableau, Qlik, SSRS, MicroStrategy, Excel, MS Access), ETL Tools (i.e. Informatica, Talend, Pentaho, SSIS). You can also call our drivers from programming languages such as JAVA, C#, Python, PowerShell etc. If you are new to ODBC and ZappySys ODBC PowerPack then check the following links to get started. |
Connect to Google Calendar in other apps
|
How to read API data in Informatica (Call JSON / XML SOAP Service)
How to write data to API (POST) in Informatica (Call JSON / XML SOAP Service)
Introduction
JSON / REST API is becoming more and more popular each day as everyone embrace cloud-centric services. This article is primarily focused on Informatica users who want to access Google Calendar data or may be other API Integration in Informatica. However many tips and techniques described in this article will help you to understand how to integrate Google Calendar / XML SOAP / JSON / REST API in other ETL / Reporting apps such as Tableau, Power BI, SSRS, Talend, Excel and many more.
After going through this article you will learn how to Read Google Calendar / JSON / REST API data in Informatica and understand the concept of JSON / REST API. We will go through many screenshots and step-by-step examples to demonstrate Google Calendar or REST API integration in Informatica PowerCenter.
XML / JSON can come from a local file or REST API service (internal or public) so we will include both examples in this article (i.e. Read JSON files in Informatica, Import REST API in Informatica). So let’s get started. Next article will focus on how to write data to API in Informatica (POST / PUT data)
Requirements
This article assumes that you have full filled following basic requirements.
- Download Install ZappySys ODBC PowerPack (API Driver for Google Calendar included)
- Install Informatica PowerCenter Client Tools (e.g. Workflow and Mapping Designers)
- Access to a Relational database such as SQL Server (or use any of your choice e.g. Oracle, MySQL, DB2 ). If nothing available then you can use flat file target.
High level Steps for Import Google Calendar data using Informatica (Read Google Calendar API data)
Before we dive deep to learn how to load Google Calendar data in Informatica (i.e. Google Calendar to SQL Table), Here the summary of high-level steps you need to perform to import Google Calendar in Informatica (same steps for Import JSON / XML / REST API).
- Download and Install ZappySys API Driver (for connecting to Google Calendar)
- Create ODBC DSN using ZappySys API driver and choose Google Calendar Connector during Wizard
- Create Relational > ODBC Connection in Informatica Workflow designer (Point to DSN we created in the previous step)
- Import Google Calendar Source Definition in the Informatica Mapping Designer > Sources Tab
- Import Target Table Definition in the Informatica Mapping Designer > Targets Tab
- Create source to target mapping in Mappings tab
- Save mapping (name m_API_to_SQL_Load )
- Create Session using the mapping we created in the previous step
-
Save Workflow and execute to load Google Calendar data into SQL Table. Verify your data and log.
Loading Google Calendar data to SQL Table in Informatica (Import REST API or JSON Files)
Video Tutorial – Read any API / JSON data in Informatica (Load Google Calendar to SQL Table)
Below video is not about Google Calendar API but its showing API access in general (for any API). By watching following ~5 min video can learn steps listed in this article to load JSON API data into SQL Server Table using ZappySys JSON Driver. You can go though full article to learn many useful details not covered in this video.
Getting Started – Import Google Calendar to SQL Server in Informatica
Now let’s get started. For example purpose, we will read data from Google Calendar and load data into SQL Server Table using Informatica Workflow.
Create ODBC Data Source (DSN) based on ZappySys API Driver
Step-by-step instructions
To get data from Google Calendar using Informatica we first need to create a DSN (Data Source) which will access data from Google Calendar. We will later be able to read data using Informatica. Perform these steps:
-
Install ZappySys ODBC PowerPack.
-
Open ODBC Data Sources (x64):
-
Create a User Data Source (User DSN) based on ZappySys API Driver
ZappySys API Driver
You should create a System DSN (instead of a User DSN) if the client application is launched under a Windows System Account, e.g. as a Windows Service. If the client application is 32-bit (x86) running with a System DSN, use ODBC Data Sources (32-bit) instead of the 64-bit version. -
When the Configuration window appears give your data source a name if you haven't done that already, then select "Google Calendar" from the list of Popular Connectors. If "Google Calendar" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:
GoogleCalendarDSNGoogle Calendar
-
Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.
Steps to get Google Calendar Credentials
To make this work you will have to create an OAuth application. To register an App, perform the following steps (Detailed steps found in the help link at the end):
- Go to Google API Console
- From the Project Dropdown (usually found at the top bar) click Select Project
- On Project Propup click CREATE PROJECT
- Once project is created you can click Select Project to switch the context (You can click on Notification link or Choose from Top Dropdown)
- Click ENABLE APIS AND SERVICES
- Now we need to enable Google Drive API.
- Search Google Drive API. Select and click ENABLE
- Go to back to main screen of Google API Console
- Click OAuth Concent Screen Tab. Enter necessary details and Save.
- Click Credentials Tab
- Click CREATE CREDENTIALS (some where in topbar) and select OAuth Client ID option.
- When prompted Select Application Type as Desktop App and click Create to receive your ClientID and Secret. Later on you can use this information now to configure Connection with UseCustomApp=true.
- Go to OAuth Consent Screen tab. Under Publishing Status click PUBLISH APP to ensure your refresh token doesnt expire often. If you planning to use App for Private use then do not have to worry about Verification Status after Publish.
Fill in all required parameters and set optional parameters if needed:
GoogleCalendarDSNGoogle CalendarUser Account [OAuth]https://www.googleapis.com/calendar/v3/Required Parameters UseCustomApp Fill in the parameter... Optional Parameters ClientId Fill in the parameter... ClientSecret Fill in the parameter... Scope Fill in the parameter... RetryMode Fill in the parameter... RetryStatusCodeList Fill in the parameter... RetryCountMax Fill in the parameter... RetryMultiplyWaitTime Fill in the parameter... Redirect URL (Only for Web App) Fill in the parameter... 
Steps to get Google Calendar Credentials
Use these steps to authenticate as service account rather than Google / GSuite User. Learn more about service account here Basically to call Google API as Service account we need to perform following steps listed in 3 sections (Detailed steps found in the help link at the end)Create Project
First thing is create a Project so we can call Google API. Skip this section if you already have Project (Go to next section)- Go to Google API Console
- From the Project Dropdown (usually found at the top bar) click Select Project
- On Project Propup click CREATE PROJECT
- Once project is created you can click Select Project to switch the context (You can click on Notification link or Choose from Top Dropdown)
- Click ENABLE APIS AND SERVICES
- Now we need to enable API - Google Calendar API
- Search Drive. Select and click ENABLE
Create Service Account
Once Project is created and APIs are enabled we can now create a service account under that project. Service account has its ID which looks like some email ID (not to confuse with Google /Gmail email ID)- Go to Create Service Account
- From the Project Dropdown (usually found at the top bar) click Select Project
- Enter Service account name and Service account description
- For Role, do not select anything for now and Click Continue and then click Done. Next we will create Key.
Create Key
Once service account is created we need to create key file (i.e. credentials).- In the Cloud Console, click the email address for the service account that you created.
- Click Keys.
- Click Add key, then click Create new key.
- Click Create and select P12 format. A P12 key file is downloaded to your computer. We will use this file in our API connection.
- Click Close.
- Now you may use downloaded *.p12 key file as secret file and Service Account Email as Client ID (e.g. some-service-account-name@your-project-id.iam.gserviceaccount.com ).
Add Permission
Now last thing is give read/write permission to Service Account for Calendar you like to access using API.- Copy the email address of your service account we created in previous step (its usually like this some-service-account-name@your-project-id.iam.gserviceaccount.com).
- Login to https://calendar.google.com/calendar and make sure you see the calendar you like to access via API
- On the left, find the "My calendars" section. To expand it, click the Down arrow Down arrow.
- Hover over the calendar you want to share, and click 3 dots next to it. Click "Settings and sharing".
- Find "Share with specific people", Click Add people button and enter the service account email id we obtained in the previous section.
- Select correct permission you like to give for sharing. Click Send button to share. Thats it now we can read / write Calendar Events using Service account approach.
- For more information check this link https://support.google.com/calendar/answer/37082?hl=en
Fill in all required parameters and set optional parameters if needed:
GoogleCalendarDSNGoogle CalendarService Account (Using Private Key File) [OAuth]https://www.googleapis.com/calendar/v3/Required Parameters Service Account Email Fill in the parameter... Service Account Private Key Path (i.e. *.p12) Fill in the parameter... Optional Parameters Scope Fill in the parameter... RetryMode Fill in the parameter... RetryStatusCodeList Fill in the parameter... RetryCountMax Fill in the parameter... RetryMultiplyWaitTime Fill in the parameter...
-
Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
-
Click OK to finish creating the data source.
Video instructions
Create Connection in Informatica Workflow Designer
Once you create DSN using API Driver our next step is to define a connection for Google Calendar source in Informatica PowerCenter Workflow designer.
- Open Workflow designer [W] icon
-
Goto Connections > Relational
Create a new connection for Google Calendar in Informatica
-
Click New and select ODBC
Select ODBC connection type in Informatica (Using ZappySys API ODBC DSN)
- Now on the ODBC connection setup enter connection name, some fake userid / password (this is a required field but its ignored by JSON Driver)
-
In the Connection String field enter the exact same name of DSN (Open ODBC Data Sources UI to confirm)
Configure Google Calendar connection in Informatica for REST API – Using ZappySys API Driver
- Click OK to close the connection properties.
That’s it. Now we ready to move to next step (define source and target in Mapping Designer).
Import Google Calendar Source Definition in Informatica Mapping Designer
Now let’s look at steps to import Google Calendar table definition.
- Open Informatica Mapping Designer (Click [D] icon)
- Click on Source Icon to switch to Sources designer
-
From the top menu > Click on Sources > Import from Database …
Import Google Calendar Source definition in Informatica Mapping Designer (JSON file or REST API)
- Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)
-
Click Connect button to get a list of tables. Any array node is listed as a table. Also, you will see array node with parent columns (e.g. value_with_parent). You may get some warning like below but they are harmless so just ignore by clicking OK.
DLL name entry missing from C:\Informatica\PowerCenter8.6.1\client\bin\powrmart.ini Section = ODBCDLL Entry = ZappySys JSON Driver
—————————————————-
Using EXTODBC.DLL to support ZappySys JSON Driver. For native support of ZappySys JSON Driver make an entry in the .ini file.
Select Google Calendar Source Table in Informatica Mapping Designer (JSON file or REST API)
- Select Table you wish to get (You can filter rows by custom SQL query. We will see later in this article how to do)
-
Optionally once table structure is imported you can rename it
Rename imported table definition in Informatica Source Designer
- That’s it, we are now ready to perform similar steps to import Target table structure in the next section.
Import SQL Server Target Definition in Informatica Mapping Designer
Now let’s look at steps to import Target table definition (very similar to the previous section, the only difference is this time we will select DSN which points to SQL Server or any other Target Server).
Now lets look at steps to import target table definition in Informatica mapping designer.
- In the Mapping Designer, Click on Target Icon to switch to Target designer
- From the top menu > Click on Targets > Import from Database …
-
Select DSN for your Target server (if DSN doesn’t exist then create one by opening ODBC Sources just like we created one for JSON API source (see the previous section about creating DSN).
Import target Table Definition in informatica
- Enter your userid , password and Schema name and click Connect to see tables
-
Select Table name to and click OK import definition.
Import Target SQL Table Definition in Informatica – Select table from the list
Create Source to Target Mapping in Informatica (Import JSON to SQL Server)
Once you have imported source and target table definition, we can create mapping and transformation to load data from JSON to SQL Table.
- First open Mapping Designer (Click [D] icon)
- Drag JSON Source from sources folder
- Drag SQL Table from Targets folder
-
Map desired columns from Source to target
Define Source to Target mapping for Google Calendar to SQL Table load in Informatica
-
For certain columns you may have to do datatype conversion. For example to convert OrderDate form nstring to DataTime you have to use Expression Transform like below and map it to target. In below example, our JSON has date format (e.g. 2018-01-31 12:00:00 AM ). To import this to DateTime field in SQL server we need to convert it using TO_DATE function. Use double quotes around T to make this format working.
TO_DATE(OrderDate,'YYYY-MM-DD H12:MI:SS AM') --For ISO use below way TO_DATE(OrderDate,'YYYY-MM-DD"T"HH24:MI:SS')
Informatica Google Calendar to SQL Table Mapping – Datatype conversion (nstring to datetime)
- Once you done with mapping save your mapping and name it (i.e. m_Api_To_SQL)
- Now lets move to next section to create workflow.
Create Workflow and Session in Informatica
Now the final step is to create a new workflow. Perform following steps to create workflow which with a session task to import JSON data into SQL table.
- Open workflow designer by click [W] icon.
-
Launch new workflow creation wizard by click Workflow top menu > Wizard
name your workflow (e.g. wf_Api_Tp_Sql_Table_Import)
Creating Informatica Workflow – Wizard UI (Import Google Calendar data to SQL Table)
- Finish the wizard and double-click the Session to edit some default properties.
-
First change Error settings so we fail session on error (By default its always green)
Fail Informatica Session on error (Google Calendar data to SQL Load)
-
Select JSON connection for Source
Select Google Calendar Source Connection in Informatica – Load Google Calendar data to SQL Table
-
Change default Source query if needed. You can pass parameters to this query to make it dynamic.
Modify Google Calendar Source SQL query – Pass parameters, change URL, set filter etc
-
Select Target connection of SQL Target Table
Select SQL Target Connection in Informatica – Load Google Calendar data to SQL Table
- Save workflow
- That’s it. We ready to run our first workflow to load JSON data to SQL.
Execute Workflow and Validate Log in Informatica
Now once you are done with your workflow, execute it to see the log.
Loading Google Calendar data to SQL Table in Informatica (Import REST API or JSON Files)
POST data to Google Calendar in Informatica
There will be a time when you like to send Source data to REST API or SOAP Web Service. You can use below Query for example. For detailed explanation on how to POST data in Informatica check this article.
Video Tutorial – How to POST data to REST API in Informatica
Here is detailed step by step video on REST API POST in informatica PowerCenter
Keywords
how to import Google Calendar in informatica | how to read Google Calendar data in informatica powercenter | how to test json from informatica | how to use Google Calendar data as source in informatica power center | how to connect Google Calendar in informatica 10 | informatica how to import data from Google Calendar | informatica jtx to import Google Calendar (use of java transformation) | informatica plugin for restful api using json | informatica power center and Google Calendar support | informatica read Google Calendar | informatica rest api | informatica Google Calendar connector | json parser import informatica
Advanced topics
Create Custom Stored Procedure in ZappySys Driver
You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.
Steps to create Custom Stored Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
-
Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
-
Enter the desired Procedure name and click on OK:
-
Select the created Stored Procedure and write the your desired stored procedure and Save it and it will create the custom stored procedure in the ZappySys Driver:
Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
CREATE PROCEDURE [usp_get_orders] @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>' AS SELECT * FROM Orders where OrderDate >= '<@fromdate>';
-
That's it now go to Preview Tab and Execute your Stored Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
Exec usp_get_orders '1996-01-01';
-
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC usp_get_orders @fromdate=''1996-07-30''')
-
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.
Create Custom Virtual Table in ZappySys Driver
ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.
If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.
Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.
-
Go to Custom Objects Tab and Click on Add button and Select Add Table:
-
Enter the desired Table name and click on OK:
-
And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.
-
Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
SELECT "ShipCountry", "OrderID", "CustomerID", "EmployeeID", "OrderDate", "RequiredDate", "ShippedDate", "ShipVia", "Freight", "ShipName", "ShipAddress", "ShipCity", "ShipRegion", "ShipPostalCode" FROM "Orders" Where "ShipCountry"='USA'
-
That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
SELECT * FROM "vt__usa_orders_only"
-
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')
-
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.
Actions supported by Google Calendar Connector
Google Calendar Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.| Parameter | Description |
|---|---|
| CalendarId |
|
| Parameter | Description |
|---|---|
| CalendarId |
|
| EventId |
|
| Parameter | Description |
|---|---|
| CalendarId |
|
| Parameter | Description |
|---|---|
| CalendarId |
|
| EventId |
|
| Parameter | Description |
|---|---|
| SourceCalendarId |
|
| TargetCalendarId |
|
| EventId |
|
| Parameter | Description |
|---|---|
| Url |
|
| Body |
|
| IsMultiPart |
|
| Filter |
|
| Headers |
|
Google Calendar Connector Examples for Informatica Connection
This page offers a collection of SQL examples designed for seamless integration with the ZappySys API ODBC Driver under ODBC Data Source (36/64) or ZappySys Data Gateway, enhancing your ability to connect and interact with Prebuilt Connectors effectively.
List calendars [Read more...]
Lists calendars
SELECT * FROM CalendarsList events [Read more...]
Lists events
SELECT * FROM Events
WITH (CalendarId='MyCalendarId')Get event [Read more...]
Gets event
SELECT * FROM get_event
WITH (CalendarId='MyCalendarId'
,EventId='MyEventId')Create event [Read more...]
Creates event
INSERT INTO Events(StartsAt, StartsInTimeZone, EndsAt, EndsInTimeZone, Summary,
Attendees, Description, Location, Status, Transparency, Visibility)
VALUES ('2021-11-26T16:30:50', 'Europe/Vilnius', '2021-11-27T16:30:50','Europe/Vilnius', 'This is an event',
null, 'My Description', 'Vilnius', 'confirmed', 'opaque', 'default')
WITH (CalendarId='YourCalendarId')Get event [Read more...]
Gets event
DELETE FROM Events
WITH (CalendarId='MyCalendarId',
EventId='MyEventId')Move event to a different calendar [Read more...]
Moves event to a different calendar
UPDATE move_event
WITH (SourceCalendarId='MySourceCalendarId',
TargetCalendarId='MyTargetCalendarId',
EventId='MyEventId'
)Conclusion
In this article we discussed how to connect to Google Calendar in Informatica and integrate data without any coding. Click here to Download Google Calendar Connector for Informatica and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).
Download Google Calendar Connector for Informatica
Documentation
More integrations
Other application integration scenarios for Google Calendar
Other connectors for Informatica
Download Google Calendar Connector for Informatica
Documentation
How to connect Google Calendar in Informatica?
How to get Google Calendar data in Informatica?
How to read Google Calendar data in Informatica?
How to load Google Calendar data in Informatica?
How to import Google Calendar data in Informatica?
How to pull Google Calendar data in Informatica?
How to push data to Google Calendar in Informatica?
How to write data to Google Calendar in Informatica?
How to POST data to Google Calendar in Informatica?
Call Google Calendar API in Informatica
Consume Google Calendar API in Informatica
Google Calendar Informatica Automate
Google Calendar Informatica Integration
Integration Google Calendar in Informatica
Consume real-time Google Calendar data in Informatica
Consume real-time Google Calendar API data in Informatica
Google Calendar ODBC Driver | ODBC Driver for Google Calendar | ODBC Google Calendar Driver | SSIS Google Calendar Source | SSIS Google Calendar Destination
Connect Google Calendar in Informatica
Load Google Calendar in Informatica
Load Google Calendar data in Informatica
Read Google Calendar data in Informatica
Google Calendar API Call in Informatica