Pulse in Venom Tasks
One feed of the status updates of the projects and initiatives you lead, work on or follow, with health changes highlighted, the ones overdue for an update, and a weekly digest in the bell and by email.
Where a project or initiative has an update schedule, "overdue" follows it (due, late, missing or quiet); without one, it is no update in 7 days.
Projects and initiatives each have a feed of status updates, a health (on track, at risk, off
track) and a note. Pulse puts the updates of everything you care about in one place, so you don't have to open
them one at a time. Open it from the Tasks sidebar under Workspace, or at /tasks/pulse.
What is in your Pulse
You get the updates of:
- projects you lead,
- projects you are a member of,
- initiatives you own,
- any project or initiative you follow.
Archived projects and initiatives are left out. Private teams apply as everywhere: a project whose teams are all private teams you're not in never shows, not even by name.
Follow and unfollow
- On a project's or initiative's page, press Follow to add its updates to your Pulse and weekly digest. The button then reads Following.
- On something you lead, own or are a member of, the button reads In your Pulse. Pressing it unfollows the project or initiative: its updates leave your Pulse and digest even though you still lead it. Press Follow to bring them back.
- The In your Pulse list at the bottom of the Pulse page shows everything in your Pulse and why ("You lead it, you follow it"), plus what you unfollowed, each with a Follow or Unfollow button.
Following is your own setting. Anyone who can read Tasks can follow, including read-only roles.
The feed
Updates come newest first, grouped by day. Each shows the project or initiative, its health, who posted it and the note.
- Health changes are highlighted. An update whose health differs from the previous update on the same project or initiative gets a coloured border and a chip such as On track → At risk: amber or red when it got worse, green when it got better. The first update of something is not a change.
- Filters: All, Projects, Initiatives, or Health changes only.
- Show older updates loads the next page.
Due an update
Above the feed, Due an update lists started projects and active initiatives in your Pulse whose last update is more than 7 days old, or that never had one (counted from when the project started, or the initiative was created). The longest wait comes first. When you lead the project or own the initiative, Write update opens its page. Paused, planned, completed and canceled ones are never due. The section hides when nothing is due.
The weekly digest
Every Monday from 07:00 UTC, everyone with something in their Pulse gets a digest of the last whole week (Monday to Monday, UTC):
- how many updates there were, across how many projects and initiatives,
- how things stand (how many are off track, at risk and on track, from each one's latest update),
- every health change of the week,
- the latest update of each project and initiative, worst first,
- what was due an update when the digest was made.
It lands in the bell at the top of every page ("Your weekly Pulse: 6 updates, 2 health changes, 1 due an update") and stays there until you open it or press Mark all read. Opening it shows it at the top of the Pulse page. A week with no updates and nothing due makes no digest.
Before Monday's digest arrives, Make last week's now on the Pulse page makes yours at once (the same digest the Monday run would make; it is not emailed).
By email
Turn on Email digest in your notification settings to get the digest by email too. It goes out through the email provider your organisation connected in Support settings, from that provider's address, and through nothing else. Without a provider nothing is sent, and the digest on the Pulse page says so.
A written summary
An organisation can add a few sentences to each digest saying what changed, what is at risk and why, and what is waiting for an update. They are written by the organisation's default gear through its own routes, the same way AI triage works, and only from the digest's facts (names, health and short excerpts of the notes).
- It is off until an owner or admin turns on Summaries by your organisation's gear at the bottom of the Pulse page.
- Summaries are capped at $1 a day for the organisation by default (
dailyCapUsd, 0 to 100). At the cap, digests go out without a summary until the next day (UTC). - If no gear answers, the digest goes out without one.
Changing these settings is recorded in the audit log.
For agents: REST and MCP
Every action has a REST route and an MCP tool that runs it as the caller. See the Tasks API for the shapes.
| Action | REST | MCP tool |
|---|---|---|
| Read your Pulse | GET /tasks/api/pulse?filter=all|projects|initiatives|changed&before=&limit= |
tasks_pulse_get |
| What is in your Pulse and why | GET /tasks/api/pulse/follows |
tasks_follow_list |
| Follow, unfollow a project | POST, DELETE /tasks/api/projects/{id}/follow |
tasks_project_follow, tasks_project_unfollow |
| Follow, unfollow an initiative | POST, DELETE /tasks/api/initiatives/{id}/follow |
tasks_initiative_follow, tasks_initiative_unfollow |
| Your digests | GET /tasks/api/pulse/digests |
tasks_pulse_digest_list |
| Make last week's digest now | POST /tasks/api/pulse/digests |
tasks_pulse_digest_create |
| One digest; mark it read | GET, PATCH /tasks/api/pulse/digests/{id} |
tasks_pulse_digest_get, tasks_pulse_digest_update |
| The organisation's summary settings | GET, PUT /tasks/api/pulse/settings |
tasks_pulse_settings_get, tasks_pulse_settings_update |
Pulse belongs to a member: an agent key that acts for no member gets 403.