惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Recent Announcements
Recent Announcements
V
Visual Studio Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
云风的 BLOG
云风的 BLOG
Microsoft Security Blog
Microsoft Security Blog
博客园 - 司徒正美
Y
Y Combinator Blog
Stack Overflow Blog
Stack Overflow Blog
雷峰网
雷峰网
小众软件
小众软件
GbyAI
GbyAI
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
aimingoo的专栏
aimingoo的专栏
MyScale Blog
MyScale Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
腾讯CDC
A
About on SuperTechFans
宝玉的分享
宝玉的分享
WordPress大学
WordPress大学
B
Blog RSS Feed
G
Google Developers Blog
量子位
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
博客园 - 三生石上(FineUI控件)

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
How I Built an AI Agent with Claude Code That Posts My Da...
Chaitrali Kakde · 2026-05-31 · via DEV Community

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.

What the Workflow Does

Every day at 10 AM:

  • The workflow fetches tasks that were updated in ClickUp yesterday.
  • It collects the latest task statuses and activity.
  • AI generates a clean and readable standup summary.
  • The summary is automatically posted to a Slack channel.

slack automation

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.

How I Built It

Prerequisites

Step 1: Install Swytchcode CLI

npm install -g swytchcode

Log in to your account:

swytchcode login

Step 2 :Initialize a project

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

Initialize Swytchcode in the project:

swytchcode init

swytchcode command

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.

swytchcode-command

Step 3: Search and fetch the integrations

Find the ClickUp and Slack integration bundles:

swytchcode search clickup
swytchcode search slack

Fetch them into your project:

swytchcode get clickup
swytchcode get slack

Step 4 : Enable the methods you need

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

Step 5 : Inspect the contracts

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.

Step 6 : Set up your .env

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

  • 1. To find your CLICKUP_LIST_ID: open a list in ClickUp and copy the ID from the URL — it's the number after /l/.
  • 2. To find your SLACK_CHANNEL ID: right-click the channel in Slack → Copy link — the ID is the last segment.

Step 7 : Ask Claude to write the script

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.

Step 8 — Run it

node standup.js

slack-clickup-atomation

slack - clickup - automation

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

Resources