Building a Timekeeper Agent: A Consultant's OS on the Microsoft Stack

This is a sophisticated "Consultant's OS" build. Since you work in the Microsoft stack, we will use Power Automate as the "Glue," Notion as the "Brain," and Clockify as the "Safety Net" for those deep-work hours that don't leave a paper trail in Outlook.

1. The Architectural Blueprint

We are creating a data funnel. All external activity flows into a Notion "Stage" Database, where you review it via a Teams Adaptive Card before the final "Post" to Ruddr.

2. Step 1: Notion Database Design

You need three specific databases to make this work without manual mapping.

A. The "Project Rules" Database (The Logic)

• Name (Title): Client/Project Name.
• Ruddr Project ID (Text): The UUID from Ruddr.
• Clockify Project ID (Text): The ID from Clockify (to keep names synced).
• Keywords (Multi-select): "Power Pages", "Migration", "SharePoint".

B. The "Activity Stage" Database (The Daily Log)

• Activity (Title): Subject of email/meeting.
• Source (Select): Outlook, Notion, Clockify.
• Duration (Number): Hours.
• Status (Select): Draft, Approved, Pushed to Ruddr.

3. Step 2: The Power Automate Design

You will create two flows to handle your specific scheduling requirements.

Flow 1: The Aggregator (The "Pull")

• Triggers:
  • Schedule 1: Daily at 8:30 AM (Recurrence).
  • Schedule 2: Friday at 6:00 PM (Recurrence).
• Action - Pull Outlook: "Get events (V2)" and "Get emails (V3)" for the past 24 hours.
• Action - Pull Notion: "Query database" (Meetings) filtered by date.
• Action - Pull Clockify: Use an HTTP Action to the Clockify API:
  • GET https://api.clockify.me/api/v1/workspaces/{workspaceId}/user/{userId}/time-entries
• Action - The Merge: Loop through each source and "Create Page" in your Notion Activity Stage database.

Flow 2: The Approver (The "Push")

• Trigger: When a page is updated in Notion (Status changed to Approved).
• Action: "Post adaptive card and wait for a response" in Teams.
• Action - Ruddr Push: If Approved, use an HTTP Action to POST the data to Ruddr.

4. Step 3: Copilot Design (VS Code and GitHub Copilot)

To maintain this system, use GitHub Copilot Chat in VS Code as your "DevOps Assistant."

1. Context Loading: Open your Notion API documentation and Ruddr API docs in VS Code tabs.
2. The Prompt:

   "I am building a Power Automate HTTP request to the Ruddr API. Based on the documentation in my open tab, write the JSON schema for a 'Create Time Entry' POST request. Map these variables: ProjectID, Date, Duration, and Note."

3. MCP Integration: If you use the Notion MCP, you can ask Copilot: "Read my Project Rules database and tell me if any entries are missing a Ruddr Project ID."

5. Clockify Configuration: The "Safety Net"

To avoid multiple inputs, configure Clockify to be passive:

• Auto-Track: Use the Clockify desktop app's "Auto Tracker." It records which apps you used (e.g., "Visual Studio Code" or "D365 Admin Center").
• Integration: Enable the Clockify-to-Notion browser extension. When you are on a Notion meeting note, you can click "Start Timer" inside Notion; this ensures the Clockify entry is pre-tagged with the Notion Project.

6. Guidance: How to Make Tools "Compliment" Each Other

The secret to "No Multiple Inputs" is Hierarchy of Truth:

1. Notion is the Master: If a project exists, it must start in Notion.
2. Naming Convention Sync: Use the exact same name for the project in Notion, Clockify, and Ruddr.
   • Tip: Use a Power Automate flow that triggers when a "New Project" is added to Notion to automatically create that project in Clockify via API.
3. The "Keyword" Strategy: In your Notion Rules, add a property called Email Domain.
   • Example: If an email comes from @client-a.com, the Power Automate agent automatically maps it to "Project A" without you typing a word.

Your Next Step to Building This

Start by obtaining your API Keys. You will need:

1. Notion: Internal Integration Token.
2. Clockify: API Key (found in Profile Settings).
3. Ruddr: Member API Token.