Setting the file. One moment.
Skill 103 · Querying PostHog Data
Subchapter 103.38
references/models-customer-tasks.mdMarkdown1 KBView on GitHub
system.customer_tasks contains customer follow-up tasks, with task and linked-account access controls applied.
These are separate from AI coding tasks.
Columns: id (UUID), team_id, account_id (nullable UUID), , , ,
, , , , , , , .
User IDs are PostHog project members. Status is , , , or .
namedescriptionstatusassigned_to_iddue_atcompleted_atcompleted_by_idcreated_by_idarchived_atcreated_atupdated_atopenin_progresscompletedcanceledSELECT id, name, assigned_to_id, due_at
FROM system.customer_tasks
WHERE archived_at IS NULL AND status IN ('open', 'in_progress')
ORDER BY due_at ASC
LIMIT 100Use posthog:customer-tasks-create to create a task, posthog:customer-tasks-partial-update to edit it,
and posthog:customer-tasks-archive-create or posthog:customer-tasks-restore-create to archive or restore it.
Use posthog:customer-tasks-list and posthog:customer-tasks-retrieve for API reads with nested account and user details.
Use posthog:customer-tasks-activities-list for the change history, including redacted historical account details.