Skip to main content
Turn on your Google calendar in the Console, on your Google connection under Connectors. There you choose how your calls are recorded (ask each time, record automatically, or never), which project the recordings go to, and whether you want a briefing before each meeting and a follow-up after recorded ones. The Meetings tab then lists your next calls with a Record button. Your agent works from the same calendar. While you are logged in (ravi login), the daemon reads it every 5 minutes and schedules one-off routines on your default agent:
  • Setup: if you never chose how calls are recorded, the agent asks you once.
  • The day before: when a call asks before recording, the agent asks whether to record it. With briefings on, it also asks what you want out of the meeting.
  • Before the start (30 minutes by default): the agent prepares a briefing from what Ravi knows (contacts, knowledge, earlier meetings with the same people), stores it on the meeting page, and sends you a short version.
  • After the call: when the recording is ready, the agent sends a summary, the decisions and the action items, and offers next steps.
The routines show in ravi cron list with names starting with calendar:. Removing one stops it; it is not scheduled again.

​
Commands

record and settings --record auto print the plan and exit 3 until you add --execute. undo needs --execute only when it clears a skip while recording is automatic.

​
Rules

  • Only you. ravi agenda uses your login, so it runs only on your own turns: the terminal, your direct chat with the agent and your routines. Anywhere else, including a group, it exits 3 with CALENDAR_ACCESS_DENIED.
  • Automatic recording needs your organization to allow it. An owner or admin turns it on in the organization settings in the Console. Calls with people outside the organization are always asked.
  • Several members in one call. The organization sends one bot per meeting, and everyone who had the meeting in their calendar can open the recording. A member’s explicit Record wins; a member’s “don’t record” holds the meeting back unless another member asks to record it.
  • Invites are data. Titles, attendees and briefings come from invites other people write, so the agent reads them as data and never follows instructions in them.

​
Errors