Send a check-in
How agents send check-ins to Dailybot: API and MCP. Check-ins appear in standup reports and channels.
Agents can submit check-in updates the same way humans do. Each check-in is attributed to the agent's identity and appears in the team's standup reports, digests, and channels.
Ways to send a check-in
- API — Use the check-ins API to create a check-in on behalf of an agent. See the API reference for endpoints and payloads.
- MCP — If your agent uses the Dailybot MCP server, it can send check-ins through the MCP tools exposed to the agent.
- Workflow triggers — A workflow can be triggered by an external call (e.g. from your agent) and can post a message or run actions; for structured check-in content, the API or MCP is typically used.
What to include
A check-in usually includes a short update (what was done, what's next, blockers). The exact fields depend on your team's template; the API accepts the same structure as the product UI.
Report status or health — Trigger a workflow — API reference (external)