Activities

Activities capture all interactions and engagements with customer accounts in the Thena platform, providing a comprehensive timeline of customer relationships.

Understanding activities

Core purpose

Activities provide a structured way to track, manage, and analyze all customer interactions. They help maintain a complete history of engagements and ensure proper follow-up on customer communications.

Activity types

Communication activities

• Meetings: In-person or virtual
• Calls: Phone conversations
• Emails: Email threads
• Chat: Instant messaging

Business activities

• Site visits: On-premise meetings
• Reviews: Performance discussions
• Presentations: Product demos
• Training: Customer education

Standard fields

Required fields

Name	Type	Options	Comments
Account ID	string	Required	Associated account identifier
Activity Timestamp	timestamp	Required	When the activity occurred
Duration	integer	Required	Length of activity in minutes
Location	string	Required	Physical or virtual location

Optional fields

Name	Type	Options	Comments
Type	string	Optional, Values: [CALL (default), EMAIL, MEETING, SITE_VISIT]	Activity type reference
Status	string	Optional, Values: [PENDING (default), COMPLETED, CANCELLED]	Activity status reference
Participants	jsonb	Optional, Default: []	List of participants
Attachment URLs	array	Optional	List of attachment URLs

System-managed fields

Name	Type	Options	Comments
Activity ID	bigserial	Auto-generated	Primary key
UID	text	Auto-generated	Unique identifier (ULID)
Is Active	boolean	Default: true	Activity’s active status
Created By	bigint	Auto-populated	References user table
Created At	timestamp	Auto-populated	Creation timestamp with timezone
Updated At	timestamp	Auto-populated	Last update timestamp with timezone
Deleted At	timestamp	Optional	Soft delete timestamp with timezone

Database types:

Account ID and Created By are stored as bigint in the database
Location is stored as text
Duration is stored as integer
Participants is stored as jsonb
System fields use their respective database types (bigserial, text, boolean, timestamp with time zone)

Activity tracking

Planning

Schedule activities
Set clear objectives
Identify participants
Prepare required materials

Execution

Record attendance
Document key points
Track action items
Note decisions made

Follow-up

Update activity status
Create follow-up tasks
Share meeting notes
Schedule next steps

Best practices

Documentation

• Record activities promptly
• Include all relevant details
• Link to related records
• Maintain consistent format

Organization

• Use clear subject lines
• Categorize properly
• Tag all participants
• Set appropriate privacy

API endpoints

Sample activity

{
  "accountId": "ACC123",
  "title": "Quarterly Business Review",
  "type": "MEETING",
  "typeId": "T123",
  "typeConfiguration": {
    "icon": "video",
    "color": "#4CAF50"
  },
  "status": "SCHEDULED",
  "statusId": "S123",
  "statusConfiguration": {
    "icon": "calendar",
    "color": "#2196F3"
  },
  "activityTimestamp": "2024-03-20T14:00:00Z",
  "duration": 60,
  "location": "https://meet.google.com/abc-defg-hij",
  "participants": ["USER123", "USER456"],
  "attachmentUrls": [
    "https://storage.thena.ai/documents/agenda.pdf",
    "https://storage.thena.ai/documents/presentation.pdf"
  ],
  "metadata": {
    "agenda": "1. Q3 Review\n2. Q4 Goals\n3. Action Items",
    "meetingType": "QBR",
    "requiredPreparation": "Please review Q3 metrics before the meeting"
  }
}

When creating an activity, the system will add additional fields in the response such as:

id: Unique identifier for the activity
account: Name of the associated account
creator: Name of the activity creator
creatorId: ID of the creator
creatorEmail: Email of the creator
createdAt: Creation timestamp
updatedAt: Last update timestamp

Available operations

Activity management

# List account activities
GET /v1/accounts/{accountId}/activities

# Create account activity
POST /v1/accounts/{accountId}/activities
Content-Type: application/json

# Get activity by ID
GET /v1/accounts/{accountId}/activities/{activityId}

# Update activity
PATCH /v1/accounts/{accountId}/activities/{activityId}
Content-Type: application/json

# Delete activity
DELETE /v1/accounts/{accountId}/activities/{activityId}

All endpoints require authentication with Bearer token, API key, and Organization ID in the headers.

For detailed API specifications, see Activity Management

Accounts overview

Learn about account management

Contacts

Manage customer contacts

Introduction

Core concepts

Apps framework

Platform events

Understanding activities

Core purpose

Activity types

Communication activities

Business activities

Standard fields

Required fields

Optional fields

System-managed fields

Activity tracking

Best practices

Documentation

Organization

API endpoints

Sample activity

Available operations

Accounts overview

Contacts

​Understanding activities

Core purpose

​Activity types

Communication activities

Business activities

​Standard fields

​Required fields

​Optional fields

​System-managed fields

​Activity tracking

​Best practices

Documentation

Organization

​API endpoints

​Sample activity

​Available operations

​Related resources

Accounts overview

Contacts

Understanding activities

Activity types

Standard fields

Required fields

Optional fields

System-managed fields

Activity tracking

Best practices

API endpoints

Sample activity

Available operations

Related resources