Weekly Wrike project health summary, posted to Slack and drafted in Gmail

Build an agent workflow that runs every Friday at 3pm ET and publishes a weekly project-health executive summary across our Wrike workspace.

Data gathering, in Wrike. Use List Folders to enumerate every active project in the account, filtering to folders that have project metadata and are not archived or completed. For each active project, call List All Tasks scoped to that project's folder to pull open tasks, their statuses, assignees, due dates, and last-updated timestamps. Then call Get Folder History on each project to capture recent status changes, owner changes, and date shifts over roughly the last two weeks. Be mindful of Wrike rate limits and serialize the per-project calls.

Classification. Grade every active project red, yellow, or green using these heuristics: red if there are overdue tasks tied to a milestone, no activity in the last seven days, a milestone that has not moved in two weeks, or a high share of tasks still in the earliest workflow status with a due date inside the next two weeks. Yellow if any single risk signal is present but the project is otherwise moving. Green if none of the signals fire. Each project gets a short one-line reason for its grade.

Narrative. Write a one-page summary grouped by status in this order: red first, then yellow, then green. Inside each group list projects with their owner, current status, and the one-line reason. After the groups, add a Top Three At Risk section that calls out the three highest-risk projects by name with the named owner and one concrete recommended next step for each (for example: confirm a new due date, reassign an owner, escalate a blocker). The tone should be opinionated and executive friendly, not a raw data dump. No tables of every task.

Delivery. Post the full narrative to the #leadership Slack channel using Send a Message, formatted with Slack markdown and section headers for Red, Yellow, Green, and Top Three At Risk. Then use Gmail Create a Draft to leave a polished email version in the project manager's drafts folder. The email should have a subject line like "Weekly project health, week of {date}", a brief intro paragraph, the same status groupings, and the Top Three At Risk section. Leave the To field empty so the PM can choose recipients before sending.

Configuration. Make the Slack channel, the Gmail account used for the draft, the time zone, the activity-staleness threshold (default 7 days), and the milestone-stall threshold (default 14 days) easy to change at setup. If Wrike returns zero active projects, skip the Slack and Gmail steps and log a no-op for that week.

Additional information

What does this prompt do?

Scans every active Wrike project once a week and grades each one red, yellow, or green based on overdue work, stalled milestones, and lack of recent activity.
Writes a one-page narrative summary grouped by status, with the top three at-risk projects called out by name with owners and a recommended next step.
Posts the report to your leadership Slack channel so the whole team sees the same picture at the same time.
Drops a polished email version into the PM's Gmail drafts, ready to forward to execs without any extra cleanup.

What do I need to use this?

A Wrike workspace where your active projects live.
A Slack workspace and the channel you want the leadership update posted into.
A Gmail account for the project manager who sends the exec-facing recap.

How can I customize it?

Change the schedule. Run it Monday morning instead of Friday afternoon, or shift the time zone to match your leadership team.
Adjust the risk rules. Tighten or loosen the thresholds for what counts as stalled, overdue, or at risk.
Swap recipients. Point the Slack post at a different channel and change who owns the Gmail draft.

Frequently asked questions

Do I need a paid Wrike plan to use this?

Any Wrike plan that lets you create active projects and read folder history will work. The report only reads project data, it does not change anything in Wrike.

Will it post anything in Slack without my approval?

Yes, that is the point. The Friday post goes straight to the leadership channel you pick so the team sees the same status at the same time. The exec email goes to a Gmail draft so a human can review it before sending.

How does it decide what is red, yellow, or green?

It uses simple heuristics like overdue tasks, projects with no activity in the last seven days, milestones that have not moved, and a heavy backlog of early-stage tasks close to the due date. You can tune the thresholds when you set it up.

What if a project does not have a clear owner?

The summary will still grade it and surface it in the at-risk list, with a note that the owner is unassigned so leadership can fix it.

Can I change the Slack channel or the email recipient later?

Yes. Both are easy to swap, and you can also change the day, the time, and the exact wording of the report at any time.