Skip to content

The moment it happens

Tick off Google Tasks when a commit finishes them

When you push commits, tasks they finish are marked done in Google Tasks and Slack hears about it.

Runs
The moment it happens
Apps
Google Tasks, Slack
AI
Yes, uses the built-in AI allowance
Access
tasks; chat:write

Send this to your assistant

Create a ClickRuntime automation: when my GitHub repo gets a push, match the commit messages to my open Google Tasks, mark the matches complete and post them to #dev.

Paste it into your assistant. It tells you what it will send or change before it runs live.

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Developers who keep their to-do list in Google Tasks end up doing the work twice: once in code, once ticking the box. The box gets forgotten, so the list drifts out of date and stops being trusted.

Solo developers, small product teams and freelancers use it to keep their task list honest without extra clicks, and to let others see progress in Slack as it happens.

What you get out of it

  • Your list stays current

    Tasks finished in code are ticked off at the same moment, so the list reflects what is really left.

  • Progress others can see

    A Slack post tells the team which tasks a push completed, which saves status questions.

  • Matching by meaning

    Commit messages rarely repeat a task's exact wording. AI matches "fix invoice rounding" to the task Rounding bug on Acme invoices.

  • Only clear matches count

    Tasks are completed only when a commit clearly finishes them, so a passing mention does not close anything.

How it works

What happens, step by step

  1. When you push to your GitHub repository, GitHub sends the push to your automation's link and ClickRuntime checks that it really came from GitHub.

  2. It reads the commit messages and your open Google Tasks.

  3. AI picks the tasks that the commits clearly finish.

  4. Those tasks are marked complete, and a Slack message lists them with the commit that closed each.

Before it runs live

  • Connect Google Tasks
  • Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
  • Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens
Tick off Google Tasks when a commit finishes themjust nowSucceeded
Slack · #devCompleted by push to acme-billing: • Rounding bug on Acme invoices ← Fix invoice rounding for EUR totals

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

  • Act only on the items that match your own rules, and skip the rest
  • Change what the AI looks for, or how it writes the result
  • Add another app, for example also send it to Google Sheets
  • Combine it with other Google Tasks and Slack steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
complete_google_tasks_from_github_commits.pyexample
from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build
from clickruntime import on_event, credentials, notify, ai

SCHEMA = {"type": "object", "properties": {"done": {"type": "array", "items": {"type": "object", "properties": {
    "task_id": {"type": "string"}, "commit": {"type": "string"}}}}}}

@on_event
def handle(event):
    if not event.is_verified:
        return {"skipped": "unverified"}
    commits = [c["message"].splitlines()[0] for c in (event.json or {}).get("commits", [])]
    if not commits:
        return {"completed": 0}
    tasks = build("tasks", "v1", credentials=Credentials(credentials.connection("google", "work")), cache_discovery=False).tasks()
    open_tasks = {t["id"]: t["title"] for t in tasks.list(tasklist="@default", showCompleted=False).execute().get("items", [])}
    if not open_tasks:
        return {"completed": 0}
    matches = ai.generate("Which tasks do these commits clearly finish? Only include certain matches.\nTasks:\n"
                          + "\n".join(f"{i}: {t}" for i, t in open_tasks.items()) + "\nCommits:\n" + "\n".join(commits),
                          json_schema=SCHEMA, max_output_tokens=300).json["done"]
    lines = []
    for m in matches:
        if m["task_id"] in open_tasks:
            tasks.patch(tasklist="@default", task=m["task_id"], body={"status": "completed"}).execute()
            lines.append(f"• {open_tasks[m['task_id']]} ← {m['commit']}")
    if lines:
        notify.slack(f"Completed by push to {event.json['repository']['name']}:\n" + "\n".join(lines), channel="#dev")
    return {"completed": len(lines)}

FAQ

Common questions

Do I need to mention the task in the commit?
No, but it helps. Clear commit messages such as Fix invoice rounding for Acme give the most reliable matches.
Can it complete the wrong task?
It can, if two tasks are very similar. The Slack post lists every task it completed, so you can reopen one in Google Tasks if needed.
Is the push from GitHub checked?
Yes. Set a webhook secret in GitHub and in your ClickRuntime dashboard, and pushes that fail the signature check are ignored.
What permissions does it need?
tasks; chat:write. Nothing else in your accounts is used.
Does it need AI?
Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.
How many runs does it use?
One run for each event the app sends.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Set up “Tick off Google Tasks when a commit finishes them” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.