The moment it happens

Announce new Teamwork.com tasks in Slack

Each task added to your project shows up in Slack with its name, assignee and a link.

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: whenever someone adds a task to the Website Redesign project in Teamwork.com, post the task name, who it's assigned to and a link in #web-team on Slack.

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 support lead assigns a task to an engineer in Teamwork on a Friday afternoon. The engineer is heads-down in another tool and Teamwork's own email notification lands among fifty other messages. Monday comes, the task has not been touched, and the customer who needed a fix has waited three days for an acknowledgment. The assignment was made, but nobody noticed.

When a task is created in Teamwork, ClickRuntime receives the event and posts a message to Slack with the task name, who it is assigned to and a link. The person who needs to act sees it in the place they already read all day, instead of in a separate notification stream.

It suits teams who live in Slack and treat Teamwork as the record rather than the place they watch.

What you get out of it

Assignments are seen quickly
A Slack message with the assignee's name draws attention far better than an email in a crowded inbox. The task gets picked up on Friday, not discovered on Monday. That is a small change with a large effect on response time.
Urgent work gets a fast start
If a task needs same-day attention, the channel makes it obvious. The assignee can reply in the thread to confirm and give a time estimate, which reassures whoever requested it.
The team sees incoming work
A visible feed of new tasks shows what is arriving and how fast. That helps leads spot overload and decide when to push back or ask for help. Spotting a spike in requests lets you act before it becomes a backlog.
Fewer tasks are created and forgotten
Because creation is visible, tasks logged and then ignored get noticed. Duplicates can be caught too, when a colleague sees that someone already added the same request. A public record of creation also makes it harder for a task to vanish.
It cuts down on side messages
Instead of pinging the assignee in a direct message saying I just created a task for you, the creator can rely on the channel. That saves a small interruption for both people each time.

How it works

What happens, step by step

When a new task is created in Teamwork.com, Teamwork.com tells ClickRuntime straight away.
ClickRuntime reads the task name, the project and who it is assigned to.
A message goes to your Slack channel with those details and a link to open 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

Announce new Teamwork.com tasks in Slackjust nowSucceeded

Slack · #web-teamNew task in Website Redesign: *Update pricing page hero* (Maya Chen) https://northwind.teamwork.com/app/tasks/4821

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.

new_task_notifications.pyexample

from clickruntime import on_event, notify

SITE = "yourcompany"  # yourcompany.teamwork.com
PROJECT = "Website Redesign"

@on_event
def handle(event):
    body = event.json
    task, project = body.get("task") or {}, body.get("project") or {}
    if project.get("name") != PROJECT:
        return {"posted": False}
    assignees = ", ".join(f"{u.get('firstName', '')} {u.get('lastName', '')}".strip()
                          for u in body.get("users") or []) or "unassigned"
    notify.slack(
        f"New task in {PROJECT}: *{task.get('name')}* ({assignees})\n"
        f"https://{SITE}.teamwork.com/app/tasks/{task.get('id')}",
        channel="#web-team",
    )
    return {"posted": True, "task": task.get("id")}

FAQ

Common questions

Does it post for tasks created by integrations and imports?

Teamwork sends an event for each created task regardless of how it was made, so imports and integrations can trigger messages too. A large import could flood the channel, so you can add a limit or pause the run during imports.

Can I mention the assignee in Slack?

Yes, when the assignee's Teamwork email matches their Slack account, the message can tag them directly. If the emails differ, you can provide a simple mapping so the right person is mentioned for each task.

Can I notify only for high priority tasks?

Yes. Teamwork tasks carry a priority field, so a condition can post only when priority is high. Other tasks are skipped, and you can still send them to a quieter channel if you want a full log.

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