https://community.appian.com/discussions/f/integrations/7030/hi-team-regarding-access-to-google-apis-ex-google-calendar-curreHi Team, Regarding access to Google APIs(ex. Google Calendar). Currently Google is using OAuth 2.0. Before when using OAuth 1.0, you need to input Consumer Key, and Consumer Secret to be able to use Create Event Smart Service. This time in OAuth 2.0,en-USTelligent Community 12https://community.appian.com/thread/28330?ContentTypeID=1Fri, 26 Feb 2016 07:19:01 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:0c32051d-d7eb-477e-a502-12687c9fc681riangThanks Tom and Eliot. Will check on this API.<div style="clear:both;"></div>https://community.appian.com/thread/28271?ContentTypeID=1Wed, 24 Feb 2016 21:06:46 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:5cb867ec-926d-44f6-98ab-cd4a1a87a0ceEliot GersonThis may be possible to implement, but it will depend on the exact specifics of your use case. Some integrations with Google APIs may work, while others may not. Likewise, some implementations of OAuth 2.0 may work where others don&#39;t. <br /><br />A good starting point might be to take a look at this plugin: <a href="https://forum.appian.com/suite/tempo/records/type/components/item/i8BCLGOdlMUpdGVqT-RV7oRg74uEGJO5yQa01fYXska-IVhw0urLsEGTPT20MRdSw/view/summary">forum.appian.com/.../summary</a><br /><br />It integrates with the Dropbox API using OAuth 2.0 and might give you some ideas.<div style="clear:both;"></div>https://community.appian.com/thread/28247?ContentTypeID=1Wed, 24 Feb 2016 10:52:37 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:19773662-38ad-4184-ad7e-cb03bd6a6157Tom RyanNote that if you need to access the Stored Credential file directly through the filesystem, the plugin will not be Cloud Approved. You should ensure that the Stored Credential file can be saved as a file within Appian.<div style="clear:both;"></div>https://community.appian.com/thread/28208?ContentTypeID=1Tue, 23 Feb 2016 14:46:58 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:18a1ffe9-c1b4-4b5b-81fd-2dd5921060d2riang...PI? and then on that page, it will return to appian if the user allowed/permit access to the API. Once it allows access, a StoredCredential file will be stored on the server and will be read everytime the user accesses Google API.<br /><br />This is the way Google OAuth2.0 is implementing it&#39;s security using OAuth Consent Screen.<br /><br />Thanks in advance!<br /><br /><br /><div style="clear:both;"></div>