{"slug": "i-was-tired-of-writing-daily-standups-so-i-built-an-ai-agent-using-claude-code", "title": "I Was Tired of Writing Daily Standups, So I Built an AI Agent using claude code", "summary": "An engineer tired of manually writing daily standup updates built an AI agent using Claude Code that automatically generates and posts summaries of completed work. The system connects ClickUp task data to Slack, fetching tasks updated in the last 48 hours and posting a formatted message with status groupings and assignee details every morning at 10 AM. The developer used Swytchcode to integrate the ClickUp and Slack APIs, eliminating the need to maintain the same information in two separate tools.", "body_md": "For the last few months, I was doing the same thing every single day.\n\nFirst, I would update all my tasks in ClickUp.\n\nThen, before the team standup, I would open Slack and manually write a summary of everything I worked on the previous day.\n\nThe funny part was that all the information already existed in ClickUp. I was basically maintaining the same data in two different places.\n\nSome days it took only a few minutes. On busy days, it felt like another task added to my list.\n\nAfter repeating this process for weeks, I finally decided to fix it.\n\n**Instead of manually writing standup updates every morning, I connected ClickUp to Slack and built a simple workflow that automatically generates and posts a summary of yesterday's work at 10 AM.**\n\nNow the **standup update appears in Slack automatically**, and I don't have to think about it anymore.\n\nSince this saved me time every day, I thought I'd share exactly how I built it.\n\n**Every day at 10 AM:**\n\nWhy I Built This\n\nThe biggest problem wasn't writing the update.\n\nThe problem was context switching.\n\nI was already keeping ClickUp updated throughout the day. Having to open another tool and rewrite the same information felt unnecessary.\n\nI wanted a system where updating ClickUp automatically became my standup update.\n\nNow it does.\n\n**Prerequisites**\n\n```\nnpm install -g swytchcode\n```\n\nLog in to your account:\n\n```\nswytchcode login\nmkdir standup-bot && cd standup-bot\nnpm init -y\nnpm install swytchcode-runtime dotenv\nswytchcode init\n```\n\nSelecting claude means Swytchcode generates an MCP config and a CLAUDE.md contract file in your project — Claude Code can then read it and know exactly which integrations are available and how to call them. Selecting sandbox means all API calls run in test mode so you don't accidentally hit production APIs while building.\n\nFind the ClickUp and Slack integration bundles:\n\n```\nswytchcode search clickup\nswytchcode search slack\n```\n\nFetch them into your project:\n\n```\nswytchcode get clickup\nswytchcode get slack\n```\n\nYou need two methods: one to fetch tasks from ClickUp, one to post a message to Slack.\n\n```\nswytchcode add method list.task.get\nswytchcode add method chat.postmessage.chat.postmessage.create\n```\n\nVerify they're enabled:\n\n```\nswytchcode list tooling\n```\n\nBefore writing any code, check the exact input/output schema for each method:\n\n```\nswytchcode info list.task.get\nswytchcode info chat.postmessage.chat.postmessage.create\n```\n\nThis tells you which fields are required, where they go (path, query, body, header), and what the response shape looks like. No guessing.\n\n```\nCLICKUP_API_KEY=pk_your_clickup_api_key\nCLICKUP_LIST_ID=your_list_id\nSLACK_BOT_TOKEN=xoxb-your-slack-bot-token\nSLACK_CHANNEL=C0XXXXXXXXX\n```\n\nThis is where Swytchcode + Claude really shines. Because you ran `swytchcode init`\n\nwith Claude selected, Claude Code already knows your project's integrations, available methods, and their exact input/output contracts via the `CLAUDE.md`\n\nfile Swytchcode generated.\n\nYou don't need to write the script yourself. Just open Claude Code in your project and paste this prompt:\n\n```\nI want to build a daily standup automation. Here's what it should do:\n\n1. Fetch all tasks from my ClickUp list using the list.task.get method\n2. Filter to tasks updated in the last 48 hours (fall back to all tasks if none match)\n3. Group the tasks by their status (done, in progress, blocked, to do, etc.)\n4. Build a formatted Slack message with emoji per status group, task names as \n   clickable links, and assignee names\n5. Post the message to my Slack standup channel using the Slack API\n\nUse swytchcode-runtime exec() for the ClickUp fetch. Read credentials from .env \n(CLICKUP_LIST_ID, CLICKUP_API_KEY, SLACK_BOT_TOKEN, SLACK_CHANNEL). \nWrite the result to standup.js.\nnode standup.js\n```\n\nA small automation, but it removes a repetitive task that used to happen every single day.\n\nIf you're already using ClickUp and Slack, this is probably one of the easiest productivity automations you can build.\n\nI'm sharing the workflow because I think many teams have the exact same problem and don't realize how easy it is to automate using swytchcode", "url": "https://wpnews.pro/news/i-was-tired-of-writing-daily-standups-so-i-built-an-ai-agent-using-claude-code", "canonical_source": "https://dev.to/chaitrali_kakde_27694f6f9/i-was-tired-of-writing-daily-standups-so-i-built-an-ai-agent-using-claude-code-35g8", "published_at": "2026-05-31 06:01:52+00:00", "updated_at": "2026-05-31 06:11:23.810878+00:00", "lang": "en", "topics": ["ai-tools", "ai-agents", "ai-products"], "entities": ["ClickUp", "Slack", "Claude"], "alternates": {"html": "https://wpnews.pro/news/i-was-tired-of-writing-daily-standups-so-i-built-an-ai-agent-using-claude-code", "markdown": "https://wpnews.pro/news/i-was-tired-of-writing-daily-standups-so-i-built-an-ai-agent-using-claude-code.md", "text": "https://wpnews.pro/news/i-was-tired-of-writing-daily-standups-so-i-built-an-ai-agent-using-claude-code.txt", "jsonld": "https://wpnews.pro/news/i-was-tired-of-writing-daily-standups-so-i-built-an-ai-agent-using-claude-code.jsonld"}}