The moment it happens

Share completed Teamwork.com tasks in Slack

Your channel hears who finished which task, and in which project, as it happens.

Runs: The moment it happens
Apps: Teamwork.com
AI: Not needed
Access: read (site admin to configure webhooks)

Send this to your assistant

Create a ClickRuntime automation: when a task is marked complete in Teamwork.com, post the task, its project and the person who completed it to #wins in Slack, with a link.

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

Add to ChatGPT Add to Claude

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

Why use it

Why teams use this automation

A project manager at a design agency waits on a developer to finish the homepage build in Teamwork before a designer can start the visual review. The developer ticks the task complete and moves on. The designer finds out two days later in a stand-up, and the review slips, pushing the client presentation back. Multiply that by dozens of handoffs per project and delays pile up quietly.

When someone marks a Teamwork task complete, Teamwork sends the event and ClickRuntime reads the task name, the project and the person who completed it from the payload. It posts a message to your Slack channel with a link to the task. The next person in the chain sees that their turn has come within seconds.

It works well for agencies, product teams and operations groups where one person's finished task is another person's starting gun.

What you get out of it

Handoffs happen the same hour
The person waiting for a task sees it is done at once and starts. Dead time between steps, which often accounts for more delay than the work itself, shrinks noticeably across a project.
Project managers stop chasing status
Instead of asking whether the build is finished, they read the channel. That frees time for planning and removes the small interruptions that make developers feel micromanaged. Developers also get left alone to finish work.
Clients hear good news sooner
When a deliverable task is completed, the account manager can tell the client the same day. Quick updates on progress build trust and reduce anxious check-in emails. The client hears about progress before they have to ask.
Wins are visible to the whole team
A stream of completed tasks in a channel shows momentum. It helps morale on long projects and gives leaders a feel for pace without opening reports. Seeing finished work stack up helps a long project feel like it is moving.
The channel doubles as a progress record
Scrolling back shows what was finished on which day and by whom. That helps when reconstructing a timeline for a client dispute or a retrospective on why a project overran.

How it works

What happens, step by step

When someone completes a task in Teamwork.com, Teamwork.com tells ClickRuntime straight away.
ClickRuntime reads the task name, the project and who completed it.
A message goes to your #wins Slack channel, such as "Maya Chen completed Launch Acme help center", with a link to the task.

Before it runs live

Connect Teamwork.com
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Share completed Teamwork.com tasks in Slackjust nowSucceeded

Slack · #wins✅ Maya Chen completed *Launch Acme help center* in Acme rollout

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
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Teamwork.com 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.

completed_task_notifications.pyexample

from clickruntime import on_event, notify

SITE = "yourcompany"

@on_event
def handle(event):
    body = event.json
    task = body.get("task") or {}
    project = (body.get("project") or {}).get("name", "")
    user = body.get("eventCreator") or {}
    who = f"{user.get('firstName', '')} {user.get('lastName', '')}".strip() or "Someone"
    notify.slack(
        f"✅ {who} completed *{task.get('name')}* in {project}\n"
        f"https://{SITE}.teamwork.com/app/tasks/{task.get('id')}",
        channel="#wins",
    )
    return {"task": task.get("id")}

FAQ

Common questions

Does it post for every task in every project?

By default it follows the events Teamwork sends for your account. If your channel would get too noisy, filter by project or task list, for example only the Website Redesign project, and other completions are skipped.

Who needs to set up the webhook in Teamwork?

Creating webhooks in Teamwork requires a user with sufficient permission, usually an administrator of the site. The webhook points to the link ClickRuntime gives you, and the Slack side only needs a connected workspace. That keeps the channel readable.

Will subtasks and recurring tasks trigger messages?

Subtask completions arrive as task completion events as well, so they can post. If that is too many messages, a condition can skip subtasks. Recurring tasks send an event each time an occurrence is completed.

What permissions does it need?

read (site admin to configure webhooks). Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's 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.

The moment it happens