Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Google Tasks

Task list management application

CategoryProductivity
AuthenticationOAuth 2.0
Version0.6.0
Published scopes2 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Google Tasks with Flows360

Task list management application

Use the Google Tasks connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 11 actions and 1 trigger.

Available actions

  • Add Task
  • Find Tasks
  • Mark Task Complete
  • Update Task
  • Delete Task
  • Create Task
  • Get Task
  • Move Task
  • Plus 3 additional declared actions.

Available triggers

  • New Task

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Google Tasks
  • Package: @activepieces/piece-google-tasks@0.6.0
  • Exact artifact digest: sha256:e2241f1c419156d27f21f37fb9976bf1077ed11a796abd9bcac160b3f061bd4e
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Add Task (add_task), Add a new task to a specified task list Classification: read.
  • Find Tasks (find_tasks), Search and list tasks in a task list with optional date-range and status filters. Classification: read.
  • Mark Task Complete (complete_task), Mark an existing task as completed. Classification: read.
  • Update Task (update_task), Edit an existing task, title, notes, due date, or status. Classification: read.
  • Delete Task (delete_task), Permanently delete a task by ID. Classification: read.
  • Create Task (create_task), Create a new task in a task list, optionally as a subtask and/or positioned after a sibling. Classification: read.
  • Get Task (get_task), Fetch a single task by its ID. Classification: read.
  • Move Task (move_task), Reposition or reparent a task within its list, or move it to another list. Classification: read.
  • Clear Completed Tasks (clear_completed_tasks), Hide all completed tasks in a task list. Classification: read.
  • List Task Lists (list_task_lists), List the authenticated user's task lists (id and title). Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Task, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects12
Supported actionsNot published
Triggers1

Authentication

Authentication method: OAuth 2.0

Required scopes

https://www.googleapis.com/auth/tasksemail

Authentication profiles

connection · oauth2

OAuth scopes: https://www.googleapis.com/auth/tasks, email

Supported objects

ObjectReadWriteNotes
Add Task Yes No Add a new task to a specified task list
Find Tasks Yes No Search and list tasks in a task list with optional date-range and status filters.
Mark Task Complete Yes No Mark an existing task as completed.
Update Task Yes No Edit an existing task u2014 title, notes, due date, or status.
Delete Task Yes No Permanently delete a task by ID.
Create Task Yes No Create a new task in a task list, optionally as a subtask and/or positioned after a sibling.
Get Task Yes No Fetch a single task by its ID.
Move Task Yes No Reposition or reparent a task within its list, or move it to another list.
Clear Completed Tasks Yes No Hide all completed tasks in a task list.
List Task Lists Yes No List the authenticated user's task lists (id and title).
Custom API Call Yes No Make a custom API call to a specific endpoint
New Task Yes No polling trigger declared by the pinned package.

Triggers

New Task · Poll

Triggers when a task is created

Inputs

  • tasks_list · string

Setup

Setup

  1. Add the Google Tasks connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.

OAuth scopes

  • https://www.googleapis.com/auth/tasks
  • email
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-google-tasks@0.6.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 11 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Google Tasks connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-google-tasks@0.6.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com