The agent adds a new deal to the pipeline spreadsheet and updates the corresponding OKR table, ensuring both files are locked and versioned to prevent conflicts.
The agent identifies the relevant pipeline sheet and OKR table within the AgentDocs workspace. It reads the current state of the data to ensure accuracy, then writes the new deal information (e.g., name, stage, value) to the pipeline. Simultaneously, it updates the relevant OKR metrics in the OKR table. The agent leverages AgentDocs' file locking and version history features to commit changes safely as a new version (e.g., v34), ensuring no data is clobbered during the edit.
- Category: Sales and marketing
- Effect: Changes data in your accounts
- MCP servers: AgentDocs MCP (https://koskamo.com/explore/agentdocs-mcp)
- Source: AgentDocs — AI Docs for the agent era (https://getagentdocs.com/)
- Source quote: "Add Lumen to the pipeline as “won”, £12k, and update the Q3 OKR table. agentdocs · sheets.write · 1,900 tok · 0.3s Done. Added Lumen → won (£12,000) to pipeline and bumped “Revenue won” in q3-okrs . Locked both files during the edit; committed as v34."
- Playbook page: https://koskamo.com/explore/use-cases/update-sales-pipeline-and-okrs-in-agentdocs
Prompt: Add Lumen to the pipeline as “won”, £12k, and update the Q3 OKR table.