Activity API - DailyBot Developers

Push custom activity from any tool into DailyBot via a simple POST request. Track any work in your check-in reports.

Activity API

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

  1. Go to DailyBot Settings → Integrations → Activity API
  2. Copy your unique Activity Hook URL
  3. 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

Name Type Required Description
custom_type string Required Activity identifier (max 128 characters). Used to categorize the activity type.
message string Required Activity details text shown in the report.
link string Optional URL that becomes clickable in DailyBot reports.
user_email string Optional Email of the DailyBot user to attribute the activity to. Use this or user_uuid.
user_uuid string Optional 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

CodeDescription
200Activity recorded successfully
404User email or UUID not found in the organization

Activity Tracking in Reports

  1. Open the check-in settings for the check-in you want to enhance
  2. Go to Sharing → Advanced Options
  3. 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