cd /news/ai-tools/i-was-tired-of-writing-daily-standup… · home topics ai-tools article
[ARTICLE · art-18986] src=dev.to pub= topic=ai-tools verified=true sentiment=↑ positive

I Was Tired of Writing Daily Standups, So I Built an AI Agent using claude code

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.

read3 min publishedMay 31, 2026

For the last few months, I was doing the same thing every single day.

First, I would update all my tasks in ClickUp.

Then, before the team standup, I would open Slack and manually write a summary of everything I worked on the previous day.

The funny part was that all the information already existed in ClickUp. I was basically maintaining the same data in two different places.

Some days it took only a few minutes. On busy days, it felt like another task added to my list.

After repeating this process for weeks, I finally decided to fix it.

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.

Now the standup update appears in Slack automatically, and I don't have to think about it anymore.

Since this saved me time every day, I thought I'd share exactly how I built it.

Every day at 10 AM:

Why I Built This

The biggest problem wasn't writing the update.

The problem was context switching.

I was already keeping ClickUp updated throughout the day. Having to open another tool and rewrite the same information felt unnecessary.

I wanted a system where updating ClickUp automatically became my standup update.

Now it does.

Prerequisites

npm install -g swytchcode

Log in to your account:

swytchcode login
mkdir standup-bot && cd standup-bot
npm init -y
npm install swytchcode-runtime dotenv
swytchcode init

Selecting 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.

Find the ClickUp and Slack integration bundles:

swytchcode search clickup
swytchcode search slack

Fetch them into your project:

swytchcode get clickup
swytchcode get slack

You need two methods: one to fetch tasks from ClickUp, one to post a message to Slack.

swytchcode add method list.task.get
swytchcode add method chat.postmessage.chat.postmessage.create

Verify they're enabled:

swytchcode list tooling

Before writing any code, check the exact input/output schema for each method:

swytchcode info list.task.get
swytchcode info chat.postmessage.chat.postmessage.create

This tells you which fields are required, where they go (path, query, body, header), and what the response shape looks like. No guessing.

CLICKUP_API_KEY=pk_your_clickup_api_key
CLICKUP_LIST_ID=your_list_id
SLACK_BOT_TOKEN=xoxb-your-slack-bot-token
SLACK_CHANNEL=C0XXXXXXXXX

This is where Swytchcode + Claude really shines. Because you ran swytchcode init

with Claude selected, Claude Code already knows your project's integrations, available methods, and their exact input/output contracts via the CLAUDE.md

file Swytchcode generated.

You don't need to write the script yourself. Just open Claude Code in your project and paste this prompt:

I want to build a daily standup automation. Here's what it should do:

1. Fetch all tasks from my ClickUp list using the list.task.get method
2. Filter to tasks updated in the last 48 hours (fall back to all tasks if none match)
3. Group the tasks by their status (done, in progress, blocked, to do, etc.)
4. Build a formatted Slack message with emoji per status group, task names as 
   clickable links, and assignee names
5. Post the message to my Slack standup channel using the Slack API

Use swytchcode-runtime exec() for the ClickUp fetch. Read credentials from .env 
(CLICKUP_LIST_ID, CLICKUP_API_KEY, SLACK_BOT_TOKEN, SLACK_CHANNEL). 
Write the result to standup.js.
node standup.js

A small automation, but it removes a repetitive task that used to happen every single day.

If you're already using ClickUp and Slack, this is probably one of the easiest productivity automations you can build.

I'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

── more in #ai-tools 4 stories · sorted by recency
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/i-was-tired-of-writi…] indexed:0 read:3min 2026-05-31 ·