Personal Ops AI Assistant Template

• What it does: Routes your requests to calendar, comms, or retrieval agents and executes the work through connected tools.
• Best for: founders, operators, busy individuals, exec assistants
• Apps used: Google Calendar, Slack, Notion, File Search, Web Search
• Setup time: 5 to 10 minutes

Personal Ops AI Assistant is a no-code, multi-agent workflow that turns a single message into action. It routes requests to calendar, communication, or information-retrieval agents, then uses connected tools like Google Calendar, Slack, Notion, File Search, and Web Search to schedule, message, and answer questions for you.

---

Problem this solves

• You lose time switching between calendar, chat, docs, and search tabs.
• Small tasks pile up: scheduling, follow-ups, reminders, quick research.
• Your “personal knowledge” is scattered across Notion and PDFs.
• You want one place to delegate work, test it, then deploy it.

---

What this agent does

This template can:

• Create, update, delete, and query calendar events via Google Calendar
• Send and manage messages and reminders in Slack
• Search your uploaded documents with File Search
• Search Notion pages and databases you allow
• Do web research when you ask for external info
• Return a clean, user-ready summary via the Response Agent

---

How it works

1. You ask in plain English (Playground, Telegram, or Slack).
2. Task Router Agent classifies the request: calendar, comms, or retrieval.
3. The request is handed off to the relevant specialist agent.
4. The specialist agent calls the connected tool (Calendar, Slack, Notion, File Search, Web Search).
5. The specialist sends results to the Response Agent.
6. Response Agent replies with the outcome and next steps.

---

Requirements

• Google account with Calendar access (if you want calendar actions)
• Slack workspace access (if you want Slack actions)
• Notion workspace access (optional)
• PDFs or docs to upload (optional, for File Search)
• Web Search enabled (optional, for internet research)

---

Setup guide

1. Click Google Calendar tool node → Connect → authorize.
2. Click Slack tool node → Connect → authorize.
3. Optional: click Notion → Connect and choose the pages or databases to allow.
4. Optional: enable File Search and upload your PDFs and docs.
5. Run Test Workflow with 2 to 3 real prompts.
6. If results look good, publish to Telegram or Slack for daily use.

Common issues and fixes

• Calendar event missing details: specify title, date, time, timezone in your prompt.
• Slack message goes to wrong place: add channel name or user.
• Retrieval feels incomplete: grant access to the right Notion pages, upload more docs, or ask it to use Web Search.

Customization knobs

• Change routing rules in the Task Router Agent.
• Tighten permissions by connecting only the apps you want.
• Add new specialist agents for other tools and workflows.

---

Apps used

(Scopes vary by how you connect each app.)

---

Use cases

• Daily planning: “Block 2 hours for deep work tomorrow morning.”
• Follow-up machine: “Send a Slack reminder to the team about today’s deadline.”
• Meeting logistics: “Find free time next week for a 30-min call with Sarah.”
• Personal knowledge QA: “What did I decide about hiring in my Notion notes?”
• Quick research: “Compare the latest options for X and summarize tradeoffs.”

---

Example prompts and outputs

Example 1: Calendar

Prompt: “Schedule a 30-min ‘Weekly Review’ every Friday at 4pm.”

Output: Event created, recurrence confirmed, next occurrences listed.

Example 2: Slack

Prompt: “Message #ops: ‘Standup moved to 10:15 today.’”

Output: Message sent to the channel with confirmation.

Example 3: Retrieval

Prompt: “Search my PDFs for the renewal clause and summarize it.”

Output: Summary with key terms and where it was found, plus a short next-step suggestion.

---

Why you need this template

• Fewer tabs, fewer context switches.
• One message becomes an action across your tools.
• Faster decisions because your docs and web research are searchable on demand.
• A solid starting point for a personal assistant on an AI workflow automation platform.

---

FAQs

1) Is this an AI agent builder template or a fixed automation?

It is a multi-agent workflow you can edit in AgentSpace, not a rigid if-then chain.

2) Do I have to connect all apps?

No. Connect only what you plan to use. The workflow includes tool nodes, but you control what is connected.

3) Can it read my entire Notion?

Only the pages and databases you allow when connecting Notion.

4) How do I make answers more “personal”?

Upload your docs to File Search, connect the right Notion pages, and give the agent more context in your prompt.

5) What should I say to create a calendar event correctly?

Include title, date, time, timezone, and attendees if needed.

6) Can I run it from Slack or Telegram?

Yes. Publish to a channel you control, or use Playground for testing and daily runs.

7) What if a request spans calendar and Slack?

Ask for the primary outcome in one sentence, or split into two commands. The router picks the best match.

8) What are the main failure modes?

Missing details in prompts, insufficient permissions, or missing source access for retrieval. Fix by adding details and tightening allowed scopes.

9) Can I add more agents?

Yes. Add specialist agents for additional tools, then adjust routing.

10) Where does “response formatting” happen?

The Response Agent synthesizes outputs from the other agents and replies to the user.