All jobs

What's Still Open Before the Wedding? A Planner App Drafts Each Couple's Weekly Checklist From the Planner's ClickUp

A wedding-planner app makes one agent per planner that reads each wedding's ClickUp List and drafts the couple's weekly to-do note for approval.

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

What the agent does

This is for a software company that sells a client app to independent wedding and event planners. Many planners run every wedding as its own ClickUp List: vendor bookings, deposits, tastings, fittings, the timeline, the seating chart, each a task with a due date and an assignee, some assigned to the couple. Couples open the app and want one answer each week: what is left, and what is on us. The software company saves one agent as a template that names the ClickUp MCP server, with instructions to read and never write, and makes one agent from it per planner with POST /o/{org}/agents {"template": "<template id>", "name": "checklist-<planner id>"}. Before saving the template, the company connects ClickUp to its own account with POST /me/connections {"type": "mcp", "name": "clickup", "url": "https://mcp.clickup.com/mcp", "auth": {"mode": "oauth"}}.

A planner connects ClickUp once from the app's settings. The backend calls POST /o/{org}/agents/{agent}/connections {"type": "mcp", "name": "clickup"} and opens the authorize_url in a popup, where the planner signs in on ClickUp's own page; ClickUp's server takes OAuth only. The planner then links each wedding in the app to its ClickUp List and says how the couple's tasks are marked: a tag such as couple, or the couple as a guest assignee.

On a run the agent calls clickup_get_list for the List's statuses, so it knows which ones count as done on this planner's setup, and clickup_get_custom_fields to find fields such as Vendor or Deposit due. It calls clickup_filter_tasks on that List for every task not done, with due dates up to the wedding, and clickup_get_task_comments on the tasks due in the next three weeks, where the planner and vendors leave the latest word ("florist sent revised quote, waiting on couple"). Tasks with the couple's tag or assignee go in one section; vendor tasks go in another.

It writes the couple's note in the planner's voice: what the couple owes this week and next, with due dates; what is booked and confirmed; and what is still open with a vendor, without vendor prices or the planner's internal comments. It returns the draft and the tasks behind each line. It updates no task, posts no comment or chat message and deletes nothing, and the planner approves the draft before the couple sees it.

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 checklist for the Nguyen-Park wedding on 2027-05-22, ClickUp List 901412345678. Today is 2026-11-13. Call clickup_get_list for its statuses and treat Complete and Confirmed as done. Call clickup_get_custom_fields for the List. With clickup_filter_tasks, find every task in the List that is not done and is due on or before 2027-05-22. Read comments with clickup_get_task_comments on tasks due by 2026-12-04. Tasks tagged couple are the couple's; the rest are vendor or planner tasks. Write a note under 180 words in a warm, plain voice: what the couple owes in the next two weeks with due dates, what is confirmed, and what is still open with a vendor. Leave out prices, the Deposit amount field and any comment that starts with INTERNAL. Return only JSON: {draft, couple_tasks: [{task_id, name, due}], open_vendor_tasks: [{task_id, name, due}]}. Do not create, update, move, tag, comment on or delete any task, and do not send chat messages."
}
  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 app shows the draft in the planner's approval list, with each task linked back to ClickUp, and the couple sees the note in their app only after the planner approves or edits it.

What the planner checks: that every task the couple owes is really theirs and not one the planner forgot to reassign, that a vendor task listed as open has not been settled by phone, and that nothing internal came through a comment that did not start with the marker. The note reflects the List as it stands; a List not updated this week produces a note that says so in effect, which is a reminder for the planner, not the couple.

Run it on every Friday morning

The app's scheduler sends one POST /o/{org}/sessions per upcoming wedding every Friday at 9 a.m. in the planner's time zone, with the planner's agent id as agent, the wedding's List and date in input, and a request_id that is a UUID v5 of the wedding id and the week, so a retried job starts no second run.

In the last month before a wedding the planner can switch that wedding to twice a week in the app, which sends the same request on Tuesday too. A planner with fifteen weddings gets fifteen runs at once; runs past the key's concurrent limit wait queued and start as earlier ones finish.

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

Why run it on Rush?

The planner already keeps everything in ClickUp; what costs them a Friday is rewriting it fifteen times for fifteen couples. Each planner signs in to ClickUp on ClickUp's page and that sign-in belongs to their own agent, so one planner's run cannot see another planner's Workspace, and the software company registers no OAuth app and holds no ClickUp token.

One template serves every planner, and a change to the note's format is one PATCH that reaches every planner's next run. Every run has its own computer and a record of each task and comment it read, so when a couple asks why a line was in their note, the planner can see where it came from.

Frequently asked questions

Will this run into ClickUp's limits?

ClickUp's docs set MCP limits per Workspace and per client, from 100 calls a day on Free Forever to 1,000 on Business without the Everything AI add-on. One note is a handful of calls, but a planner on a low plan with many weddings can reach the limit; the app can read fewer comments or move busy planners to a higher plan.

Could the agent delete or change a planner's tasks?

ClickUp's tool list includes tools that update tasks and one that moves a task to Trash. The template's instructions and each prompt forbid them, and the transcript would show any such call. ClickUp's own FAQ says it has not added deletion tools, so check its current tool list when deciding how much to trust the prompt alone.

Does the couple need a ClickUp or Rush account?

No. The couple only uses the planner's app. The planner signs in to ClickUp once, and the agents, their runs and the bill belong to the person who created the software company's API key.

Can the note include the timeline for the day itself?

If the planner keeps the run-of-show in a ClickUp Doc, the template can tell the agent to read it with clickup_get_document_pages once the wedding is a few weeks out. The planner should still approve any times a couple will plan around.

More ClickUp jobs

More jobs like this: Run an agent per customer task

Keep reading