ProjectPulse

Automated Project Health and Client Update Agent

Overview

ProjectPulse is an automated agent that delivers consistent, reliable project updates using real activity from monday.com.

It works on two levels:

• Daily internal visibility via email
• Weekly consolidated project updates inside monday.com

The goal is to keep teams aligned day-to-day, while ensuring clients and stakeholders get a clean, professional weekly summary without exposing internal noise.

---

What Problem ProjectPulse Solves

Project reporting usually fails because it is:

• Manual and time-consuming
• Inconsistent across projects
• Too detailed for clients, or too vague for delivery teams

ProjectPulse removes guesswork by summarizing what actually happened, on a predictable schedule, using structured sections that are easy to read and reuse.

---

Who This Is For

• Project Managers
• Delivery and Implementation Teams
• Account Managers
• Client-facing Stakeholders

If your projects live in monday.com, ProjectPulse becomes your reporting backbone.

---

Prerequisites

Before deploying ProjectPulse, verify the following:

• A monday.com workspace is active and contains a parent Projects board and a child Tasks board.
• The Tasks board is linked to the Projects board so each task item references its parent project.
• monday.com API access is configured in Synthreo Builder with a valid monday.com API token.
• An email delivery integration is configured so the daily email summaries can be sent to internal recipients.
• The target recipient email addresses for daily updates are known and configured in the agent.
• The scheduled trigger is configured for the daily run time and the Friday weekly run.

---

How ProjectPulse Works

ProjectPulse runs on a scheduled cadence and behaves differently depending on the day.

Daily Execution (Email Updates)

• Runs every day at a configurable time
• The run time is fully adjustable based on team preference
• Reviews activity that occurred during the current week
• Sends an email summary of:
  • What changed
  • What progressed
  • What may need attention

This gives internal teams continuous visibility without needing to check monday.com.

---

Weekly Execution (monday.com Update)

• Runs every Friday
• Generates a single consolidated project update
• Posts the update at the Project level in monday.com
• Overwrites the existing pinned ProjectPulse update
• Pins the new update so it is always visible

Only one ProjectPulse update exists per project at any time, ensuring clarity and avoiding clutter.

---

Boards and Data Used

ProjectPulse uses a parent-child board structure.

Projects Board (Parent)

Each item represents a project.

Used for:

• Posting the weekly ProjectPulse update
• High-level project visibility
• Stakeholder review

Tasks Board (Child)

Each item represents work tied to a project.

Used for:

• Status changes
• Time tracking
• Task-level updates and comments

---

Setup and Deployment

Step 1: Connect the monday.com Integration

In Synthreo Builder, open the ProjectPulse agent and configure the monday.com connection with a valid API token. The token must have read access to board items, updates, time tracking columns, and the ability to create and pin updates on the Projects board.

Step 2: Map the Board IDs

Provide the board IDs for:

• The Projects board (parent) - used for posting the weekly update
• The Tasks board (child) - used for reading task activity, status changes, and logged time

Board IDs can be found in the monday.com URL when viewing a board.

Step 3: Configure the Daily Email Recipients

Set the email addresses that should receive the daily internal update. This is typically the project manager, delivery lead, or a shared team inbox.

Step 4: Configure the Schedule

Set up two scheduled triggers:

• Daily trigger - runs every day at the preferred time (for example 07:00 local time)
• Friday trigger - runs every Friday to generate and post the weekly monday.com update

Both triggers can be managed from the Synthreo Builder scheduler.

Step 5: Validate the Weekly Scope Logic

ProjectPulse always summarizes activity from the current week only. Confirm the week boundary aligns with your team’s working week (Monday to Friday by default). No additional configuration is required unless a custom week definition is needed.

Step 6: Test with a Live Project

Trigger the agent manually against an active project with recent task activity to confirm:

• The daily email is generated and delivered correctly
• The weekly monday.com update is posted and pinned on the correct project item
• The Client Update section contains no internal blocker language

---

Weekly Scope Logic

Even though ProjectPulse runs daily, it always summarizes activity from the current week only.

This prevents:

• Old work from being resurfaced
• Repetition across daily emails
• Bloated weekly summaries

---

Weekly ProjectPulse Update Structure

The Friday monday.com update always contains five fixed sections, in this order:

1. What Happened This Week

A factual summary of completed work, progress made, and meaningful task movement.

This section is driven by:

• Status changes
• Completed tasks
• Logged time
• High-signal updates

2. Blockers

Identifies risks, delays, or constraints affecting progress.

• Written in neutral, professional language
• Focuses on impact, not blame
• Intended for internal visibility

3. Next Steps

Outlines what is expected to happen next based on current task state and momentum.

This helps align teams on immediate priorities.

4. Overall Project Summary

A high-level health snapshot of the project.

This answers the question: “How is this project doing overall?”

It is useful for leadership and high-level stakeholders who do not need task-level detail.

5. Client Update

A client-safe summary of the week.

This section:

• Summarizes progress and outcomes
• Excludes internal blockers and operational issues
• Uses clear, non-technical language
• Is designed to be copied directly into client emails

This same section is also used when sending updates externally.

---

Client Communication Flow

• ProjectPulse generates the Client Update section automatically
• This content is safe for external sharing
• Teams can reuse it for:
  • Client status emails
  • Weekly check-ins
  • Executive summaries

No rewriting is needed.

---

Update Behavior Rules

• Daily runs produce email only
• Friday run produces a monday.com update
• Existing ProjectPulse update is overwritten
• Latest update is always pinned
• Only one ProjectPulse update per project

This keeps reporting clean and predictable.

---

Smart Behavior

ProjectPulse is designed to be practical, not noisy.

It:

• Ignores low-signal or empty updates
• Avoids repeating the same blocker unless it is still relevant
• Prefers real task movement over generic comments
• Separates internal context from client-facing language

---

Usage Example

Scenario: A delivery team is managing three active implementation projects in monday.com. Each project has a Tasks board with items tracked by status (Working on it, Stuck, Done) and logged time.

Daily behavior:

Each morning at 07:00, ProjectPulse runs and emails the project manager a summary such as:

• Two tasks moved to Done yesterday
• One task is marked Stuck with a note about a pending vendor response
• Three tasks are in progress with time logged this week

Friday behavior:

At the end of the week, ProjectPulse posts a monday.com update on the project item with all five sections. The project manager reviews the Blockers and Next Steps sections internally, then copies the Client Update section into the weekly client status email without modification.

---

Troubleshooting

Issue: The daily email is not being received.

Check:

• Confirm the email delivery integration is correctly configured in Synthreo Builder.
• Verify the recipient addresses are entered correctly in the agent configuration.
• Check that the daily scheduled trigger is active and not paused.

---

Issue: The weekly monday.com update is not appearing on the project item.

Check:

• Confirm the Projects board ID is correctly mapped in the agent configuration.
• Verify the monday.com API token has permission to create and pin updates on the Projects board.
• Check the agent run log for errors on the Friday execution.

---

Issue: The Client Update section contains internal blocker language.

Check:

• This may indicate the system prompt has been modified. Review the prompt to confirm the Client Update section is explicitly instructed to exclude internal issues.
• Ensure task updates and comments are written with the understanding that high-signal content will be included in summaries.

---

Issue: ProjectPulse is summarizing activity from previous weeks.

Check:

• Confirm the weekly scope logic is filtering by the current calendar week.
• Verify the agent’s date context is being passed correctly on each run.

---

What ProjectPulse Does Not Do

ProjectPulse is not:

• A task management tool
• A real-time alerting system
• A replacement for detailed project plans

It is built for structured, trustworthy project communication.

---

Best Practices

To get the best results:

• Keep task statuses accurate
• Log time consistently
• Write task updates clearly
• Treat comments as reportable information

Good inputs produce strong summaries.

---

Summary

ProjectPulse provides:

• Daily internal visibility via scheduled emails
• A clean, authoritative weekly project update in monday.com
• A built-in client-ready summary with no internal noise

Once it is set up, project reporting becomes automatic, consistent, and reliable.