DEV Community

Cover image for How my AI Agent post my daily statndup summary in slack instead of me
Chaitrali Kakde
Chaitrali Kakde

Posted on

How my AI Agent post my daily statndup summary in slack instead of me

#ai #automation #development #productivity

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
Enter fullscreen mode Exit fullscreen mode

Log in to your account:

swytchcode login
Enter fullscreen mode Exit fullscreen mode

Step 2 :Initialize a project 

mkdir standup-bot && cd standup-bot
npm init -y
npm install swytchcode-runtime dotenv
Enter fullscreen mode Exit fullscreen mode

Initialize Swytchcode in the project: 

swytchcode init
Enter fullscreen mode Exit fullscreen mode

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
Enter fullscreen mode Exit fullscreen mode

Fetch them into your project:

swytchcode get clickup
swytchcode get slack
Enter fullscreen mode Exit fullscreen mode

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
Enter fullscreen mode Exit fullscreen mode

Verify they're enabled:

swytchcode list tooling
Enter fullscreen mode Exit fullscreen mode

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
Enter fullscreen mode Exit fullscreen mode

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
Enter fullscreen mode Exit fullscreen mode
  • 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.
Enter fullscreen mode Exit fullscreen mode

Step 8 — Run it 

node standup.js
Enter fullscreen mode Exit fullscreen mode

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

Top comments (0)