Knowify

Create a checklist or punch-list item on a project. A ListItem is a single to-do, deficiency, or work item tracked at the project, milestone, or task level. Use this to add items the user describes ("add a punch list item to job 102345 for ...", "create a task on phase X to ..."). REQUIRED: ProjectId, Description. OPTIONAL: MilestoneId/TaskId to scope, Deadline (ISO date), ResourceIds to assign, UnitsTotal/UnitName for measurable items. ASSIGNMENT: ListItems without ResourceIds are created unassigned. When the user creates a task for themselves or another person, set ResourceIds to that person's Resource Id. Look up the current user's Resource Id from `knowify://me`. If the user says "create a task" without naming an assignee, ASK who it should be assigned to before creating. Default applied by the API: Done=false. Returns the new ListItem in the same shape as a GET on `/api/v2/list-items/{id}`.

list_items_create

Soft-delete a list item by Id. The item is marked Inactive (ObjectState) rather than physically removed, so it stops appearing in default list queries but related history is preserved. There is no API-level undo from this tool — recovery would require an admin action.

list_items_delete

Schemas, guides, and domain reference for the Knowify data model.Pair with `query` only when you need raw data for your own internal computation. **For user-facing questions about Knowify data, use `ask_knowify` instead — it handles schema lookup, the platform's conventions and gotchas, and presentation internally.** Modes: - No args → returns categorized index of all available knowledge - search: 'todos' → finds matching content across all guides and schemas - search: 'retainage', scope: 'schema/*report*' → search only report schemas - search: 'create a project', scope: 'api' → hybrid search over OpenAPI operations - uri: 'overview' → reads a specific resource in full Search is useful for discovering model names from common terms. Example: platform_knowledge({ search: 'todos' }) reveals that todos are 'ListItems'. Example: platform_knowledge({ search: 'profitability', scope: 'schema/*report*' }) finds the right report. Example: platform_knowledge({ search: 'how do I create a project', scope: 'api' }) finds the right endpoint. Knowify is a project management platform for contractors and professional services. ## About the Data - Each connection is scoped to a single company (tenant). Data from other tenants is not accessible. - All date fields are stored in UTC. Company time zone is available via `knowify://company`. - Knowify is in beta. For questions or issues, users can reach support@knowify.com. ## Resources - `knowify://me` — Current authenticated user profile - `knowify://company` — Current company profile **Name:** Marc Mock **User ID:** 100007 **Resource ID:** 132983 **Email:** mvisent+demo@knowify.com **Username:** mvisent+electrical@knowify.com **Access:** none, system-user, tenant-admin, tenant-user **Company:** 10 Knowland Electrical Inc **Address:** 76 Bowery — New York **Time Zone:** America/New_York **Company ID:** 26070 **Tenant ID:** 23955

platform_knowledge

Use `platform_knowledge` to read a model's schema before your first query against it. BEHAVIORS: - Most ENTITY models auto-filter to ObjectState = 'Active'. To include inactive records on entities, add where: { ObjectState: { $in: ["Active", "Inactive"] } } - REPORT models DO NOT have an ObjectState column — the underlying report function already returns only active rows. Never pass an ObjectState filter on a report; Postgres will reject the query with "column does not exist". - Enum fields accept string values (e.g. BusinessState: "Open"), not integers - Use "fields" (not "attributes") to select specific columns - Models have 20-40 columns. Use "fields" to select only the columns relevant to the question. - Results in the platform use human-readable names. NEVER surface internal IDs (Id, ProjectId, MilestoneId, ResourceId, etc.), raw schema field/column names, association names, scope names, hash-prefixed enum codes, or query mechanics in your answer to the user. These are query-layer artifacts: use them to fetch and join data, then report only the human-meaningful values (names, dates in tenant TZ, money, statuses in plain words). Refer to records by their name, not their ID. DATA MODEL EXAMPLES: { table: "Projects", where: { BusinessState: "Open" }, include: ["Client"], fields: ["Id", "ProjectName", "ClientId", "BusinessState"], limit: 10 } { table: "TimeEntries", scopes: ["active-check-ins"], include: [{ association: "Resource", fields: ["Description"] }] } { table: "Clients", where: { "$Projects.BusinessState$": "Open" }, include: ["Projects"] } REPORT MODELS (require 'params' scope): JobsReport, BillsSummaryReport, InvoicesSummaryReport, TimeEntriesReport, SalesReport, PurchasesReport, PurchasesAndItemsReport, BillableItemsReport, SubcontractorsReport, SubcontractorDocsReport, QuotingPerformanceReport, CatalogAnalysisReport, ServiceJobsSummaryReport, ServiceVisitsReport, WipReport Report example: { table: "JobsReport", scopes: [["params", { date_type: "created", start_date: "2024-01-01", end_date: "2024-12-31" }]], where: { Status: "#ACTIVE" }, fields: ["ProjectName", "ClientName", "ContractTotal", "Profit"] } WHERE OPERATORS: Comparison: $eq, $ne, $gt, $gte, $lt, $lte Pattern: $like, $iLike, $startsWith, $endsWith Set: $in, $notIn Range: $between, $notBetween Logical: $and, $or, $not Fuzzy: $fuzzy (typo-tolerant) Cross-model: { "$Association.Field$": value } Direct value implies $eq: { Status: "Active" }

query

Update fields on an existing list item. Only the fields you send are changed (PATCH semantics). Common uses: - Mark complete: `{ Id, Done: true }` — server stamps DateCompleted + CompletedBy. - Reassign: `{ Id, ResourceIds: [42, 18] }` — pass the FULL desired set, not a delta. - Reschedule: `{ Id, Deadline: "2026-07-01" }`. Returns the full updated ListItem.

list_items_update