Reference · built on requestOperator by FibricReporting & analysis

Meeting Prep

Drafts prep notes for a scheduled operations meeting, with current numbers and open items, and proposes them to the attendees' channel.

Request accessPricing ↗

About

An operations meeting starts with someone reading numbers off a screen while everyone else waits. Meeting Prep does that reading beforehand. It finds the meeting on the organizer's calendar through Google Calendar or Microsoft Outlook, takes the attendee list from the event, then pulls the figures the agenda names from BigQuery or Snowflake and the open items assigned to those attendees from Jira or Asana.

Some hours before the start time it drafts a note: each number with its query and as-of time, each open item with owner and due date, and what changed since the last meeting. It proposes the note to the attendees' Slack or Teams channel. A person approves before anything is posted.

This is a reference listing. It documents what Fibric would read from Meeting Prep and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Upcoming events on the organizer's calendar through Google Calendar events.list or Microsoft Graph calendarView, with attendees, description, and start time
  • Query results from BigQuery jobs.query or the Snowflake SQL API for the figures the agenda names
  • Open issues assigned to attendees, found with JQL through the Jira search endpoint, with status and due date
  • Incomplete tasks by assignee and project from the Asana tasks endpoint, with due_on and modified_since
  • The previous prep note it posted, so the draft can show what moved since the last meeting
  • Approve, edit, and dismiss responses on the proposals it posts

Proposed actions

  • Target capability: propose the prep note to the attendees' Slack channel through chat.postMessage, with blocks for numbers and open items
  • Target capability: propose the same note as a chatMessage in a Microsoft Teams channel, when the attendees work there
  • Target capability: propose a comment on each overdue Jira issue asking its assignee for a status line before the meeting
  • Target capability: propose a due-date change on an Asana task an attendee says will slip, for the owner to confirm

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Monday operations review, prepared Sunday night

    The weekly review names four figures in its calendar description. Meeting Prep runs the four queries in BigQuery, lists the open Jira items for each attendee, and proposes the note to the review channel in Slack before anyone logs on.

    With Google Workspace, BigQuery, Jira, Slack

  • Daily standup for a team that works in Teams

    The standup's Outlook invite carries the attendee list. The operator pulls each person's incomplete Asana tasks, adds yesterday's counts from Snowflake, and proposes the note as a chatMessage in the standup's Teams channel.

    With Microsoft Outlook, Asana, Snowflake, Microsoft Teams

  • Chase status before the meeting, not during it

    Two Jira issues on the agenda are past their due date. Meeting Prep proposes a comment on each asking the assignee for one line of status, so the meeting starts with answers.

    With Jira

Requirements

  • A recurring calendar event to prepare for, with the attendees on the invite and the figures named in its description
  • Read access to the warehouse tables the agenda references, through the BigQuery or Snowflake connector
  • A Jira project or Asana project where the attendees' open items live, readable by the connector
  • A Slack channel the app has been added to, or a Teams channel, where the note will be proposed
Authentication
Meeting Prep holds no credentials of its own. It reads calendars, trackers, and warehouse tables through the Google Workspace, Microsoft Outlook, Jira, Asana, BigQuery, and Snowflake connectors you connect, and posts through Slack or Microsoft Teams.

Limits

  • It prepares from what the calendar event names. A figure absent from the description and from every tracker is not in the note.
  • Jira search results can lag recent edits, so an item closed minutes before the draft may still show open.
  • Teams channel messages need a delegated user permission (ChannelMessage.Send). Application-only tokens cannot post outside migration.
  • It drafts and proposes. It does not run the meeting, take minutes, or post without approval.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Meeting Prep ↗

Questions and answers

What does a person approve?
One proposal per meeting: the note itself, shown as it will appear in the channel, with each number's source query and each open item's tracker link. You approve it, edit it, or dismiss it. Comments on overdue issues are separate proposals, one per issue.
What record does it leave?
A receipt per meeting: the calendar event it prepared for, the queries it ran and their as-of times, the tracker items it listed, the note as approved, and who approved it. If you dismiss a draft, the reason you give is kept with it.
Can it post to the channel on its own?
No. Every note and every comment waits for approval. It reads calendars, trackers, and warehouse tables, and writes only through the Slack, Teams, Jira, and Asana connectors after a person says yes.
Ask about Meeting Prep

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy