[ monday.com / PMO ]

Weekly status reports, written from your boards

Every week, engini has an AI agent read your monday.com project boards, their status columns, dates and recent updates, plus Jira issues or budget figures where you track them, and write the portfolio summary: what is at risk, what slipped, what is blocked and why. It posts the report to Slack or Teams and the board, and flags slipped dates as they happen.

monday.comJiraSlackGoogle Sheets
Read the monday.com guide →
Friday, 3 pm
  1. Every Friday at 15:00schedule trigger
  2. monday.com logo
    Read project boardsstatus, timeline, owners, this week’s updates
  3. Read Jiraopen blockers by project
  4. Agent writes the report3 at risk, 2 slipped, 1 blocked
  5. Slack logo
    Posted#leadership and a summary item
Illustration of the flow on this page, not a product screen.
What it does
A weekly portfolio report written from boards, Jira and budget data
Systems
monday.com, Jira, your ERP or a sheet for budgets, Slack or Teams
Built with
A scheduled workflow with an AI agent step, plus an item-update trigger
Your control
Which boards, what counts as at risk, where the report goes
[ 01 / The problem ]

Friday afternoons go to writing status reports

Every project manager knows the routine: open each board, read the updates, check the dates, ask a few people what is really going on, then write it up for leadership. In a portfolio management report produced with monday.com, managers named tracking and reporting among their main pain points (The Digital Project Manager).

Dashboards help with the numbers, but leadership wants the story: which projects are at risk, why, and what is needed to fix them. Writing that story is the part nobody has time for.

What goes into a status report

  • Status and timeline columns across several boards.
  • The week’s updates, where the real news is.
  • Blockers tracked in Jira by engineering.
  • Budget versus actuals from the ERP or a finance sheet.

Let the agent write the first draft

A scheduled engini workflow reads the items on each project board, their status, dates and owners, and the updates posted this week. It reads blocked Jira issues and, if you track them, budget figures from a sheet or your ERP. An AI agent step writes the summary in your format: at risk, slipped, blocked, decisions needed.

The report is posted to Slack or Teams and saved as an update on a summary item. A second workflow triggers on item updates and flags a slipped date the moment it happens, so Friday holds no surprises. Leaders can also ask Claude or ChatGPT about the portfolio through an engini MCP server with read-only board tools.

[ 02 / How it works ]

Read every board, write one report

01 / Schedule

Every week

A scheduled workflow runs at the time you choose, for example Friday at 15:00.

02 / Gather

Boards, Jira, budget

It reads items, status, dates, owners and this week’s updates across your project boards, plus Jira blockers and budget figures.

03 / Write

The summary

An AI agent step writes the portfolio report in your format: at risk, slipped, blocked, decisions needed.

04 / Share

Where people read it

It posts to Slack or Teams and to a summary item. An item-update trigger flags slipped dates during the week.

[ 03 / What the agent reads and writes ]

What the agent reads and writes

SystemRecordsAccess
monday.comBoards, items, status and timeline columns, updatesRead
monday.comThe report as an update on a summary itemCreate
JiraBlocked and overdue issues by projectRead
Google Sheets, Excel or your ERPBudget and actualsRead
Slack or TeamsThe weekly report and slip alertsWrite
[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the monday.com logo, the engini mark and a frosted tile joined by a thin line, labeled every Friday: boards, blockers, report

Editorial image: the week, summarized.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: every Friday at 15:00, read all items and this week's updates from my monday.com boards "Project Alpha", "Project Beta" and "Project Gamma", write a short status report listing projects at risk, items whose dates slipped, and blockers mentioned in updates, and post it to #leadership in Slack.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect monday.com, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can monday.com status reports be written automatically?

Yes. A scheduled engini workflow reads your boards and an AI agent step writes the report in your format, then posts it where you want it.

Can it combine monday.com with Jira or budget data?

Yes. The same workflow reads Jira issues and budget figures from a sheet or your ERP, so the report covers delivery and money.

Where does the report go?

To Slack or Teams, and as an update on a summary item on monday.com. It can also be saved to a sheet.

How is this different from monday dashboards and monday agents?

Dashboards show numbers. monday’s agents work inside monday.com. engini writes the narrative from monday.com, Jira and your finance data together.

Can executives ask questions about the portfolio?

Yes, through an engini MCP server with read-only board tools added to Claude or ChatGPT.