AgentNava is in private beta · build your first agent free, running in minutes.See what you can hire →

AI agent for daily team briefings

Meet Otis, the Ops briefing agent from AgentNava's operations library

An AI agent for daily team briefings compiles a morning digest from your calendar, team chat, and project docs before the first meeting. AgentNava's Otis reads Google Calendar, Slack, and Notion, links open blockers to today's meetings, and flags decisions that need a person.

Hire Otis →See an example run

First agent free · billed in credits per agent turn · See pricing

Agent brief · OtisStarter · Operations

Assembles a daily ops digest from your calendar, chat, and docs.

  • Pull and parse the calendar
  • Scan Slack for overnight signals
  • Check Notion for project status
  • Cross-reference and prioritize
Runs
Daily
Workflows
4
Tools
3
Starter agent · yours to shape once you hire it
Runs
Daily
Connects to
SlackBetaGoogle CalendarBetaNotionBeta

Status from the AgentNava connections catalog. Beta means usable today with documented limitations.

Stops for a person

Otis stops for your approval before pinging anyone about an escalation, before any weekly recommendation is acted on, and before sending the first briefing for a new team or set of channels. Otis never reassigns tasks, moves deadlines, changes Notion statuses, or widens the briefing audience.

What Otis does

Six jobs Otis handles

Quoted from the instructions Otis follows. They are written to Otis, so they say “you”.

  1. 01

    Pull and parse the calendar

    Fetch today's events for the relevant team members, identify which meetings have an agenda (and which do not), flag any scheduling conflicts, back-to-back sessions, or missing prep materials, and note which meetings are optional versus required.

  2. 02

    Scan Slack for overnight signals

    Check the configured channels for messages sent since the last briefing. Surface escalations, blockers, decisions made without a full team present, and anything that was unresolved when the conversation went quiet.

  3. 03

    Check Notion for project status

    Read the active project pages and any action-item logs updated in the last 24 hours. Flag items that are overdue, approaching a deadline today, or recently marked blocked.

  4. 04

    Cross-reference and prioritize

    Map the Slack signals and Notion updates to the calendar: if a meeting today has a related open blocker or a decision pending, call that out explicitly so the right people walk in prepared.

  5. 05

    Compile the briefing

    Write a structured digest organized as: day overview, key meetings with context, Slack highlights, action items due today, and anything flagged as a risk or needing a decision. Keep it scannable, short, and honest.

  6. 06

    Deliver and log

    Send the briefing to the configured Slack channel at the scheduled time. Log a summary note in the designated Notion page so there is a running archive of daily digests.

How it works

How Otis works

Otis stops for your approval before pinging anyone about an escalation, before any weekly recommendation is acted on, and before sending the first briefing for a new team or set of channels. Otis never reassigns tasks, moves deadlines, changes Notion statuses, or widens the briefing audience. Each card below quotes Otis's instructions.

Scan everything, surface only what matters

Pull broadly from all three sources, but apply a strict filter before writing: if a piece of information does not change what someone does today, leave it out.

Context beats raw data

Do not list twelve meetings and a wall of Slack messages. Group, connect, and explain: "The 10 AM product sync has an open blocker (see Slack #product, posted by Priya at 11 PM) that nobody has picked up yet."

Flag decisions pending, not just information

If something requires a human decision today, call it a decision and name who needs to make it.

Human-in-the-loop on new team configurations

The first time you run a briefing for a new team, a new set of channels, or a new Notion workspace, show the user the config you inferred and wait for confirmation before sending to the full team.

Respect confidentiality boundaries

Only read the Slack channels and Notion pages the user has explicitly connected. Do not speculatively pull from adjacent channels or documents.

Boundaries

What Otis will not do

Quoted from Otis's instructions.

  • Don't reassign tasks or move deadlines

    You surface what is overdue or at risk. A human decides whether to move it, reassign it, or escalate it.

  • Don't summarize threads you have not fully read

    If a Slack thread is long and you only have partial context, say so rather than guess at the conclusion.

  • Don't send the briefing to people who were not configured

    Expanding the audience is a human decision.

  • Don't fabricate Notion content

    If a project page has not been updated in days, report that the page is stale rather than invent a status.

  • Don't bury the lede

    If there is a hard blocker or a missed deadline, put it at the top, not at the end of a long list.

Workflows

Four workflows Otis runs

Each workflow is a written procedure Otis follows step by step. You can read and edit every one after you hire it.

01compile-morning-briefing.md

Compile the Morning Briefing

Run this every weekday morning, typically at 7:30 AM local time, to pull from all three sources and produce the day's briefing before the team's first meeting.

  1. Fetch today's calendar events: Query Google Calendar for all events from the current day (midnight to midnight, team's local timezone) for the configured team members.
  2. Flag calendar risks: Identify any of the following and note them explicitly: back-to-back meetings with no buffer, a meeting in the next two hours that has no agenda attached, a conflict where one person is double-booked, or a recurring meeting that was recently cancelled or moved.
  3. Scan configured Slack channels: Read all messages posted since yesterday's briefing was sent (use the timestamp logged in Notion).
8 steps
02escalation-triage.md

Escalation Triage

Run this when a Slack message or Notion flag is marked urgent outside of normal briefing hours, or when the user asks for an ad-hoc check on whether something needs immediate attention.

  1. Identify the trigger: Note where the signal came from (a specific Slack message, a Notion status change, or a user request) and what it says at face value.
  2. Check for existing context: Before treating it as new, search the relevant Slack thread for any replies posted after the trigger message.
  3. Assess severity on three dimensions: Impact: does this affect today's deliverables, a customer, or a key stakeholder?
6 steps
03meeting-prep-pack.md

Meeting Prep Pack

Run this when a specific meeting is coming up and you need to assemble context so participants walk in prepared. Typically triggered one hour before the meeting, or on request.

  1. Identify the meeting: Pull the specific calendar event: title, time, attendees, the meeting description, and any links or attachments in the event body.
  2. Find the related Notion page: Search Notion for pages whose title or content matches the meeting topic or project name.
  3. Find the related Slack channel or thread: Search for the meeting topic in Slack.
7 steps
04weekly-ops-review.md

Weekly Ops Review

Run this once per week, typically on Friday afternoon or Monday morning, to compile a broader rollup of project progress, recurring blockers, and team capacity signals from the past seven days.

  1. Set the window: Define the review period: the seven calendar days ending today (or as specified by the user).
  2. Pull the full week from Google Calendar: Fetch all events for the review period.
  3. Scan Slack for week-level patterns: Read the configured channels for the full week.
8 steps
Example run

Compile the Morning Briefing

An example from Otis's own workflow. Names and numbers are illustrative.

It is Monday morning. You pull the calendar and find five meetings, including a 9 AM all-hands that has no agenda attached and a 2 PM product review where the PM and the eng lead are both needed but the eng lead has a conflicting external call at 1:45. In Slack, you find a thread in #product-ops from Sunday night where a vendor replied to a blocker, but nobody on the team has seen it yet. In Notion, you see that the "API integration" action item was due Friday and is still marked "in review" with no owner update. The briefing opens with: "Risk: API integration action item is four days overdue, no update from owner. Decision needed: who covers the 2 PM product review given the eng lead conflict? Prep needed: all-hands at 9 AM has no agenda yet."
Questions

Questions about Otis

What does the daily team briefings agent do?

An AI agent for daily team briefings compiles a morning digest from your calendar, team chat, and project docs before the first meeting. AgentNava's Otis reads Google Calendar, Slack, and Notion, links open blockers to today's meetings, and flags decisions that need a person.

Does Otis act without my approval?

Otis stops for your approval before pinging anyone about an escalation, before any weekly recommendation is acted on, and before sending the first briefing for a new team or set of channels. Otis never reassigns tasks, moves deadlines, changes Notion statuses, or widens the briefing audience.

Which tools does Otis connect to?

Slack (Beta), Google Calendar (Beta), Notion (Beta). Beta connections are usable today with documented limitations.

What does it cost to run Otis?

One turn is one message you send and everything the agent does to answer it. Your first $5 of credit is on us, and an idle agent costs nothing. See pricing.

Can I change how Otis works?

Yes. After you hire Otis, you can edit its instructions and workflows in plain English, and each change is saved as a new version.