# Dailybot

DailyBot simplifies team collaboration and tasks with chat-based standups, reminders, polls, and integrations, streamlining workflow automation in popular messaging platforms

- **Category:** team collaboration
- **Auth:** API_KEY
- **Composio Managed App Available?** N/A
- **Tools:** 7
- **Triggers:** 0
- **Slug:** `DAILYBOT`
- **Version:** 20260223_00

## Tools

### Create Check-in

**Slug:** `DAILYBOT_CREATE_CHECKIN`

Tool to create a check-in based on a template in DailyBot. Use when you need to set up a new recurring check-in (like daily standups, weekly syncs) for a team. The check-in can be scheduled with custom triggers, reminders, and reporting channels.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Check-in name |
| `active` | boolean | No | Indicates if the check-in is active. When true, the check-in will be sent automatically according to its schedule |
| `end_on` | string | No | Date (YYYY-MM-DD format) when the check-in will be finished |
| `start_on` | string | No | Date (YYYY-MM-DD format) that indicates when the check-in will start running |
| `template` | string | Yes | UUID of the template which the check-in will be created with |
| `frequency` | integer | No | Weekly frequency to trigger automatic reminders (e.g., 1 for weekly, 2 for bi-weekly) |
| `is_anonymous` | boolean | No | Indicates if the check-in is anonymous. When true, responses are submitted anonymously |
| `can_be_edited` | boolean | No | Indicates if the check-in settings can be edited after creation |
| `is_trigger_based` | boolean | No | If true, check-in will not receive automatic reminders and must be triggered manually |
| `frequency_on_days` | array | No | Days of the week to send automatic reminders, represented as integers (0=Monday, 6=Sunday) |
| `reporting_metadata` | array | No | List of channels where the check-in reports will be sent. Each entry should contain channel information |
| `custom_trigger_time` | string | No | Custom trigger time for the check-in in HH:MM:SS format (e.g., '08:00:00', '14:30:00') |
| `reminders_max_count` | integer | No | Total number of additional reminders to send (0-3) |
| `custom_template_intro` | string | No | Custom intro message shown at the beginning of the check-in |
| `custom_template_outro` | string | No | Custom outro message shown at the end of the check-in |
| `allow_edit_permissions` | string | No | Indicates who can edit the check-in settings (e.g., 'admin', 'all') |
| `send_reports_one_by_one` | boolean | No | Indicates if the check-in reports will be sent one by one as they get completed, rather than waiting for all responses |
| `reminders_frequency_time` | integer | No | Interval in minutes for fixed_frequency reminders (only applicable when reminders_trigger_condition is 'fixed_frequency') |
| `use_user_defined_work_days` | boolean | No | Indicate if the check-in uses the user-defined workdays for scheduling reminders |
| `reminders_trigger_condition` | string ("smart_frequency" | "fixed_frequency") | No | Enum for reminders trigger condition modes. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Find User by UUID

**Slug:** `DAILYBOT_FIND_USER`

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, birth date, chat platform data, and organization details.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user_uuid` | string | Yes | The UUID of the user to retrieve information for |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Find Workflow by Name

**Slug:** `DAILYBOT_FIND_WORKFLOW`

Searches for a specific workflow in DailyBot by name (case-insensitive match). Returns the complete workflow object including id, name, description, status, created_at, and updated_at fields when found. If no workflow matches the provided name, returns an empty dict. This tool is useful for locating a workflow's ID or details before executing workflow-related operations.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `workflow_name` | string | Yes | Name of the workflow to search for (case-insensitive) |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get All Users

**Slug:** `DAILYBOT_GET_USERS`

Retrieves a paginated list of all users within the authenticated organization from DailyBot. This action requires no input parameters and returns comprehensive user information including: - User identification (UUID, full name, username) - Status information (is_active, bot_enabled) - Work details (role, timezone, occupation, work_days, work hours) - Time off information (timeoff_start, timeoff_end) - Chat platform integration data (user_external_id, external_grid_id) - Organization details The response includes pagination fields (count, next, previous) for navigating large user lists. All users in the organization are returned regardless of their active status or role.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Give Kudos to Users

**Slug:** `DAILYBOT_GIVE_KUDOS`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `content` | string | Yes | The text content of the kudos message |
| `receivers` | array | Yes | List of user UUIDs who will receive the kudos |
| `by_dailybot` | boolean | No | Whether to give kudos on behalf of DailyBot instead of the API key owner |
| `is_anonymous` | boolean | No | Whether to give the kudos anonymously |
| `company_value` | string | No | Optional company value to associate with the kudos |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Send Message

**Slug:** `DAILYBOT_SEND_MESSAGE`

This tool allows sending a message through DailyBot to either specific users or channels/rooms. The message can include markdown formatting.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `buttons` | array | No | List of interactive buttons to add to the message |
| `message` | string | Yes | The content of the message to send. Supports markdown formatting. |
| `image_url` | string | No | URL of an image to include in the message |
| `target_teams` | array | No | List of team UUIDs whose members will receive the message |
| `target_users` | array | No | List of user UUIDs who will receive the message |
| `exchange_token` | string | No | Reserved for public commands that need to interact on behalf of other users |
| `target_channels` | array | No | List of channel targets to send the message to |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |