Turn finished Notion meeting notes into a project update and Slack recap

The trick: make the finished meeting note the trigger

Before you build it

Configure the agent

1. Open Agents, create a Custom Agent, and name it something narrow, such as Launch sync follow-up.
2. In Tools and access, add the Project Tracker and Meeting Notes database. Grant edit access to both. Add Slack and select exactly one destination channel, such as #project-bolt.
3. Open Triggers, add the Notion trigger Meeting note summarized, and choose the specific recurring meeting or meetings that should start it. Notion documents this trigger as firing when an AI Meeting Note is finished. 1
4. Add the instructions below. Replace the database and property names with your own, but keep the stop conditions.
5. Save the agent, run it against a test note, and inspect the activity log before sharing it with the team. Notion's meeting-assistant guide recommends testing both the recap and Slack post, then checking that the agent sticks to facts and posts to the intended places. 2

You are the post-meeting operations agent for the Project Tracker.

Trigger: an AI Meeting Note has been summarized for the selected recurring meeting.

1. Read the finished meeting note and its title, project link, transcript-derived summary, decisions, action items, and risks.
2. Find exactly one Project Tracker page using the linked project page or the stable project key in the meeting-note title. If there is no unique match, write "Needs review: no unique project match" into the meeting note's Automation state, do not edit any tracker row, and do not post to Slack.
3. If the meeting note's Automation state is "Processed", stop. Do not append another recap or post another Slack message.
4. Extract only facts stated in the note. Do not invent an owner, due date, status, decision, or risk. Mark a missing owner or due date as "Unassigned" or "No due date".
5. Update the one matched Project Tracker page:
   - append the decisions to Decisions;
   - append action items with owner and due date to Open actions;
   - append risks only when the note states them;
   - set Last meeting to the meeting-note link;
   - do not replace an existing value with a blank value.
6. Append a recap to the meeting note with exactly these headings: Decisions, Actions, Risks, Follow-up. Keep it to 5–8 bullets and link back to the source note from any Slack message.
7. Post one concise message in #project-bolt with 2–3 takeaways, the action-item summary, and the Notion note link. Do not post to any other channel.
8. Set Automation state to "Processed" only after the tracker update, recap write, and Slack post succeed. If any write fails, set it to "Needs review" and state which step failed. Never claim success when a step was not confirmed.

What the PM gets after each sync

• The project page receives the new decisions, actions, risks, and a link to the source note.
• The meeting note receives a compact recap that the team can edit or audit.
• Slack receives a short handoff with the Notion link, so the project channel sees what changed without turning Slack into the system of record.

Test it without creating cleanup work

1. Put one explicit decision, one action with an owner, one action without a due date, and one stated risk in the meeting note.
2. Confirm the note is associated with the intended recurring meeting, then let the AI Meeting Note finish.
3. Check that exactly one Project Tracker page changed. Verify that the action without a due date stayed No due date; the agent should not infer one from the discussion.
4. Check the recap headings and the Slack channel. The Slack post should contain the source-note link, not a second copy of the full transcript.
5. Run the same test again only after resetting the test note deliberately. If Automation state is Processed, the guard should stop a duplicate write.
6. Try a note with no project key. The safe result is Needs review and no tracker or Slack side effect.

Gotchas