Skip to content

The moment it happens

Post Wrike status changes to Slack

When a task's status moves, the channel sees the task with its old and new status.

Runs
The moment it happens
Apps
Wrike
AI
Not needed
Access
read

Send this to your assistant

Create a ClickRuntime automation: whenever a task in my 'Q3 Launch' Wrike project changes status, post the task title with its old and new status to #launch in Slack.

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

Handoffs in Wrike depend on status. A designer sets a task to In Review and the reviewer needs to pick it up. QA marks a bug as Rejected and the developer has to look at it again. If nobody sees the change, the task sits idle while everyone assumes someone else is on it, and a half-day delay becomes two days.

When a task's status changes, Wrike sends an event right away. The automation looks up the task's title and posts a Slack message showing the task name with the old status and the new one, so people can see at a glance what moved and from where.

Teams with sequential work, such as content approvals, design reviews and release checklists, rely on it most. The change is reported with the context needed to act, without opening Wrike.

What you get out of it

  • Handoffs happen when status changes

    The next person in the chain gets a message the moment a task moves into their stage, so work does not wait for them to happen to open Wrike. That shortens the idle time between steps, which is where most project delays hide.

  • Both statuses are shown

    Seeing In Progress changed to Completed, or Completed back to Active, explains what happened without opening the task, which is useful when a task gets reopened. Knowing the direction of the change tells you whether to celebrate or investigate.

  • Fewer status-check meetings

    If everyone can see movement in a channel, there is less need for a meeting whose only purpose is asking where things stand. Shared visibility cuts down on the check-in meetings people already complain about.

  • Reopened work gets noticed

    A task flipped back from Completed to Active is exactly the kind of change that gets missed, and a message makes sure the owner sees it. A message gives the owner a chance to react before the next deadline is affected.

  • A searchable history in Slack

    Months later, you can search the channel for a task title and see when it moved between statuses, which settles arguments about what happened and when. That record is useful in retrospectives and when a client asks about timing.

How it works

What happens, step by step

  1. When a task's status changes in Wrike, Wrike tells ClickRuntime straight away.

  2. The automation looks up the task's title.

  3. It posts the change to your Slack channel, showing the old status, the new status and a link to the task.

Before it runs live

  • Connect Wrike
  • Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens
Post Wrike status changes to Slackjust nowSucceeded
Slack · #launchLanding page copy: In Progress → Completed https://www.wrike.com/open.htm?id=1234567890

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 Wrike 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.
status_change_notifications.pyexample
from clickruntime import on_event, notify, http, credentials

@on_event
def handle(event):
    events = event.json if isinstance(event.json, list) else [event.json or {}]
    headers = {"Authorization": "Bearer " + credentials.connection("wrike", "main")}
    posted = 0
    for e in events:
        if e.get("eventType") != "TaskStatusChanged":
            continue
        task = http.get(f"https://www.wrike.com/api/v4/tasks/{e['taskId']}", headers=headers).json()["data"][0]
        notify.slack(f"{task['title']}: {e['oldStatus']} → {e['status']}\n{task['permalink']}", channel="#launch")
        posted += 1
    return {"posted": posted}

FAQ

Common questions

Does it notify me about every single task in Wrike?
It reacts to status change events that Wrike sends for the scope you connect. You can limit it to one folder or to certain statuses, such as only Completed and Rejected, so the channel is not flooded by every small move.
Can the message mention the assignee?
It can show the task title and statuses, and with a mapping of Wrike users to Slack users, your AI assistant can add a mention for the assignee. Without that mapping, the message goes to the channel without tagging anyone.
How quickly does the Slack message arrive?
The message is sent when the event reaches ClickRuntime, which is usually within seconds of the status being changed in Wrike. The task title is fetched at that moment, so it reflects the latest name.
What permissions does it need?
read. 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.

Set up “Post Wrike status changes to Slack” from your assistant

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