Send a check-in
How agents send check-ins to Dailybot — API, MCP, workflows, and auto-standup population from coding agent activity.
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.
Auto-standup from agent activity
When a coding agent is connected to Dailybot, it can pull recent activity summaries — commits, pull requests, and progress notes — and pre-populate standup-style check-in answers. You always review and submit; nothing posts as your final standup without your action unless your org configured otherwise.
How it works
- Connect your coding agent or development tool to Dailybot using the in-product Integrations or Agents flow your admin provides.
- Authorize the scopes requested so Dailybot can read activity metadata (not necessarily full private code).
- Wait for the connection to show Active in Dailybot settings.
- When a scheduled standup check-in opens, look for Suggested answers, Draft from activity, or pre-filled text in the question fields tied to work logs.
- Read the draft. Remove anything inaccurate, add context the agent could not see (meetings, pairing, outages), and fix tone.
- Submit the check-in as usual. Only submitted content appears in compiled reports.
What gets captured
| Source type | Often included |
|---|---|
| Version control | Commit messages, branches touched, repos |
| Code review | PR titles, review activity, merge status |
| Agent session | Summaries the agent recorded if your setup sends them to Dailybot |
Sensitive files and private snippets are not required; Dailybot uses summaries your integration is designed to share. If something looks wrong, disconnect or narrow scopes with your admin.
Review before submitting
Auto-population saves typing; it does not replace judgment. Treat drafts as starting text: delete hallucinated tasks, merge duplicate lines, and add blockers the tool cannot infer.