All jobs

What Happened on My Renovation This Week? A Contractor App Drafts Each Homeowner's Update From the Contractor's monday.com Board

A portal app for renovation contractors makes one agent per contractor that reads its monday.com job board and drafts each homeowner's weekly update.

Run this on RushOpens the console with this prompt ready to send. Connect monday.com there first.

What the agent does

This is for a software company that sells a client portal to residential renovation contractors: kitchen and bath remodelers, roofers, basement finishers. Many of those contractors run their jobs on monday.com, one board per crew or one board for every active job, with a group per project and items for demolition, rough-in, inspection, cabinets, punch list. Homeowners log into the portal and ask the same thing every week: what happened, what is next, what do you need from me. The software company saves one agent as a template that names the monday.com MCP server, with instructions to read and never write, and makes one agent from it per contractor with POST /o/{org}/agents {"template": "<template id>", "name": "updates-<contractor id>"}. Before saving the template, the company connects monday.com to its own account with POST /me/connections {"type": "mcp", "name": "monday", "url": "https://mcp.monday.com/mcp", "auth": {"mode": "oauth"}}.

A contractor's office manager connects monday.com once from the portal's settings. The backend calls POST /o/{org}/agents/{agent}/connections {"type": "mcp", "name": "monday"} and opens the authorize_url in a popup, where the office manager signs in on monday.com's own page. monday.com's docs say an account admin may have to approve an MCP connection the account has not seen before, so the portal's setup guide tells the office manager to ask their admin first. The office manager also maps each portal project to its monday.com board and group.

On a run the agent calls get_board_info for the board's columns and groups, so it knows which column is the status, which is the date and which is the person, by their titles on this board. It pages through the project's items with get_board_items_page, reads the week's comments on each with get_updates, and calls get_board_activity to see which items changed status since last Friday. It writes for the homeowner: what moved to done this week, what is scheduled next week with dates, and anything waiting on the homeowner, such as a tile choice or a payment milestone the board marks, quoted from the item or its comment.

It leaves out what a homeowner should not read: internal notes, crew names other than the lead, supplier prices and margins. The template's instructions name the columns to skip, and the contractor can add more in the portal. The agent posts nothing on the board, changes no column value and sends nothing. It returns one draft per project, and the contractor reads and approves each before the portal shows it to the homeowner.

Start it with one API call

POST https://api.phoenix.so/o/{org}/sessions with this body:

{
  "agent": "<agent id>",
  "input": "Draft this week's homeowner update for project \"Alvarez kitchen\" on board 4512398761, group \"Alvarez - 112 Birch St\", for the week 2026-11-09 to 2026-11-13. Call get_board_info and identify the status, date and person columns by title. Page through the group's items with get_board_items_page, read this week's comments on each with get_updates, and use get_board_activity to find items whose status changed this week. Write for the homeowner, under 200 words: done this week, scheduled next week with dates, and anything waiting on the homeowner, quoting the item or comment it comes from. Skip the columns Internal notes, Supplier cost and Margin, and name no crew member except the project lead. Return only JSON: {draft, waiting_on_homeowner: [string], sources: [{item_id, item_name}]}. Do not create, change, move or comment on anything, and do not send notifications."
}
  1. Get an API key. In the console, open Settings, then API keys, and create a key for your org. Send it in the Authorization header as a Bearer token.
  2. Send the request. POST the body in request.json to https://api.phoenix.so/o/{org}/sessions, with your repository as the resources URL. The run starts in its own cloud sandbox.
  3. Read what came back. Follow the run on its live stream or wait for the run.completed webhook, then read the result and its trajectory.

What comes back

The answer is JSON in the session's result and in the run.completed webhook. The portal puts the draft in the contractor's approval queue with each sentence's source items linked back to monday.com, and the homeowner sees nothing until the contractor approves it.

What the contractor checks: that a date the draft promises is one they still stand behind, that nothing internal slipped through a column the instructions did not name, and the tone of anything the homeowner owes. Editing the draft before approving is normal. When the board was not updated this week, the draft says little, which tells the contractor more than a padded update would.

Run it on every Friday afternoon

The portal's scheduler sends one POST /o/{org}/sessions per active project on Friday at 2 p.m. in each contractor's time zone, with the contractor's agent id as agent, the project's board and group in input, and a request_id that is a UUID v5 of the project id and the week, so a retried job starts no second run. A contractor with twelve active jobs gets twelve runs at once, and runs past the key's concurrent limit wait queued.

A contractor can also press Draft update on one project midweek, after a big day such as a passed inspection, which starts the same request for that project at once.

The use case this job follows, with its automation and trigger: Run an agent per customer task.

Why run it on Rush?

The facts are already on the contractor's board; the office manager's Friday work is turning them into a note a homeowner can read. Each contractor signs in to monday.com on monday.com's page and that sign-in belongs to its own agent: one contractor's run cannot see another's boards, and the software company registers no OAuth app and holds no monday.com token.

One template serves every contractor. When the portal adds a section, such as photos taken this week, one PATCH to the template reaches every contractor's next run. Every run has its own computer and a record of each board, item and comment it read, so a homeowner's question about a sentence can be traced to the item behind it.

Frequently asked questions

Does this use up the contractor's monday.com API limit?

monday.com's docs say each tool call runs as a GraphQL API request and counts toward the account's daily API call limit. One update reads a board's columns, one group's items and their comments, which is a small share of a day's limit for most accounts.

Could the agent change the contractor's board?

monday.com's server has tools that create items, change column values and post updates, and its docs do not describe a read-only mode. The template's instructions and each prompt forbid every one of them, and the transcript would show any such call.

Does the homeowner or the contractor need a Rush account?

No. The contractor signs in to monday.com from the portal, and the homeowner only uses the portal. The agents, their runs and the bill belong to the person who created the software company's API key.

What if a contractor tracks jobs in another tool?

This template names monday.com only. For contractors on another tool Rush lists as an MCP server, such as ClickUp, the company saves a second template with the same instructions and makes each contractor's agent from the one that matches.

More monday.com jobs

More jobs like this: Run an agent per customer task

Keep reading