Dailybot
DailyBot simplifies team collaboration and tasks with chat-based standups, reminders, polls, and integrations, streamlining workflow automation in popular messaging platforms
Verdict
Common use cases
- Pull standup responses before morning sync
- Send kudos after a successful deploy
- Check who submitted check-ins today
- Find workflow status for sprint retrospectives
- Message team channels from AI conversations
Integration
- Vendor
- Dailybot
- Category
- other
- Auth
- API_KEY
- Tools
- 6
- Composio slug
dailybot
Tools
- Find User by UUID
This tool allows you to find and retrieve information about a specific user in dailybot. it uses the provided user uuid to lookup the user and returns detailed information including the user's uuid, full name, image, username, occupation, b
- Find Workflow by Name
This tool allows users to find a specific workflow within dailybot by providing the workflow name. it returns detailed information including the workflow id, workflow name, workflow status, workflow type, created at, and updated at. it is e
- Get All Users
This tool retrieves a list of all users within the organization from dailybot. it doesn't require any input parameters other than authentication. the returned json contains user details including uuid, active status, full name, and organiza
- Get Workflows List
This tool retrieves a list of all workflows that the authenticated user has access to in dailybot. it can be executed independently with only the authentication required, and it supports optional pagination parameters (page, per page) to re
- Give Kudos to Users
This tool allows giving kudos to one or multiple users in dailybot. kudos can be given either on behalf of dailybot or the api key owner.
- Send Message
This tool allows sending a message through dailybot to either specific users or channels/rooms. the message can include markdown formatting.
Setup
Setup guide
- 11. In Dailybot, navigate to Settings > Integrations > API and generate a new API key with read/write permissions. 2. Copy the key to your clipboard. 3. In Switchy, open your workspace settings and click 'Add MCP Integration'. 4. Select Dailybot from the list. 5. Paste your API key into the authentication field and click 'Connect'. 6. Switchy confirms the connection by fetching your user list. 7. Open any Space and type '@Dailybot get workflows list' to verify the integration works. 8. If you see your active workflows, the setup is complete. 9. To test messaging, try '@Dailybot send message to #general with text: Test from Switchy'. 10. Revoke the API key in Dailybot settings if you need to disconnect.
What teammates see: by default, memories from Dailybot are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Summarize Today's Standups
@Dailybot get workflows list and show me which workflows had responses submitted today, then summarize the key updates from each team member.Open in a Space →
Recognize Top Contributors
@Dailybot give kudos to users who closed the most tasks this week. Check our workflow data and send recognition messages to the top three contributors.Open in a Space →
Find Missing Check-Ins
@Dailybot get all users and compare against today's standup workflow submissions. List anyone who hasn't checked in yet.Open in a Space →
Broadcast Sprint Kickoff
@Dailybot send message to #engineering with text: Sprint 47 starts Monday. Focus areas: API refactor, mobile bug fixes, analytics dashboard. Daily standups at 9:30am.Open in a Space →
Audit Workflow Activity
@Dailybot find workflow by name 'Daily Standup' and show me the status, last response date, and how many team members are participating.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Dailybot show me all active workflows and their current status, then summarize which ones are running daily check-ins
Found 8 active workflows in your DailyBot workspace. Daily check-ins: 'Engineering Standup' (active, 47 responses this week), 'Sales Pipeline Update' (active, 22 responses), 'Customer Success Check-in' (paused). Other workflows include 'Weekly Retrospective', 'Onboarding Survey', 'Mood Tracker', 'Sprint Planning', and 'Incident Report'. The two daily standups account for 73% of your team's workflow activity. Engineering Standup runs at 9 AM UTC; Sales Pipeline at 10 AM UTC.
This example combines the Get Workflows List tool with AI synthesis to surface patterns. Requires read access to workflows via API key. Response reflects the state at query time—workflow statuses and participation rates change frequently, so treat this as a snapshot rather than a static report.
@Dailybot send kudos to Sarah Chen and Marcus Lee for shipping the payment integration ahead of schedule
Kudos sent successfully to 2 users. Sarah Chen (uuid: a3f7...) and Marcus Lee (uuid: b8c2...) will receive notifications in their DailyBot feed and connected Slack workspace. The kudos message 'Shipped the payment integration ahead of schedule' is now visible to your team. This recognition will appear in their individual kudos history and count toward monthly team recognition metrics.
Demonstrates the Give Kudos tool, which creates visible team recognition. The API key owner is recorded as the kudos sender unless you specify 'on behalf of DailyBot'. Requires user UUIDs or email lookups—if you reference teammates by name, the MCP will attempt to resolve them via the Find User tool first. Side-effect: notifications are sent immediately.
@Dailybot find all users who haven't responded to the Engineering Standup workflow in the past 3 days and draft a friendly reminder message
Identified 4 users with no Engineering Standup responses since January 20: Alex Kumar, Jordan Park, Taylor Wong, Priya Desai. Draft reminder: 'Hey team! Just a friendly nudge—we haven't seen your standup updates in a few days. Your input helps the team stay aligned, even if it's a quick 'no blockers today'. Drop your update when you get a chance. Thanks!' Note: This is a draft only. Use the Send Message tool separately if you want to deliver it via DailyBot channels.
Combines Get Workflows List (to identify the standup), Get All Users (to cross-reference participants), and AI reasoning to detect gaps and generate copy. The MCP cannot directly query 'who missed responses'—the AI infers this from available workflow metadata. Requires read access to users and workflows. No messages are sent unless you explicitly invoke Send Message afterward.
Use-case deep-dives
When Dailybot MCP makes sense for distributed check-ins
A 6-person remote engineering team runs daily standups through Dailybot's Slack workflows. The MCP lets them query standup responses directly in Switchy—useful when a PM wants to pull yesterday's blockers into a planning doc or a lead needs to spot patterns across the week without opening Slack. The workflow lookup and user tools make this fast. The trade-off: if your team only uses Dailybot for standups and nothing else, you're adding an integration for a narrow slice of data. This MCP wins when you're already invested in Dailybot's workflows and want to surface that context in team docs or retrospectives without tab-switching.
Using the MCP to automate recognition workflows
A 12-person customer success team uses Dailybot to track peer kudos as part of their quarterly review process. The MCP's 'Give Kudos' tool lets them build a Switchy workflow that prompts managers to recognize direct reports after closed tickets, then logs the kudos automatically. The user lookup tool ties kudos back to UUIDs for reporting. This works if your team already treats Dailybot as the system of record for recognition—if kudos live in Slack reactions or a separate tool, the MCP doesn't help. The buying call: if you're running structured recognition programs through Dailybot and want to reduce manual data entry, this integration saves 10-15 minutes per manager per week.
When to use the MCP for multi-team coordination
A 20-person product org runs separate Dailybot workflows for design, engineering, and marketing. A product lead uses the MCP in Switchy to pull workflow status across all three teams into a single weekly sync doc—no need to jump between Dailybot dashboards or ask each lead for updates. The 'Get Workflows List' and 'Find Workflow by Name' tools make this a 2-minute task instead of a 20-minute Slack thread. The threshold: if your workflows are simple (just standups, no custom forms or multi-step approvals), the MCP might be overkill. This integration shines when you have 3+ active workflows and need a single pane to monitor them without leaving your shared workspace.
Frequently asked
What does the Dailybot MCP do in Switchy?
It lets AI agents read your Dailybot workflows, send kudos, and post messages to users or channels. The MCP pulls user lists, searches workflows by name, and can message on behalf of Dailybot or the API key owner. Useful for automating standup follow-ups or recognizing team wins without opening Dailybot.
Do I need admin access to connect Dailybot?
You need a Dailybot API key, which typically requires workspace admin or owner permissions to generate. The key authenticates all requests, so whoever connects it controls what the AI can read and send. Check your Dailybot settings under Integrations or API to confirm you can create keys.
Can the MCP create or edit Dailybot workflows?
No. It can list workflows and search them by name, but it can't create, modify, or delete workflows. If you need to change workflow logic or schedules, you still do that in Dailybot's UI. The MCP is read-only for workflows, write-enabled only for messages and kudos.
Why use this instead of Dailybot's Slack integration?
Dailybot's Slack bot posts standup reminders and collects responses. This MCP lets AI agents query workflow data and send targeted messages based on context from other tools—like kudos after a GitHub PR merge. Use both: Slack integration for scheduled standups, MCP for conditional automation across your stack.
Does Dailybot MCP usage count against my plan limits?
API calls made through the MCP count against Dailybot's rate limits, not Switchy's. Dailybot plans typically cap API requests per hour or day. If your team runs many automated workflows, check your Dailybot plan's API quota. Switchy doesn't meter Dailybot calls separately.