DailyBot simplifies team collaboration and tasks with chat-based standups, reminders, polls, and integrations, streamlining workflow automation in popular messaging platforms
DailyBot simplifies team collaboration and tasks with chat-based standups, reminders, polls, and integrations, streamlining workflow automation in popular messaging platforms On Nagent, Dailybot is exposed as a fully-configurable team collaboration integration that any agent can call — 6 actions, and API key authentication. No code is required to wire Dailybot into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Dailybot to automate the kinds of tasks team collaboration teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Dailybot into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Dailybot, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DAILYBOT_CREATE_CHECKINTool 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
Check-in name
Indicates if the check-in is active. When true, the check-in will be sent automatically according to its schedule
Date (YYYY-MM-DD format) when the check-in will be finished
Date (YYYY-MM-DD format) that indicates when the check-in will start running
UUID of the template which the check-in will be created with
Weekly frequency to trigger automatic reminders (e.g., 1 for weekly, 2 for bi-weekly)
Indicates if the check-in is anonymous. When true, responses are submitted anonymously
Indicates if the check-in settings can be edited after creation
If true, check-in will not receive automatic reminders and must be triggered manually
Days of the week to send automatic reminders, represented as integers (0=Monday, 6=Sunday)
List of channels where the check-in reports will be sent. Each entry should contain channel information
Custom trigger time for the check-in in HH:MM:SS format (e.g., '08:00:00', '14:30:00')
Total number of additional reminders to send (0-3)
Custom intro message shown at the beginning of the check-in
Custom outro message shown at the end of the check-in
Indicates who can edit the check-in settings (e.g., 'admin', 'all')
Indicates if the check-in reports will be sent one by one as they get completed, rather than waiting for all responses
Interval in minutes for fixed_frequency reminders (only applicable when reminders_trigger_condition is 'fixed_frequency')
Indicate if the check-in uses the user-defined workdays for scheduling reminders
Enum for reminders trigger condition modes.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DAILYBOT_FIND_USERThis 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
The UUID of the user to retrieve information for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DAILYBOT_FIND_WORKFLOWSearches 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
Name of the workflow to search for (case-insensitive)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DAILYBOT_GET_USERSRetrieves 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.
Input parameters
Maximum number of results per page.
Number of results to skip.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DAILYBOT_GIVE_KUDOSThis 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
The text content of the kudos message
List of user UUIDs who will receive the kudos
Whether to give kudos on behalf of DailyBot instead of the API key owner
Whether to give the kudos anonymously
Optional company value to associate with the kudos
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DAILYBOT_SEND_MESSAGEThis tool allows sending a message through DailyBot to either specific users or channels/rooms. The message can include markdown formatting.
Input parameters
List of interactive buttons to add to the message
The content of the message to send. Supports markdown formatting.
URL of an image to include in the message
List of team UUIDs whose members will receive the message
List of user UUIDs who will receive the message
Reserved for public commands that need to interact on behalf of other users
List of channel targets to send the message to
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 90 agents privately built on Nagent that already use Dailybot.
Build on Nagent
Connect Dailybot to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Dailybot, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Dailybot is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Dailybot is connected, you configure its 6 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Dailybot steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Dailybot event fires, the agent kicks off automatically.
Every Dailybot action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Dailybot ships with 6 pre-built team collaboration actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Dailybot together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Dailybot-based workflows tailored to your business.