Google Tasks Recurring Task Generator

Overview

This flow adds robust, template-driven recurring tasks to Google Tasks — going beyond Google's limited built-in repeat options. On a daily schedule it reads recurrence templates stored in a Dataverse table, finds the ones whose next-due date has arrived, creates each as a Google Task with the correct due date, advances the template's schedule by its cadence (which inherently avoids duplicates), and posts a summary to a Microsoft Teams channel.

Why it matters: Google Tasks can only repeat on simple fixed intervals and has no central management. A template-driven generator supports any day-based cadence (daily standups, weekly reports, 30/60/90-day reviews), keeps all recurrence rules in one governed Dataverse table, and notifies the team each run.

Build: CF-700. Solution FlowLibs - Google Tasks Recurring Task Generator. State Off (demo). Flow Checker 0 errors / 0 warnings.

Use Case

Operations and business users who manage recurring work in Google Tasks need cadences Google can't express natively and a single place to maintain them. They populate the Recurring Task Template Dataverse table (title, notes, cadence in days, next-due date, target list), switch the flow On, and the generator creates each instance on time and reports activity to Teams.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Google Tasks	shared_googletasks	CraeteTask
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords UpdateRecord
Microsoft Teams	shared_teams	PostMessageToConversation

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Change cadence

Edit each template row's flowlibs_cadencedays (e.g. 1 = daily, 7 = weekly, 30 = monthly-ish). No flow edits needed.

Pause a recurrence

Set flowlibs_status to Paused; the row stops generating without being deleted.

Per-template list

Set flowlibs_tasklistid on a row to route that recurrence to a specific Google Tasks list; otherwise it uses flowlibs_GoogleTaskListId.

Generation frequency

Adjust the Recurrence trigger (frequency/interval/startTime) to run more or less often.

Lead time

To create tasks N days early, compare flowlibs_nextdue against addDays(varRunTimestamp, N) in the List Due Recurring Templates filter.

Notification target

Re-point flowlibs_TeamsGroupId / flowlibs_TeamsChannelId, or swap the Teams action for email.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

concat('flowlibs_status eq ''Active'' and flowlibs_nextdue le ', variables('varRunTimestamp'))

coalesce(items('Apply_to_each_Template')?['flowlibs_tasklistid'], variables('varDefaultTaskList'))

addDays(items('Apply_to_each_Template')?['flowlibs_nextdue'], items('Apply_to_each_Template')?['flowlibs_cadencedays'])

length(coalesce(outputs('List_Due_Recurring_Templates')?['body/value'], createArray()))

Customize & download