{"id":101478,"plugin_id":"plugins_6af4333b6f008191806d76e5f43ec5f9","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-17T12:11:35.793Z","digest":"626da6ef7c9efe603155a3416f802f811a23edd8b535d026fc28ee3036267a1c","against":null,"payload":{"description":"Working with Tines Cases from a 3B workflow or chat — creating, updating, listing, and managing cases with their comments, subscribers, and activities, plus the Records store cases draw on. Use this whenever you’re asked to open, update, close, search, or manage a Tines case, to work with Tines records, or to call the Tines API for anything case- or record-related.","included_files":[],"name":"tines-cases","skill_md_contents":"---\nname: tines-cases\ndescription: Working with Tines Cases from a 3B workflow or chat — creating, updating, listing, and managing cases with their comments, subscribers, and activities, plus the Records store cases draw on. Use this whenever you’re asked to open, update, close, search, or manage a Tines case, to work with Tines records, or to call the Tines API for anything case- or record-related.\nlicense: Apache-2.0\ncompatibility: Tines 3B\n---\n\n# Working with Tines Cases\n\nTines Cases is Tines’ investigation and case-management surface, and Records is the structured-data store alongside it. You reach both through the same **Tines Stories** connector (identifier `tines`) that covers the rest of the Tines API.\n\n## Find the connector first\n\nBefore writing any call, use the `searchConnectors` tool with the identifier `tines` to find an existing “Tines Stories” connector. Reuse it if one exists. Only if none is found, prompt the user to create one with the `connectStepToApp` tool.\n\n## Read the endpoint doc before you write the call\n\nPayloads have non-obvious fields, so fetch the specific endpoint doc and follow it rather than guessing. The API index the connector points you at links a per-endpoint markdown doc for every case operation and sub-resource (comments, records, subscribers, activities, and so on), and for every record operation. For a conceptual overview of how Cases works, see `https://www.tines.com/docs/cases/overview/`.\n\nFlag ambiguity rather than guessing silently.\n\n## Records\n\nRecords are structured, queryable tables: a record type defines typed fields, and each record is a row of field values. They stand on their own, and a record can additionally be linked to one or more cases, e.g., when it’s evidence in an investigation. Records live under `records`, their schemas under `record_types`, and a case’s linked records under `cases/<case_id>/records`.\n\nFor a conceptual overview, see `https://www.tines.com/docs/records/`. Before writing record calls, read `https://www.tines.com/llm/stories/docs/api/records/best-practices.md` — it covers aggregate queries, pagination, filters, rate limits, retention, and linking records to cases.\n\n## Base path\n\nCases and records live under `{TINES_URL}/api/…`. Prefer the newest API version an endpoint offers, and don’t fall back to an older version just because the connector’s connection test happens to hit one. Versions vary by endpoint — some case-related operations sit under the newer version while others are still on the older one — so check the endpoint doc for the current version of each call rather than assuming a single base path.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}