# Update source-google-tasks This PR was autogenerated by running `airbyte-ci connectors --name=source-google-tasks up_to_date --pull` We've set the `auto-merge` label on it, so it will be automatically merged if the CI pipelines pass. If you don't want to merge it automatically, please remove the `auto-merge` label. Please reach out to the Airbyte Connector Tooling team if you have any questions or concerns. ## Operations - Upgrade the base image to the latest version in metadata.yaml: Successful - PATCH bump source-google-tasks version to 0.0.39: Successful - Build source-google-tasks docker image for platform(s) linux/amd64, linux/arm64: Successful - Get dependency updates: Successful - Create or update pull request on Airbyte repository: Successful - Add changelog entry: Successful ## Dependency updates We use [`syft`](https://github.com/anchore/syft) to generate a SBOM for the latest connector version and the one from the PR. It allows us to spot the dependencies that have been updated at all levels and for all types of dependencies (system, python, java etc.). Here are the dependencies that have been updated compared to `airbyte/source-google-tasks:latest`. Keep in mind that `:latest` does not always match the connector code on the main branch. It is the latest released connector image when the head commit of this branch was created. | Type | Name | State | Previous Version | New Version | |------|------|-------|-------------|------------------| | python | airbyte-cdk | updated | 6.60.12 | **7.3.4** | | python | anyio | updated | 4.10.0 | **4.11.0** | | python | cattrs | updated | 24.1.2 | **25.2.0** | | python | importlib_metadata | updated | 8.0.0 | **8.7.0** | | python | joblib | updated | 1.5.1 | **1.5.2** | | python | jsonschema | updated | 4.17.3 | **4.25.1** | | python | pandas | updated | 2.2.2 | **2.2.3** | | python | whenever | updated | 0.6.16 | **0.8.8** | | python | zipp | updated | 3.19.2 | **3.23.0** | | python | jsonschema-specifications | added | not present | **2025.4.1** | | python | referencing | added | not present | **0.36.2** | | python | rpds-py | added | not present | **0.27.1** | | python | filelock | removed | 3.18.0 | **not present** | | python | pyrsistent | removed | 0.20.0 | **not present** | > [!IMPORTANT] > **Auto-merge enabled.** > > _This PR is set to merge automatically when all requirements are met._ Co-authored-by: octavia-bot-hoard[bot] <230633153+octavia-bot-hoard[bot]@users.noreply.github.com>
Google Tasks
This directory contains the manifest-only connector for source-google-tasks.
Documentation reference:
Visit https://developers.google.com/tasks/reference/rest for API documentation
Authentication setup
Source-productive uses bearer token authentication,
Visit https://support.google.com/googleapi/answer/6158849?hl=en&ref_topic=7013279 for getting bearer token via OAuth2.0
Setting postman for getting bearer token
Currently Code granted OAuth 2.0 is not directly supported by airbyte, thus you could setup postman for getting the bearer token which could be used as api_key,
Steps:
- Visit google cloud
https://console.cloud.google.com/apis/api/tasks.googleapis.com/metricsand enable the tasks api service - Go to the consent screen
https://console.cloud.google.com/apis/credentials/consentand add your email for enabling postman testing access - Visit
https://console.cloud.google.com/apis/credentialsand create new credentails for OAuth 2.0 and copy client id and client secret - Add callback url
https://oauth.pstmn.io/v1/callbackwhile credential creation - Goto postman client and select new tab for setting authorization to OAuth 2.0
- Set scope as
https://www.googleapis.com/auth/tasks https://www.googleapis.com/auth/tasks.readonly - Set access token URL as
https://accounts.google.com/o/oauth2/token - Set auth URL as
https://accounts.google.com/o/oauth2/v2/auth - Click
Get New Access Tokenand authorize via your google account - Copy the resulted bearer token and use it as credential for the connector
- Set scope as
Usage
There are multiple ways to use this connector:
- You can use this connector as any other connector in Airbyte Marketplace.
- You can load this connector in
pyairbyteusingget_source! - You can open this connector in Connector Builder, edit it, and publish to your workspaces.
Please refer to the manifest-only connector documentation for more details.
Local Development
We recommend you use the Connector Builder to edit this connector.
But, if you want to develop this connector locally, you can use the following steps.
Environment Setup
You will need airbyte-ci installed. You can find the documentation here.
Build
This will create a dev image (source-google-tasks:dev) that you can use to test the connector locally.
airbyte-ci connectors --name=source-google-tasks build
Test
This will run the acceptance tests for the connector.
airbyte-ci connectors --name=source-google-tasks test