feat: pull Google Tasks into Delta #291

Closed
opened 2026-05-11 18:30:38 +00:00 by barrettruth · 2 comments
Owner

Problem

Google Tasks pull/populate is part of the minimum viable integration scope.

Delta should be able to pull tasks from Google Tasks into the local task model without creating duplicates or requiring multi-user/app-login infrastructure.

Solution

  • Use the single-user Google provider connection from #290.
  • Read Google Task lists and tasks from the Google Tasks API.
  • Preserve Google task/list IDs in local metadata so repeated pulls are idempotent.
  • Map title, notes, due date, completed status, deleted/hidden state, and list name/category where possible.
  • Start with pull/populate into Delta; do not add bidirectional Google Tasks writes unless explicitly split into a later issue.
  • Provide a manual sync trigger and let the narrow sync scheduler from #295 run it later.

Acceptance criteria

  • Pulling Google Tasks creates or updates Delta tasks without duplicates.
  • Completed/deleted Google Tasks are handled deliberately and documented.
  • A failed pull reports a clear operator-visible error.
  • The implementation does not depend on app login, multi-user accounts, or generic automations UI.
## Problem Google Tasks pull/populate is part of the minimum viable integration scope. Delta should be able to pull tasks from Google Tasks into the local task model without creating duplicates or requiring multi-user/app-login infrastructure. ## Solution - Use the single-user Google provider connection from #290. - Read Google Task lists and tasks from the Google Tasks API. - Preserve Google task/list IDs in local metadata so repeated pulls are idempotent. - Map title, notes, due date, completed status, deleted/hidden state, and list name/category where possible. - Start with pull/populate into Delta; do not add bidirectional Google Tasks writes unless explicitly split into a later issue. - Provide a manual sync trigger and let the narrow sync scheduler from #295 run it later. ## Acceptance criteria - Pulling Google Tasks creates or updates Delta tasks without duplicates. - Completed/deleted Google Tasks are handled deliberately and documented. - A failed pull reports a clear operator-visible error. - The implementation does not depend on app login, multi-user accounts, or generic automations UI.
barrettruth added this to the v0.1.0 milestone 2026-05-11 18:30:38 +00:00
Author
Owner

Tracker note: this issue previously mentioned the generic scheduler from #295, which is now retired scope. Treat #291 as owning a manual pull/populate path first; split a narrow sync runner later if needed rather than reviving generic automations.

Tracker note: this issue previously mentioned the generic scheduler from #295, which is now retired scope. Treat #291 as owning a manual pull/populate path first; split a narrow sync runner later if needed rather than reviving generic automations.
Author
Owner

Basic Google Tasks pull remains closed here. Follow-up #442 tracks the v0.1 merge/outdated policy: last-applied snapshots, local-modified detection, conflict counts, and operator-visible sync issue tracking while keeping Google Tasks pull-only.

Basic Google Tasks pull remains closed here. Follow-up #442 tracks the v0.1 merge/outdated policy: last-applied snapshots, local-modified detection, conflict counts, and operator-visible sync issue tracking while keeping Google Tasks pull-only.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/delta#291
No description provided.