Auto-Generate Meeting Agendas in Notion

Never spend 10 minutes drafting an agenda again.

Nora pulls pending issues/decisions from Jira/Slack, creates a pre-structured agenda in Notion, and sends calendar invites 24 hours before the meeting.

Twenty-four hours before a scheduled meeting, Nora queries Jira using JQL to find open blockers, unresolved decisions, and action items due this week. It extracts the ticket summaries, assignees, and current statuses. Nora then creates a new page in a designated Notion database. It formats the page with sections for each topic, assigns an owner based on the Jira assignee, and estimates discussion time based on the ticket complexity. Finally, it adjusts the Notion page permissions to share the agenda with meeting attendees.

The operations manager reviews the drafted agenda in Notion. They adjust time allocations if necessary and manually append any sensitive or off-record topics. They spend their prep time reviewing the actual blockers rather than hunting across boards to figure out what needs discussing.

Runs manually triggered, but ideally 24 hours before meeting using Notion and Jira, run by your Operations Manager.

How it works

  1. Trigger on a schedule — Twenty-four hours before the recurring meeting time, Nora wakes up to prepare the agenda. The schedule is maintained by Nora's internal cron system based on your initial conversational request. It requires no manual prompt.
  2. Query Jira for blockers — Nora searches Jira using a specific JQL query to locate open blockers, tasks flagged as high priority, and unresolved issues in the current sprint. It reads the summary, description, assignee, and status for each matching issue.
  3. Pull previous action items — Nora queries Jira again for tasks created during the last meeting that are due this week. It checks if these issues are marked complete or still in progress, gathering the latest comments to provide context.
  4. Handle empty query results — If no blockers or action items match the criteria, Nora still creates the Notion page but leaves the specific sections blank. It adds a note indicating that no urgent Jira issues require discussion this week.
  5. Create the Notion agenda — Nora creates a new page in your meeting Notion database. It applies a structured format using Notion blocks, creating headers for each topic, bulleted lists for context, and assigning an estimated time block based on volume.
  6. Share with meeting attendees — Nora updates the Notion page permissions to share it with the specified attendees. It sends a direct link to the page so participants can review the context and add their own notes before the meeting begins.

What this replaces

Currently, a manager manually prepares the agenda the day before a meeting. They open Jira, filter for blockers, and read through recent sprint activity. They copy the relevant ticket titles and links into a new Notion document. Then, they format the page, guess how long each item will take to discuss, and manually share the link.

Rough estimate rather than a measured figure: about 15 minutes per meeting, based on finding and reading 5-10 Jira tickets and formatting a new Notion page.

What it needs to run

Accounts and plans

Access it asks for

What Nora reads

What Nora writes

When it goes wrong

Who this is for

Worth it if

Not worth it if

A worked example

A 40-person software agency runs a weekly project sync. Nora is instructed to pull Jira issues labeled 'blocker' or 'client-escalation' every Monday at 9 AM and draft an agenda in their 'Weekly Syncs' Notion database.

# Weekly Sync: Oct 24

## Open Blockers (Est. 10 min)
* **[PROJ-402]** Payment gateway timeout on staging (Owner: Sarah Jenkins)
  * *Context:* Failing since Friday deploy. Blocks UAT.
* **[PROJ-415]** Missing design assets for mobile nav (Owner: Marcus T)

## Previous Action Items (Est. 5 min)
* **[PROJ-390]** Finalize Q4 budget (Status: In Progress)

*Note: No client escalations found this week.*

Frequently asked questions

How do I change which Jira issues get pulled into the agenda?

You tell Nora in plain language via chat. If you decide you want to include issues tagged with a specific component or exclude bugs, you send Nora a message explaining the new criteria. Nora updates its internal JQL query for the next run. You do not need to rewrite the query yourself or adjust any settings.

Can Nora take notes during the actual meeting?

This specific automation only prepares the agenda beforehand. Nora cannot join a video call or transcribe live audio. If you want Nora to create follow-up Jira tickets based on meeting outcomes, you can type the decisions into the chat or the Notion page after the meeting, and ask Nora to generate the tickets.

What happens if a Jira ticket is updated after the agenda is created?

Nora creates the Notion page as a static document at the time it runs, which is usually a day before the meeting. It does not maintain a live sync. If a blocker is resolved an hour before the meeting, the Notion page will still list it as open unless you manually edit the document.

Will Nora overwrite my existing Notion meeting templates?

No. Nora creates a completely new page in your designated Notion database for every meeting. It does not edit your existing templates or historical meeting notes. If you want Nora to adopt a different page structure, you describe the preferred layout in chat and it applies that format to future pages.

Connects to

Related automations

Start a 2-week free trial · Browse all automations