The Account Status Agent processes customer meeting recordings from Grain and automatically updates your Notion account tracking database with structured notes on deal health, competitive intelligence, feature requests, and follow-up items. After each round of customer calls, every participating company's Notion page reflects the latest stakeholder context, technical requirements, and open action items — extracted directly from the full transcript, not from AI summary blurbs.

The result is an account database that stays current without any manual note-taking, giving SEs and AEs a reliable source of truth before every call.

Paste one prompt into Warp and the agent deploys itself:

Set up Grainiac: clone https://github.com/warpdotdev/account-status-agent-oss.git
if it isn't already cloned, then read the grainiac-setup skill in the repo and
follow its instructions.

The setup skill walks through everything interactively: cloning, Oz CLI auth, Notion configuration, secrets, environment creation, a test run, and an optional daily schedule.

Or set it up manually:

1. Set up Notion

Create an account-tracking database and share it with a Notion integration, then note the integration token (GRAINIAC_NOTION_TOKEN) and the database ID from its URL (GRAINIAC_NOTION_DATABASE_ID).

2. Add secrets

Authenticate the Oz CLI with oz login (or set WARP_API_KEY for CI), then register the secrets. Warp injects team secrets into cloud runs as environment variables; each command prompts for its value securely:

oz secret create --team GRAINIAC_GRAIN_TOKEN
oz secret create --team GRAINIAC_NOTION_TOKEN
oz secret create --team GRAINIAC_NOTION_DATABASE_ID
oz secret create --team GRAINIAC_INTERNAL_DOMAIN

3. Create the environment

The orchestrator discovers the environment by its exact name, so it must be named grainiac:

oz environment create --team \
  --name grainiac \
  --repo <owner/repo> \
  --docker-image warpdotdev/dev-base:latest

4. Run and schedule

Trigger a manual run to verify the wiring, then schedule it daily so every morning starts with updated account pages:

oz agent run-cloud \
  --environment <ENV_ID> \
  --prompt "Read the grainiac-orchestrator skill for instructions. Process today's meetings."

oz schedule create \
  --name "Grainiac Daily" \
  --cron "0 5 * * *" \
  --environment <ENV_ID> \
  --prompt "Read the grainiac-orchestrator skill for instructions. Process today's meetings."

Configure the Notion database structure using the included account template, which tracks stakeholders, tech stack, current tooling, requirements, use cases, commercial context, and a POC/pilot tracker. The agent updates each section surgically, appending to chronological timelines without overwriting existing notes.

Grain for meeting recording access, participant data, and full transcript retrieval. Notion for account page creation and structured content updates — tracking stakeholders, tech stack, requirements, use cases, deal status, competitive mentions, and sentiment.

Oz for scheduled and on-demand cloud agent execution. The per-meeting child agent architecture means large batches of daily meetings are processed in parallel — one agent per company — so a day with ten customer calls completes in roughly the same time as a day with two.