Unique identifier for the activity
The type of activity (Note, Task, or Event)
Information about who created the activity
The display title/summary of the activity
Primary content for the activity
Start time of a scheduled activity. Notes are not typically scheduled unless they're about specific times. For recurring events, this represents the start of the first occurrence. Can be a Date object for timed events or a date string in "YYYY-MM-DD" format for all-day events. Null for activities without scheduled start times.
End time of a scheduled activity. Notes are not typically scheduled unless they're about specific times. For recurring events, this represents the end of the first occurrence. Can be a Date object for timed events or a date string in "YYYY-MM-DD" format for all-day events. Null for tasks or activities without defined end times.
For recurring activities, the last occurrence date (inclusive). Can be a Date object, date string in "YYYY-MM-DD" format, or null if recurring indefinitely. When both recurrenceCount and recurrenceUntil are provided, recurrenceCount takes precedence.
For recurring activities, the number of occurrences to generate. Takes precedence over recurrenceUntil if both are provided. Null for non-recurring activities or indefinite recurrence.
Timestamp when the activity was marked as complete. Null if not completed.
Reference to a parent activity for creating hierarchical relationships
OptionalthreadFor nested activities in a thread, references the top-level activity of that thread
Array of interactive links attached to the activity
The priority context this activity belongs to
Recurrence rule in RFC 5545 RRULE format (e.g., "FREQ=WEEKLY;BYDAY=MO,WE,FR")
Array of dates to exclude from the recurrence pattern
Array of additional occurrence dates to include in the recurrence pattern
For recurring event exceptions, points to the root recurring activity. Used when an individual occurrence of a recurring event is modified.
For recurring event exceptions, the original occurrence date being overridden. Used to identify which occurrence of a recurring event this exception replaces.
Metadata about the activity, typically from an external system that created it
Tags attached to this activity. Maps tag ID to array of actor IDs who added that tag.
Array of actor IDs (users, contacts, or twists) mentioned in this activity via @-mentions
Represents a complete activity within the Plot system.
Activities are the core entities in Plot, representing anything from simple notes to complex recurring events. They support rich metadata including scheduling, recurrence patterns, links, and external source tracking.
Example