Activity API guide
The Activity API lets you push custom activity from any external application into Dailybot. Use it to track work from tools that don’t have a native Dailybot integration — activity is displayed in check-in reports alongside data from other integrations.
Billing requirement: Your organization must have a billing plan that supports APIs and integrations to use the Activity API.
Getting started
- Go to Dailybot Settings → Integrations → Activity API
- Copy your unique Activity Hook URL
- Use this URL as the target for POST requests from your application
POST request
Send a POST request with Content-Type: application/json to your Activity Hook URL.
Request fields
| Field | Type | Required | Description |
|---|---|---|---|
custom_type |
string | Yes | Activity identifier (max 128 characters). Used to categorize the activity type. |
message |
string | Yes | Activity details text shown in the report. |
link |
string | No | URL that becomes clickable in Dailybot reports. |
user_email |
string | No | Email of the Dailybot user to attribute the activity to. Use this or user_uuid. |
user_uuid |
string | No | UUID of the Dailybot user to attribute the activity to. Use this or user_email. |
Identify the user with either user_email or user_uuid. At least one is required to attribute the activity to a team member.
Example request
curl -X POST "https://your-activity-hook-url/" \
-H "Content-Type: application/json" \
-d '{
"custom_type": "deployment",
"message": "Deployed v2.1.0 to production",
"link": "https://github.com/org/repo/releases/tag/v2.1.0",
"user_email": "developer@company.com"
}'Response codes
| Code | Description |
|---|---|
200 |
Activity recorded successfully |
404 |
User email or UUID not found in the organization |
Activity tracking in reports
- Open the check-in settings for the check-in you want to enhance
- Go to Sharing → Advanced Options
- Enable Activity tracking
Activity logged within 24 hours before a check-in response through the end of that day appears as an automatically added column in reports.
Use cases
- Deployments — Log deployment events with version and environment details
- Support tickets — Track resolved support tickets per team member
- Design tools — Push activity from Figma, Sketch, or other design tools
- Custom scripts — Integrate with CI/CD pipelines, monitoring systems, or internal tools
- Zapier / Make — Use the Activity Hook URL as a webhook destination in automation platforms
