Keep Slack decisions in Notion

The agency's website launch has a Notion project page, but the decisions keep arriving in Slack. The account team agrees on a smaller first release with the client. The design team debates a new photography plan. A delivery date moves in a reply halfway down a thread. By the next project meeting, the page and the people no longer tell the same story.

Hand the catch-up to a Midpoint worker: "Read these launch threads from this week and write up the decisions for our Notion project page. Link the original discussions, check what is already recorded, and bring me any unclear owner or deadline before changing the page."

You get a proposed update to the page: the decisions, a link to the discussion behind each one, and a short list of questions. The worker does the reading and comparing. The project lead decides what goes on the page.

What the worker reads, and what it leaves alone

You name the threads. For a building-products supplier's website launch, that means the threads on launch scope, copy review and product photography. You also point the worker at the existing Notion project page.

It reads those threads, replies included, and the page. It does not go looking through other channels, and it does not edit anything yet. What it hands back is a proposal, with each change next to its source so the project lead can check it.

If a decision is already on the page, the worker says so and leaves it. You see "already recorded, no change" instead of a second copy of the same entry.

Three things it might bring back

A clear decision. The client's sales team needs usable category pages soon, and the full searchable product catalog isn't ready. The account team and the client agreed that category pages launch first and the catalog moves to a later phase. The proposed entry reads: Launch with category pages. Catalog is phase two. Owner: account lead. Agreed: November 6, 2026, in the client call follow-up. Evidence: link to the thread and the client's reply confirming it. Nothing is left to ask, so this one is ready to approve.

A decision with a hole in it. The client and delivery team agree on a November 19, 2026 launch. But the copy-review deadline is a mess: one person says Wednesday, another says the Friday before launch, and nobody says who signs it off. The worker proposes recording November 19, 2026 as the launch date and lists the copy review as a question, with both messages linked. It does not pick a day for you.

A suggestion that isn't a decision yet. A designer proposed using the supplier's own product photos in place of stock images. Two teammates liked it. The client never answered. The worker files it as "proposed, no client reply" and links the thread, so nobody reads the photography plan as settled.

The project lead gets it all in one place, with agreed decisions, suggestions and open questions kept apart. Every entry keeps its link to the original discussion, so anyone can read how it was decided. Those links also make it easier to check why a record changed later.

When Notion's own Slack connection is enough

Notion's Slack connection can send a message you pick into a Notion database, preview Notion links in Slack, and send notifications. If your job is "save this message as a task or a note", use it. You may not need anything more.

A worker earns its place when the job is bigger: read this week's launch threads, compare them with the project page, and come back with something ready to approve. That takes reading and judgment across several conversations.

What stays with you

Tell the worker to wait until you've reviewed the proposed changes before it writes to Notion. After you approve, it checks the page again, makes only the changes you agreed to and sends you the page link. If someone changed the same entry in the meantime, it brings that back to you instead of writing over their work. If it can't open a thread or the page, or can't make an approved change, it tells you what's missing and keeps the proposal ready. It won't open anything you didn't give it, settle a disputed date or approve a client decision for you.

It also won't keep the page in sync on its own. You hand it a set of threads when you want a review, the way you would hand a colleague a pile of notes before the Monday meeting.

Start here

Connect Slack and Notion to your worker, then send it the thread links and the project page. Ask it to check that it can open all of them before it starts.

Try this:

Here are three Slack threads from the website launch and our Notion project page. First confirm you can open all of them. Then read the threads and compare them with the page. Give me a proposed update: each decision with its owner, deadline and a link to the discussion, anything already recorded, and a list of questions where an owner or date is unclear or a suggestion has no client answer. Don't change the page until I approve. When I do, check the page again first, and if anyone has changed an entry since, show me instead of overwriting it.

Give your Midpoint worker a project review.