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.
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
When a task's status changes in Wrike, Wrike tells ClickRuntime straight away.
The automation looks up the task's title.
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
Build your own
Need it to work differently?
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
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?
Can the message mention the assignee?
How quickly does the Slack message arrive?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Hear in Slack when you're assigned a Wrike task
The moment someone makes you responsible for a task, you get a Slack message with its title, due date and link.
See how it worksGet your Wrike tasks for today in Slack
Every weekday morning you get a Slack list of your tasks due today and anything already overdue.
See how it worksGet an email when a project task goes overdue
When a task in your project passes its due date unfinished, you get one email about it.
See how it worksKeep exploring
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.
